Seedance 2.0
Modes, prompts, credits, and output
This guide is written for people who want the shortest route from a simple prompt or reference frame to a usable Seedance render.
Choose the mode that matches your source
Use text-to-video when you start from a written scene. Use image-to-video when a single still frame already contains the composition you want. Use the reference-driven workflow when you need a cleaner storyboard-style pass around an existing visual anchor.
The goal is to start with the simplest input that still protects the shot you care about. That keeps the prompt shorter and makes the final render easier to review.
- Text-to-video for prompt-led scenes
- Image-to-video for composition or identity anchors
- Reference-driven motion for storyboard-style planning
Set the shot before you render
Seedance Pro currently supports 4s to 15s clips, plus 480p and 720p quality settings. Pick the aspect ratio for the destination first, then decide how much movement the shot really needs.
Short clips tend to work best when the prompt focuses on one subject, one motion beat, and one camera direction. That keeps the result easier to judge and usually gives a cleaner first pass.
- 16:9 for product and landing-page clips
- 9:16 for vertical social placements
- 1:1 or 4:3 for square or editorial framing
Plan credits in integers
The studio estimates credits before you generate. The current mapping is simple: 480p uses 5 credits per second, and 720p uses 11 credits per second.
That means a 4 second 480p render costs 20 credits, while a 5 second 720p render costs 55 credits. Users can read that quickly without thinking through decimal math or hidden multipliers.
- 480p = 5 credits per second
- 720p = 11 credits per second
- The toolbar shows the live total before render
Review the output, then refine the brief
After generation, check the video, the last frame, and the archive together. That makes it easier to decide whether the problem is the motion, the framing, or the original prompt.
If the result is close but not quite right, keep the successful parts of the brief and only change the weakest line. That is usually faster than rewriting everything from scratch.
- Use cases help users see what the model already does well
- Pricing explains the credit cost before the task starts
- The archive keeps the previous render context available
If you want to compare what the model already does well, open the case gallery. If you want to estimate monthly usage, check the pricing page. If you want to render now, open the studio.
