🔑 How to Access Seedance 2.5 (And What Isn't Live)

Seedance 2.5 launched on July 31 and immediately produced a familiar problem: a lot of pages explaining how to use an API that does not exist yet. Here is what is actually reachable today.

Update, August 7: one of those APIs now exists. Higgsfield shipped seedance_2_5 in its live model catalog — the first real third-party surface for the model — and we verified its parameters against that catalog the same day. The route table has been reordered accordingly. ByteDance's own ModelArk API is still "coming soon".

By the numbers#

The now-primary route: Higgsfield ships seedance_2_5#

The headline change since this page first ran: on August 7, Seedance 2.5 went live in Higgsfield's model catalog as seedance_2_5 — the first shipped third-party API surface for the model, verified against the live catalog that day. If you hold a Higgsfield account with credits, you can call it now: through the website, or programmatically over API, MCP and CLI.

What the deployment exposes, briefly: four modes — t2v (default), omni_reference for image + video + audio references, video_edit, video_extension — durations of 4–30 seconds, seven aspect ratios from 21:9 to 9:16, and native audio on by default (generate_audio is a boolean defaulting to true). Resolution is 480p or 720p only, whatever the "up to native 4K" marketing headline says. There are no start/end-frame roles, so keyframe pipelines stay on 2.0. The parameter-by-parameter walkthrough is in our Higgsfield settings guide.

Two caveats stated plainly. This is Higgsfield's deployment spec, not ByteDance's — the official ModelArk API, whenever it lands, may differ. And it is credit-billed with no published credit prices yet; API usage is explicitly not eligible under Higgsfield's unlimited plans.

The no-credits route: 14-Day Seedance Unlimited, week 2#

Higgsfield is also running a 14-Day Seedance Unlimited event — the one way to touch 2.5 without spending credits, with terms precise enough to trip over:

• Week 1 is unlimited Seedance 2.0 at 4K — most plans get 4K at 8 seconds per generation; Plus-monthly plans are capped at 1080p@8s or 720p@15s.
• Week 2 is unlimited on one other Seedance model of your choice, and 2.5 is on the eligible list. Caps for 2.5 are listed as "to be determined".
• It is website only — explicitly not MCP, CLI, Canvas or Supercomputer. If your pipeline is programmatic, the event does not cover it.
• Maxed-out Ultra, Max and Team plans are ineligible.
• New users get a 24-hour trial: five generations of Seedance 2.0 at 4K@8s.

ByteDance's own two routes: Jimeng and Doubao Pro#

ByteDance's own announcement names the paths precisely: Jimeng Web → Video Generation → Select Seedance 2.5, and Doubao Pro → Video Generation → Select Seedance 2.5.

Both are consumer applications rather than developer surfaces. You get the model through an interface, not an endpoint — which means no batching, no programmatic pipeline, and no model ID to point a script at. For a solo creator that is workable. For anything automated it is a blocker.

Both are also ByteDance's Chinese-market products. ByteDance has published no regional availability list for 2.5, so whether you can reach them depends on your region and account, and we are not going to pretend otherwise or walk you through circumventing it.

ByteDance's own API still isn't live#

ByteDance's launch post says API access via BytePlus ModelArk is coming soon. That is the entire official statement, and it was still true when we re-checked ModelArk on August 7.

Two checks confirm it. ModelArk's published model list still shows Seedance 2.0, 1.5-pro and 1.0-pro, with no 2.5 entry. And ByteDance has released no official model IDs for 2.5 — a callable string now exists, but seedance_2_5 is Higgsfield's identifier for its own deployment, not a ByteDance publication.

This matters because a number of gateways and reseller sites already publish "Seedance 2.5 API" documentation, complete with endpoints and parameter tables. Those are the gateway's own conventions, written in anticipation. They may end up matching ByteDance's release. They may not. Building against them is a bet.

Higgsfield left that category on August 7. Its seedance_2_5 is a shipped, documented deployment you can verify in a live catalog — the difference between a convention and a product. It is still a platform's own surface rather than ByteDance's, but it is real, callable and testable today.

Jimeng, Dreamina, Doubao, CapCut: which is which#

The naming causes real confusion, so plainly:

• Jimeng — ByteDance's Chinese-market AI creation product. Named in the launch post.
• Dreamina — the international branding of the same line, inside the CapCut ecosystem.
• Doubao — ByteDance's assistant product; Doubao Pro is the paid tier that carries 2.5.
• BytePlus ModelArk (also referred to as Volcano Ark) — the developer/API platform. Where the API will land.

Worth noting: ByteDance's own Dreamina surface hosts a page addressing Seedance 2.5 character consistency, which tells you the vendor treats these as real user questions even while the developer path stays closed.

Why the gateways are ahead of ByteDance#

Several API resellers published Seedance 2.5 endpoints within days of launch. That is not necessarily bad faith — it is how the aggregator market works. A gateway that lists a model early captures the search traffic for it, and if the official API arrives shaped differently, they adjust.

The risk sits with you rather than them. Code written against a provisional endpoint may need rewriting when ByteDance ships real model IDs, and pricing quoted before an official rate card exists is the reseller's guess at what their margin will need to be. If you must start now, isolate the provider behind your own interface so swapping it later is a one-file change.

What to do in the meantime#

If you are shipping this month, stay on Seedance 2.0. It has a live API, published pricing, documented model IDs and — after months of production use — mapped moderation behaviour. As of August 7, 2.5 has ticked the live-API and model-ID boxes on Higgsfield; pricing and mapped moderation remain the open two, and if your pipeline pins start/end frames, 2.5 has no roles for them at all. The full trade-off is in Seedance 2.5 vs 2.0.

If you need 30-second single takes specifically, that capability has no substitute right now; 2.5 is the only model doing it in one pass. Since August 7 you no longer need a consumer app for it either: 30-second single passes are callable on Higgsfield at 480p or 720p. The unpublished part now is just the price.

If you need a live public API today with a documented spec, MiniMax H3 launched the same day with exactly that — a complete v2 reference, published limits and pay-as-you-go access. It caps at 15 seconds and 2K, so it is not a like-for-like replacement, but it is buildable-against right now. See H3 vs Seedance 2.5 for where the line falls.

If you are evaluating, read what ByteDance has actually confirmed before trusting any spec sheet. Most of the numbers circulating for 2.5 are either 2.0 figures relabelled or invented outright.

How we checked#

Access routes and the API status come from ByteDance Seed's own launch announcement, which names the platforms and the menu path directly. The absence of a 2.5 entry on BytePlus ModelArk was verified against its published model list. CineD's launch coverage corroborates both the rollout platforms and the pending API. The Higgsfield route — model ID, modes, durations, resolutions — was verified first-hand against Higgsfield's live model catalog on August 7, and the 14-Day Unlimited terms come from Higgsfield's own event material; ModelArk was re-checked the same day, still with no 2.5 entry.

We have not tested either consumer route ourselves — we do not hold Jimeng or Doubao Pro access, and we are not going to describe an onboarding flow we have not seen. Everything above is what ByteDance published about where the model lives.

Last verified: August 7, 2026, including the first-hand check of Higgsfield's live model catalog. The thing most likely to date this page now is the ModelArk API going live. When it does, official model IDs and pricing arrive with it and most of the remaining unknowns on this page resolve at once.

What didn't make the cut#

Workarounds for regional restrictions. People ask, and it is not something we are going to write up — account terms and regional licensing are ByteDance's to enforce, and a guide to getting around them is not useful advice.

We also left out the gateway-by-gateway comparison of who claims 2.5 access. Until there is an official API to compare against, ranking unofficial implementations would be ranking guesses. Higgsfield graduated out of that list on August 7 by shipping something checkable; the rest are still guesses.