Seedance 2.0 Fast vs Mini: which should you test?

Seedance 2.0 Fast and Seedance 2.0 Mini share the same main output limits: 480p or 720p, four to fifteen seconds, and synchronized audio. Mini has a lower published token rate, but neither the names nor the specification table establishes which gives you a usable shot sooner. Choose with a matched brief, current prices and a clear definition of an acceptable result. 1 2

The Fast model page and Mini model page provide separate Playgrounds, samples, live rate tables and request previews. This guide explains what to compare before spending credits. It does not claim a measured quality or latency winner on Wan API.

Check the shared limits firstCopy heading link

These facts were checked against first-party specifications on October 15, 2026. The standard Seedance 2.0 has different resolution options; do not transfer its 1080p or 4K settings to either variant. Seedance 2.5 offers a longer generation window and a larger reference allowance. A scene that requires twenty continuous seconds already falls outside both variants in this comparison. 1

The per-type reference counts also come with constraints. For each model, reference video must total no more than fifteen seconds, and reference audio has its own fifteen-second combined limit. Audio references require a reference image or video. First-frame and first/last-frame inputs cannot be combined with the mixed reference collection. Consult the model-specific guide before preparing assets. 3 4

Compare the whole request costCopy heading link

The model pages calculate the Wan API price from the current rate configuration. Use those live figures when budgeting. Official comparison rates are linked alongside them; they are not a fallback quote when Wan API pricing is unavailable.

Without reference video, the generated output determines video-token usage. With reference video, both input and output contribute, and a minimum billable input allowance applies. The lower token rate in the reference-video column therefore does not imply a cheaper request. Adding a clip simply to reach that column can increase the total bill. Audio does not introduce a separate rate tier. 2

For a practical comparison, keep duration, resolution, framing and reference files identical. Compare the estimated maximum before each submission, then record the final cost beside the result. A cheaper attempt that needs several revisions can cost more per accepted shot than a more expensive attempt that works for the edit.

A useful record has these columns:

What the two samples actually showCopy heading link

The Fast page shows a golden retriever running through shallow water at sunset. Its tracking camera makes the animal's gait, body consistency and splashes useful review points. Check whether the dog stays recognizable through the movement and whether the action remains continuous.

The Mini page shows a park bench with falling autumn leaves and a gentle camera push-in. Watch the bench geometry, leaf motion and background stability. A quiet scene can still fail if details pop in and out or the camera makes an unintended cut.

Both existing sample files are 1280 × 720, approximately five seconds long, at 24 fps, with an audio track. The stills on each page were extracted from that page's own video. These are different scenes, so they are not a controlled comparison. We have not used them to calculate a speed advantage, a success rate or a cost-per-result claim.

Run a comparison that answers your questionCopy heading link

Choose the brief from your actual work. For a product shot, define the product details that must remain recognizable. For a character scene, specify the action and the moment it ends. For an environmental insert, decide which elements stay stable and which move.

For example, a small motion study could use this prompt:

Use the same prompt for both models, at five seconds, 720p and 16:9, with generated audio enabled. Start without references if you want to isolate text direction. If your production brief depends on a reference image, use that same image in both requests instead. This is a proposed test brief, not a report of a test we have run.

Before generating, write down the acceptance criteria: no unexpected cut, a recognizable boat through the whole clip, continuous movement and suitable sound. Review video at full size, then listen separately. Record specific failures rather than a vague quality score. If you revise the prompt for one model, give the other the same revised brief before comparing again.

A single successful result cannot establish consistent performance. A larger repeated test can improve confidence, but it also costs money; decide the scope and budget before expanding it.

Choose the next step from your constraintsCopy heading link

If you need a focused 720p shot and want to investigate budget, Mini is a reasonable candidate to test against your acceptance criteria. If you are considering Fast for a motion-heavy brief, test the action and actual elapsed time rather than assuming its name guarantees a particular turnaround. If either model misses a critical detail, revise the reference roles or scene complexity before drawing a conclusion about the entire model.

For an application, keep each variant explicit in saved requests. The Fast integration guide and Mini integration guide document their model identifiers, fields and task retrieval. Native editing, extension and final-frame-image capabilities are not exposed by this Wan API integration, so do not design around them from a general model announcement alone.

Return to the Fast Playground or Mini Playground to prepare your request. Playing either existing sample does not spend credits. Generating a new result requires an available service and enough balance for the displayed estimate.

SourcesCopy heading link

1. BytePlus: Seedance 2.0 series tutorial, model-specific capabilities and output limits. Checked October 15, 2026.

2. BytePlus: ModelArk pricing, international video-token rates and reference-video billing. Checked October 15, 2026.

3. Seedance 2.0 Fast endpoint specifications, supported input and output settings. Checked October 15, 2026.

4. Seedance 2.0 Mini endpoint specifications, supported input and output settings. Checked October 15, 2026.