Seedance 2 Prompt Guide: Plan Shots That Actually Cut Together

Why good-looking Seedance 2 clips still fail

Seedance 2 can combine text, image, video, and audio direction, which makes the prompt feel like a tiny production brief. That flexibility is also where weak workflows break. A prompt asks for three scenes, five camera moves, dialogue, a product transformation, and a logo reveal; the result contains pieces of everything but no clean shot an editor can approve.

The useful unit is one shot with one story job. Define what the audience must learn or feel, what must remain true, and what the first and last frames need to provide. Then judge the output against that contract. This changes prompting from taste-driven rerolling into a production process.

The seven-part shot contract

A strong contract might read: “Six-second medium close-up of the approved ceramic bottle on a wet stone counter at blue hour. A hand enters from camera right, lifts the bottle once, and leaves frame. Slow 10-centimeter push-in, stable horizon, soft rain ambience, no music. Preserve the exact cap, label-free surface, proportions, light direction, and rightward hand movement.”

The contract does not guarantee a perfect result. It makes defects visible. If the bottle changes shape, that is a failed lock. If the hand performs two actions, that is a failed action. If the camera orbits, that is a failed camera brief.

Give every reference one documented job

Ranking Seedance guides correctly emphasize reference files and prompt structure. The missing step is reference ownership. For each uploaded item, write what it controls and what it must not override. A portrait can control face and hair; a product pack can control geometry and material; a motion clip can control timing; a sound reference can control cadence. Avoid several contradictory images competing to define the same fact.

Use only material you own or are authorized to use. A public video being easy to download does not make its people, music, voice, product design, or cinematography free production input.

Write camera direction an operator could perform

“Cinematic camera” is an aesthetic wish. “Locked waist-height medium shot, then a slow push-in while the subject remains centered” is an instruction. Define starting frame, camera height, subject distance, lens feel, movement, and end frame. Prefer one motivated move: pan to reveal, track to follow, tilt to reframe, push to intensify, or pull back to reveal context.

Do not combine a drone dive, orbit, handheld shake, zoom, rack focus, and whip pan in one short clip. If two camera ideas matter, test them as separate shots. That produces clean edit options and reveals which movement actually serves the story.

Prompt synchronized audio as part of the event

Seedance 2 is presented in QuestStudio as supporting native synchronized audio. Treat sound as a timed layer, not a final adjective. Name the source, its relationship to the action, and what should be absent. “At the moment the cap clicks shut, one dry plastic click; quiet studio room tone; no music and no speech” is testable.

For dialogue, keep the line short, write the exact words, state the language, and review pronunciation with a fluent listener. A convincing face does not excuse a changed word. If exact legal or product language matters, plan to replace or finish the track in an audio workflow rather than trusting one generated pass.

Build continuity before generating the sequence

Create a continuity card for recurring people, products, wardrobe, environment, screen direction, time, key-light direction, and prop state. Save the accepted ending frame from shot A and use it to brief shot B when the workflow allows. The next shot should inherit the same state unless the story explicitly changes it.

Generate an establishing shot, action shot, detail, reaction, and close separately. Keep an overlap at edit points: a completed head turn, hand reaching, object crossing frame, or stable one-second hold. Overlap gives the editor a motivated cut. A flashy transition cannot repair a product that quietly changes between clips.

Use a one-variable repair ladder

1. Identity or product drift: reduce competing references and restate only the invariant facts.
2. Too many actions: shorten the clip and keep one verb.
3. Wrong camera: remove style language and specify start, move, and end.
4. Broken motion: simplify interaction, preserve screen direction, or split the action.
5. Audio mismatch: isolate one sound event or generate the picture without dialogue for later finishing.
6. Almost right: change only the failed variable. Do not rewrite the whole prompt and lose the diagnosis.

Record the prompt, references, duration, accepted output, rejection reason, and changed variable. The useful metric is cost and time per approved clip, not the number of impressive generations.

Approval test for an edit-ready shot

• The shot performs one documented story job.
• Identity, product geometry, hands, text, and background facts remain stable.
• The camera starts and ends where the edit expects.
• Motion has believable weight, direction, contact, and timing.
• Spoken words and sound events are correct, authorized, and intelligible.
• The first and last second contain usable handles.
• A normal-speed phone review and a frame review both pass.

Run the same contract through Seedance 2 in QuestStudio, keep the first test short, and save the rejection reason beside each version. That record becomes more valuable than a folder of unexplained renders.

What the current prompting guidance gets right

Luma's Seedance 2 prompting guide is useful on prompt structure, camera terms, multimodal references, and audio direction. This workflow adds the production layer: who owns each reference, what counts as a pass, how adjacent shots preserve state, and when a failed variable should be isolated instead of hidden.

Frequently asked questions