How to Use Seedance 2.5: A Step-by-Step Guide (Pre-Release Access)
Seedance 2.5 is not yet generally available. Access is pre-release and provider-mediated, so the routes below range from first-party apps to a pre-release API. This is an independent guide; EvoLink is our recommended third-party provider, and this site is not affiliated with ByteDance. Verify current availability and support with your provider before relying on any route in production.
Route 1: first-party apps (Dreamina, CapCut)
ByteDance is expected to ship Seedance 2.5 inside its own creative apps. If you already pay for Dreamina or CapCut tiers and your region gains access, this can be the most integrated experience — generation, editing and publishing in one place. The catch: rollout is expected to be staged by region and tier, and heavy usage tends to run into tier limits quickly.
Route 2: the API route (pre-release)
Platforms like EvoLink plan to serve Seedance 2.5 over a REST API, pay-as-you-go. The intent is no subscription — you top up and pay per generation. Public rates are not published yet; billing is expected per second of output, native audio included free, with an optional content-filter-off surcharge (+10%). Confirm pricing on the rate card and check provider support before you commit. This is the route we plan to use across this site, and the most practical one for developers — the API quickstart has copy-paste code, and the model id (seedance-2.5-reference-to-video) is pre-release, so keep it configurable.
Don’t want to write code? Set up your shot in our playground: write the prompt, pick duration and quality, and your settings can carry over to EvoLink when generation goes live. You can also drive it from an agent.
Writing the prompt: direct, don’t describe
The single biggest quality lever is prompting like a director rather than a wisher. Compare:
❌ “A beautiful city at sunset, cinematic, high quality”
✅ “Golden-hour drone pullback over a coastal city, anamorphic flare, slow dolly out over the harbor as streetlights flicker on”
The second prompt specifies camera (drone pullback, slow dolly out), light (golden hour, flare), and an event with timing (streetlights flicker on). Seedance 2.5 is expected to follow camera vocabulary well — whip-pan, rack focus, crane move, handheld shake are all worth writing explicitly.
A structure that tends to perform:
- Shot type + camera move — “macro lens push-in”, “handheld tracking shot”
- Subject + action — what happens, in sequence
- Light + atmosphere — “backlit steam”, “sodium streetlight”
- Style anchors — film stock, era, genre
Steal working examples with settings attached from the prompt library.
Using references
References are where 2.5 is expected to stand out. A single request accepts up to 30 image, 10 video, and 10 audio references — spend that budget deliberately:
| Reference type | What it locks | Practical tip |
|---|---|---|
| Images (up to 30) | Characters, products, locations, palette | 2–3 angles per character beats one |
| Video clips (up to 10) | Camera moves, motion style, effects | A short clip of the move is enough |
| Audio files (up to 10) | Tempo, rhythm, atmosphere | Motion can sync to beats — use clean mixes |
The workflow that works: start with prompt-only takes to find the shot, then add references one layer at a time — characters first, then camera move, then audio. Adding everything at once makes failures impossible to diagnose.
Duration, quality and audio
Expected duration is roughly 4–30 seconds per take. Launch quality options are 480p and 720p; higher resolutions such as 1080p and above are pending and not confirmed, so don’t design around them yet. Native audio is generated in a single pass and is expected to be included free — no separate audio step or file to stitch in.
Iterating without burning budget
Because billing is expected per second of output, iterate cheap: run short 480p or 720p drafts until composition and motion are right, then commit to the longer version. Public prices are not available yet, so estimate with the rate card once it is live rather than assuming a figure.
Common failure modes
- Morphing faces mid-take — add character reference images; don’t rely on the prompt.
- Dead camera — you didn’t specify a move. Static prompts get static shots.
- Audio out of sync with cuts — describe the sync explicitly (“lighting changes on each downbeat”) and provide the track as an audio reference.
Set up your first take in the playground, and verify provider support and pricing before you move to production.