Seedance 2.5 in Symphony takes 50 references: what Sume lists
TikTok says Seedance 2.5 in Symphony takes up to 50 image, video and audio references. Sume's docs give per-model reference types, so check the catalog first.

TikTok's August 3, 2026 post says Seedance 2.5 in Symphony accepts up to 50 multimodal references (image, video and audio), up from 9, and up to 30 seconds of video (read 2026-10-02). Sume's docs do not publish a single reference count for Seedance 2.5, so read the live catalog instead of assuming 50.
What TikTok says
The post says Seedance 2.5 is rolling out to select paid advertisers in select markets, through Symphony Creative Studio and Symphony Automations in TikTok Ads Manager. It adds that real face uploads remain blocked, that AI labels and invisible watermarking are applied, and that C2PA Content Credentials are included (read 2026-10-02).
| Item | What TikTok says |
|---|---|
| References | Up to 50 (image, video, audio), up from 9 |
| Video length | Up to 30 seconds, up from 15 |
| Availability | Select paid advertisers in select markets |
| Real faces | Uploads remain blocked |
What Sume documents
On Sume, seedance-2.5 accepts 4 to 30 seconds at 480p, 720p or 1080p (Video Router). References go in input_references, and only models whose supported_input_references lists a type accept that type. The docs say audio and video references are honored by the Seedance 2.x models (Video generation).
- Call the model list and read
supported_input_referencesforseedance-2.5. - Do not copy TikTok's 50 into your code; no Sume page I read states a count.
- Test a request with your real reference mix before you plan a batch.
What stays different
Symphony lives inside Ads Manager and labels its exports for TikTok policy. Sume returns a file from an async job, with no TikTok publishing step. If the clip will run as a TikTok ad, follow TikTok's own AI label steps.
Sources
Related posts
More in Comparisons
- Together AI dynamic rate limits (429, 503) vs Sume rate_limited
Together AI publishes no fixed tiers: limits track live capacity and your recent traffic. How its 429 and 503 map to Sume's rate_limited and queue_full.
- Together AI video API alternative: Sume /v1/videos compared
Together AI's video API is create-then-retrieve with five statuses. How that maps to Sume /v1/videos, and what each side does better.
- Together AI says download videos immediately: Sume media URLs
Together's docs say not to rely on video URLs for long-term storage. Sume returns media.sume.com artifacts as its public contract. What to save in each case.
- Together AI video status values vs Sume job statuses (canceled)
Together's video job has five statuses, including cancelled. Sume has five too, but spells it canceled and adds terminal and result_ready flags. Map them here.
Written by Sume