Seedance 2.0 4K price: Luma 261 credits/sec, Runway 150, Sume 1080p

Luma lists Seedance 2.0 at 4K for 261 credits per second, and Runway's API docs list seedance2 at 4K for 150 credits per second. Sume's docs list seedance-2 at 480p, 720p and 1080p, so there is no 4K request to price there.

Vendor figures are from Luma's pricing page and Runway's API pricing, both read 2026-10-01.

What do Luma and Runway list for Seedance 2.0?

Luma's rows are text-to-video and image-to-video with audio, in credits per second. Runway's seedance2 rows are in credits per second of output. Runway's page states that credits are bought at $0.01 each, which makes its 4K line $1.50 per second; Luma's page prints no per-credit price, only plan prices (Plus is $30 for 10,000 credits, or $0.003 per credit, so 261 is about $0.78 per second there).

Why not compare those directly?

Credits are not interchangeable between vendors, and the two tables are not the same product: Luma bills on its own plans, Runway on its developer portal credits. Read each row as that vendor's own price, not as a ranking.

What does Sume list for seedance-2?

The docs' sample catalog entry for seedance-2 shows supported_resolutions of 480p, 720p and 1080p, 4 to 15 seconds, and generate_audio true; the prose adds that "seedance-2 also offers 1080p" and that every other catalog model besides the few named tops out at 15 seconds (see Video generation). The catalog endpoint is the source for what your workspace can submit.

Video jobs reserve on submit at provider list price multiplied by 1.25, with usage.cost as the Sume billable amount. For the pixel dimensions behind each resolution, see Seedance 2.0 resolution pixels.

What should I do if I need 4K?

Check supported_resolutions for the model you intend to use; do not assume a 4K entry. Gemini Omni Flash 1.1 is named in the docs as accepting 4K, with a 3 to 10 second range; if your project needs 4K output on Sume, read the catalog for that model before planning.