Unified multimodal references
The official model supports text, image, audio, and video inputs in one generation architecture, allowing several types of context to shape a result.
A multimodal video model from ByteDance Seed built around text, image, audio, and video references with joint audio-video generation and detailed creative direction.
This diagram explains supported context types. It is not presented as a generated sample from the model.
The points below summarize the model family as documented by its developer. Product-specific limits are kept separate.
The official model supports text, image, audio, and video inputs in one generation architecture, allowing several types of context to shape a result.
Seedance 2.0 is designed to create motion and sound together instead of treating audio as a separate finishing step.
Reference materials and prompts can guide performance, lighting, shadow, and camera movement for more intentional scene direction.
Published model facts and current UnblurVideo status, last checked 2026-09-27.
Its model design is most useful when the brief depends on several reference types or when picture and sound need to be planned together.
Combine visual, motion, and audio direction when a text prompt alone cannot communicate the full brief.
Describe acting, staging, lighting, and camera movement as connected parts of the same shot.
Explore scenes where dialogue, ambience, or sound cues are part of the concept from the beginning.
Plan the inputs first, then use the fewest references needed to communicate the shot clearly.
Write the subject, action, setting, camera movement, lighting, and intended sound as one concise direction.
Use images for appearance, video for movement, and audio only when each reference contributes information the prompt cannot express precisely.
Check the provider variant, accepted inputs, duration, resolution, and cost before generating; those product limits can differ from the model family overview.
This public guide is the canonical UnblurVideo page for Seedance 2.0 and clearly separates published model capabilities from the current product integration.
Answers distinguish the published model family from the version and controls that may later be deployed here.
Use the same availability and specification checks before choosing the next model for your workflow.
Open the shared workspace to compare the current production models, supported settings, duration, and credit cost before submitting a job.
Source for this guide: ByteDance Seed model page.