🔍 Seedance 2.5 Specs: What ByteDance Actually Confirmed

We corrected our own Seedance 2.5 coverage this week. An earlier version of our guide led with "native 4K output" — a figure we carried over from June pre-launch reporting. ByteDance's actual launch announcement publishes no resolution at all. If we got that wrong reading the same sources everyone else did, the pages that never went back and checked are still wrong.

So here is the full ledger.

By the numbers — confirmed

Spec	Value	Source
Launch (consumer)	July 31, 2026	ByteDance Seed
Announced	June 23, 2026, Volcano Engine FORCE	ByteDance
Single-pass duration	Up to 30 seconds	ByteDance Seed
Extensions	Two further rounds	ByteDance Seed
Reference budget	30 images + 10 video + 10 audio = 50	ByteDance Seed
2.0's reference ceiling	12 files	CineD
Timestamp editing	Yes	ByteDance Seed
Green-screen replacement	Yes	ByteDance Seed
Camera re-editing	Yes	ByteDance Seed
3D blockout camera control	Yes	CineD
Prompt adherence vs 2.0	~20% better (vendor claim)	CineD
Platforms	Jimeng AI, Doubao Pro	ByteDance Seed
API	"Coming soon", BytePlus ModelArk	ByteDance Seed

Not published — treat any figure you see as invented

• Resolution. No ceiling stated. Not 4K, not 1080p, nothing.
• Frame rate. Not stated.
• Pricing. No rate card, no per-second figure, no credit cost.
• Official API model IDs. BytePlus ModelArk's model list still shows Seedance 2.0, 1.5-pro and 1.0-pro. There is no 2.5 entry.
• Render times and latency. Nothing published.
• Error codes. Nothing published for 2.5.
• Independent benchmarks. None exist. The ~20% prompt-adherence figure is ByteDance's own, and CineD explicitly flags the absence of third-party testing.

That is a long list of unknowns for a model with hundreds of pages already ranking for its specs.

Four fabrications currently circulating

"Native 4K." The most widespread. It comes from June reporting on the pre-launch beta and was never in the shipped announcement. We repeated it ourselves and have corrected it.

"Identity-Lock." A named feature appearing across several tool blogs and exact-match domains. It is in no ByteDance material. Consistency in 2.5 comes from the 50-file reference budget and from extension rounds that carry characters forward — not from a toggle you can enable.

"Reference strength 70–80%." A percentage slider that does not exist in any published interface description. Neither does a user-exposed seed lock.

Fabricated drift benchmarks. These matter because they shape how people spend the 50-slot reference budget. One widely-copied claim states that cutting from six references to two reduced drift by around 60%. Another describes hands-on testing where identity "drifts by the third or fourth shot." Both appear on sites publishing about a model released the day before, with no methodology. Nobody had run controlled drift tests on Seedance 2.5 in that window.

The corpus even contradicts itself: one page insists 2.5 "is not publicly available yet as of July 23, 2026, and remains in closed enterprise beta" while others describe hands-on results.

How to check a Seedance 2.5 claim yourself

1. Does ByteDance say it? Start at ByteDance Seed's launch post. If a spec is not there, it is not confirmed.
2. Does BytePlus list a model ID? If the API is being described but ModelArk has no 2.5 entry, the writer is describing a gateway's own convention.
3. Is the number attached to a version? Most concrete Seedance facts in circulation — pricing, moderation behaviour, error codes, render times — are genuine 2.0 facts relabelled as 2.5.
4. Could they have tested it? A drift benchmark published within 48 hours of a consumer-app launch, with no methodology, was not run.

What this means for planning

You can plan around the confirmed set. Thirty seconds in one pass, fifty reference files, and a real editing suite are substantial and well-documented capabilities — enough to decide whether 2.5 changes your workflow.

You cannot plan a budget or a delivery spec. Without a published resolution you do not know if it meets a client's master requirement, and without pricing you cannot model cost per finished minute. If a project depends on either, stay on Seedance 2.0, whose numbers are known, until ByteDance publishes.

For what H3 does differently — and it publishes a complete API reference, which is the sharpest contrast between the two July 31 launches — see H3 vs Seedance 2.5.

How we assessed this

Confirmed rows come from ByteDance Seed's own launch post and its model page, cross-checked against CineD, the one trade publication covering the launch rather than reselling access. The "not published" list was verified by absence: we checked the announcement and BytePlus ModelArk's model list for each item and found nothing.

The fabrication examples are real claims from pages currently ranking. We have not named the sites, because the point is the pattern rather than the offender, and several are churning the same syndicated text.

Last verified: August 1, 2026. This page is only useful while it is current. When ByteDance publishes a resolution spec or a rate card, the rows move from the second table to the first and we will update them here.

What didn't make the cut

Our own measurements. We do not have Jimeng AI or Doubao Pro access, so every claim here is documentary. We would rather publish a short verified list than a long plausible one — which is exactly the failure mode this page exists to document.