Why Is Seedance So Expensive? Where the Money Goes

There are two answers to the question why is Seedance so expensive, and only one of them is about the rate card. The first is the rate itself. Seedance 2.5 charges per second of finished video, and a second of 1080p footage with synchronised speech, effects and music is costly to produce. A single request occupies that capacity for two to five minutes. Per-second inference at that quality is priced close to what it costs to serve, so there is not much room in the rate to argue with.

The second half is more useful, because most invoices that feel expensive are larger than the rate card predicts. Four mechanics account for nearly all of that gap, and three of them are avoidable.

What the rate card says

Ten seconds at 1080p is about $4.62, at 720p about $2.67, at 480p about $1.19. The spread from the top row to the bottom is 3.9 times, which makes resolution the largest single lever in the request body.

Why is Seedance so expensive when the bill beats the estimate

A reference video is charged for its own length. Attaching a source clip drops the per-second rate at 1080p from $0.461856 to $0.275904, which reads as a discount. The clip's own duration is then added to the output duration before that lower rate applies. A ten-second source producing ten seconds of output bills twenty seconds, about $5.52, against $4.62 for the same ten seconds generated from a prompt. Cheaper per second, more expensive in total.

The five-thirds floor. Any request containing video is billed for at least five thirds of the output duration. A two-second source with a five-second output adds up to seven seconds and floors at nine. Nine is the charge. The shorter the source relative to the output, the more the floor dominates, so the smallest edits carry the largest proportional overhead.

Auto duration reserves at the cap. Sending duration: -1 lets the model choose the length and reserves credits as though the answer will be the full 30 seconds, refunding the difference afterwards. The refund is real, but the reserve clears first. On a thin balance that returns a 402 for a clip that was going to cost about a dollar, and the failure looks like a pricing problem rather than a sequencing one.

1080p renders that ship at 720p. 1080p costs 1.7 times 720p per second. When the finished file lands on a surface that transcodes to 720p anyway, that multiplier bought nothing you can see. Ten seconds at 1080p is $4.62; the same ten seconds at 720p is $2.67, and the delivered file is identical to the viewer.

Five ways to spend less at the same rate

Choose resolution from where the video will be watched rather than from a request template you copied once.

Iterate at 480p. Five seconds at 480p costs about $0.59 against about $2.31 at 1080p, and a prompt reads the same in both. Settle composition, motion and timing at the cheap tier, then render the keeper at the tier you deliver.

Use reference images instead of reference clips wherever either would carry the idea. Up to 30 images and 10 audio tracks add nothing to the bill. Only video adds seconds.

Set duration explicitly. It removes both the 30-second reserve and the 402 that follows it on a low balance.

Cut length before you cut quality. Cost is linear in seconds at a fixed resolution, so trimming a ten-second concept to six seconds takes 40 percent off the line item with no change to how the frames look.

What you are never charged for

Polling a running task is free. The two to five minutes of wall time a generation takes are free. Reference images and reference audio add no billable seconds. Failed jobs are refunded in full, including safety refusals, which surface as error 80006 without naming which stage fired.

That last point matters for anyone who has been burned by a run of refusals. The wasted resource there is time and attention, not credits.

Frequently asked questions

Why is Seedance so expensive compared with the figure I calculated? Almost always one of three things: a reference video added its own seconds, the five-thirds floor lifted a short request, or duration: -1 reserved at the 30-second cap and you are reading the reserve rather than the settled charge.

Does the reference-video rate actually save money? Per second, yes. In total, usually not, because the source clip's length is added to the output length before the rate is applied. Compare finished totals rather than per-second figures.

Is 720p enough? For most delivery surfaces it is, and it costs $0.266824 per second against $0.461856 at 1080p. Render at 1080p when the file will be viewed at 1080p.

Do refused generations cost money? No. A refusal returns error 80006 and the job is refunded in full.

The short version

Seedance charges per second for generated 1080p video with synchronised audio, and that work is costly to serve, so the rate card is close to the floor. The answer to why is Seedance so expensive on any particular invoice is usually one of four mechanics instead: reference-video seconds, the five-thirds billing floor, auto-duration reserving at the 30-second cap, and paying 1080p rates for video that ships at 720p. Fix those four and the rate itself stops being the issue.