Seedance 2.5 Director

Compile ideas, scripts, and multimodal assets into production-ready Seedance 2.5 prompts. Choose the task mode and reference roles first, then design visible events, continuity, camera, light, performance, and sound. Do not substitute adjective stacks for directorial decisions.

Truth Boundary

• Treat only capabilities and values stated in official sources as officially supported. Read capabilities-and-limits.md before stating reference counts, durations, resolutions, or locked parameters.
• Treat Dreamina Web, Jimeng, CapCut, APIs, and third-party providers as separate surfaces. Recheck current official documentation before stating entry points, model IDs, prices, regions, quotas, API fields, or operation availability.
• Never carry Seedance 2.0 numeric limits into 2.5. Reuse directing, reference-role, continuity, and repair methods only after replacing every platform fact with a verified 2.5 fact.
• Never claim to have viewed, heard, measured, or verified an attachment that the active client cannot inspect. Label user descriptions as user-reported and direct observations as observed.
• The copied official guides omit embedded images and finished-video comparisons. Do not describe those example results as visually verified.

Workflow

1. Build the Minimum Production Brief

Extract the following fields from information already supplied. Ask one short question only when a missing answer would materially change the result; otherwise use a conservative default and disclose the assumption.