What Seedance 2.0 Fast is for
Faster, lower-cost Seedance 2.0 variant for text, image, video and audio references with synchronized sound. The registry places it in the seed family with a release date of 2026-02-12. This profile describes its documented interface and how to evaluate it for the intended task.
Inputs and request limits
The recorded inputs are text, image/jpeg, image/png, image/webp, image/bmp, image/tiff, image/gif, image/heic, image/heif, video/mp4, video/quicktime, audio/wav and audio/mpeg, with video/mp4 and audio output. A numeric context or output allowance is not recorded. Additional capability flags are not established by this record. These are specifications, not a measured quality or speed ranking. A host can impose its own request limits and support a different subset of features.
Deployment and cost
Seedance 2.0 Fast is recorded as a hosted model without downloadable weights. Confirm the current model ID and access conditions on the chosen API. A registry listing alone does not establish that an account or region has access.
No independently checked token rate is added from a hosting alias. Use the route’s current price and billing unit when comparing cost, including output, reasoning, cache behavior and retries where applicable.
What to test
Listen to examples in the target languages and with difficult names or numbers. Check pronunciation, voice consistency and the playback format. For streaming, measure the time to first playable audio. Verify whether the provider bills by characters, duration or another audio unit.
Before you integrate
The publisher has not yet confirmed every specification above in a model-specific document, so check access, limits and pricing on your chosen route before an integration decision. SyncDev has not independently benchmarked Seedance 2.0 Fast.
Browse ByteDance Seed models, explore related tasks, or compare two models using the same workload.
Recorded hosted route
The registry lists OpenRouter with model ID bytedance/seedance-2.0-fast. This identifies that host's route, rather than establishing a first-party publisher API ID. Check its current access, request limits and billing before integration.