Seedance 2.0 Prompt Guide for AI Film Teams

A strong Seedance 2.0 prompt starts as a shot brief. Give the model one clear job, the right references, camera and lighting direction, constraints, and review criteria before you generate.

ByteDance Seed describes Seedance 2.0 as a unified multimodal audio-video model that supports text, image, audio, and video inputs. The official launch post describes up to 9 images, 3 video clips, and 3 audio clips as inputs. The model card says Seedance 2.0 supports 4-to-15-second audio-video output, native 480p and 720p, and a Seedance 2.0 Fast variant. BytePlus also maintains ModelArk docs for video generation and prompt writing.

Those inputs help, but they do not replace direction. A practical Seedance 2.0 prompt structure connects scenes, shots, references, takes, and dailies before the model starts generating.

Key takeaways

Seedance 2.0 prompts work best when the team writes them as shot briefs. Define the intent, separate each production note, assign jobs to references, write constraints that protect the scene, and review every take against the brief before final approval.

• Start with the shot’s purpose before writing visual detail.
• Separate subject, action, camera, lighting, environment, references, and constraints.
• Use references with clear jobs instead of attaching every image you like.
• Write review criteria before generation so the team can judge takes consistently.
• Use Lotix when you want prompts, references, takes, and approvals tied to scenes and shots.

Start with shot intent

Shot intent tells the model and the team why the clip exists. Write one sentence that names the story beat, then let that sentence decide framing, action, references, camera movement, and review criteria. Without intent, prompt revisions become guesswork for the whole team.

Before you describe the frame, answer why the shot belongs in the scene.

A shot may establish geography, reveal a character’s decision, show a prop clearly, bridge two actions, or end on a frame that sets up the next shot. If it tries to do too much, the prompt gets muddy and the take gets harder to review.

Use a one-sentence intent line:

Shot intent:
A tense close-up as Mara realizes the signal is coming
from inside the station.

That sentence anchors the rest of the prompt. It tells you what matters and what you can cut. If a wardrobe note, camera move, prop detail, or lighting idea does not serve the intent, place it in another shot.

Once the intent is written, it needs to stay with the generated output. That continuity is hard to preserve when prompts, references, and clips drift into separate folders. Lotix supports that production shape: a shot lives inside a project, sequence, and scene, then generated outputs become takes attached to that shot. The Lotix product workflow keeps the prompt, references, settings, and review state together.

Use a filmmaker-first prompt structure

A filmmaker-first Seedance 2.0 prompt separates production decisions into readable sections. The format helps directors, producers, editors, and collaborators revise one part of the brief without rewriting the whole prompt after a take misses the target during review sessions.

Use this structure:

• Intent: what the shot needs to communicate.
• Subject: who or what the camera follows.
• Action: what changes during the clip.
• Framing: close-up, medium, wide, insert, over-the-shoulder, or another clear frame.
• Camera: movement, lens feel, angle, height, speed, and stabilization.
• Lighting: source, contrast, color temperature, atmosphere, and practicals.
• Environment: location details that should stay visible.
• References: character, location, prop, wardrobe, image, frame, or video references and their jobs.
• Audio direction: music preference, dialogue direction, ambience, or sound behavior when relevant.
• Constraints: what should stay out of the shot or stay unchanged.
• Review criteria: what makes the take reject, maybe, selected, or approval-ready.

Here is a compact version:

Shot intent: Show Mara deciding to open the sealed signal case.
Subject: Mara, still and tense, framed from chest up.
Action: She looks from the blinking case light to the locked door,
then reaches toward the latch.
Framing: Tight medium close-up, case edge visible in the lower foreground.
Camera: Slow push-in, steady, eye-level, restrained.
Lighting: Low tungsten practical from camera left, cool spill from
the case light, soft shadow across her face.
Environment: Rain-streaked station booth, worn metal walls,
paper notices in the background.
References: Character reference controls Mara's face and wardrobe.
Prop reference controls the signal case.
Location reference controls the booth layout.
Constraints: Avoid extra people, bright daylight, modern office furniture,
new props, and comedy tone.
Review criteria: Usable only if Mara's wardrobe stays consistent,
the case remains readable, and the ending frame can cut to an insert.

This reads longer than a quick prompt, but it makes revision easier. If the camera move fails, adjust the camera section. If the prop drifts, revise the reference and constraints. If the beat feels wrong, fix the intent or action.

Give every reference a job

Every Seedance 2.0 reference should have a named job. A character image, prop still, location photo, start frame, end frame, or video reference can help only when the prompt explains what that asset should control during generation and review.

Before generating, label each reference by purpose:

• Character reference: identity, hair, silhouette, age range, wardrobe, expression range.
• Location reference: architecture, room layout, textures, geography, practical lights.
• Prop reference: shape, scale, markings, handling, continuity value.
• Wardrobe reference: color, fabric, fit, wear, damage, weathering.
• Start-frame anchor: the exact composition where the shot should begin.
• End-frame anchor: the composition the shot should resolve toward.
• Reference video: motion, blocking, timing, camera move, or staging rhythm.

Lotix generation workflows support image references and reference videos for shots, with video support centered on Seedance 2.0 and Seedance 2.0 Fast. Teams can build reusable production assets for characters, locations, props, wardrobe, and reference videos, then pull them into shot prompts.

Use references only when they clarify the shot. A close-up may need a character reference and a wardrobe note. An insert may need a prop reference and an end-frame target. A movement-heavy shot may need a reference video more than five extra stills.

Write constraints that protect the scene

Constraints should protect continuity, tone, and editability. Write the few restrictions that matter: unwanted people, wrong wardrobe, prop changes, lighting shifts, modern objects, camera speed, or tone problems. Long vague negative lists usually add noise for the next generated take.

Good constraints use plain, specific language:

• Avoid extra people in the frame.
• Keep the signal case closed until the final second.
• Keep the wardrobe dark green and rain-damp.
• Avoid daylight, clean white walls, modern laptop screens, and comic expressions.
• Keep the camera slow and restrained.

Weak constraints leave the model and reviewers guessing:

• Make it cinematic.
• Do not make it bad.
• Avoid weird artifacts.
• Make everything consistent.

Pair constraints with references, shot intent, and review criteria so the team can see which part of the brief needs revision after each take.

In Lotix, negative constraints can live inside the shot plan with the rest of the brief. That makes them easier to inspect before generation and easier to revise after a take fails.

Plan for takes, not one perfect output

Plan for multiple takes because Seedance 2.0 prompting improves through review. The first output may expose an unclear frame anchor, crowded action, weak reference, or broad constraint. Treat each take as evidence for the next prompt and plan revision.

Review each take against the brief:

• Did the take serve the shot intent?
• Did the subject and action stay readable?
• Did the camera language match the scene?
• Did the important references hold?
• Did the take introduce unwanted objects, mood shifts, or continuity breaks?
• Can the ending frame cut into the next planned shot?

That review language matters. A take can look impressive and still fail the scene. Marking it as rejected, maybe, selected, or approved keeps the team honest.

Lotix turns generated outputs into reviewable takes tied to shots. Successful generations can flow into dailies and review, where directors, producers, editors, and collaborators can compare work in context instead of debating filenames.

A reusable Seedance 2.0 prompt template

Use this Seedance 2.0 prompt template when you need a repeatable shot brief. Fill only the fields that affect generation or review. Short, precise entries usually beat paragraphs that mix camera, story, references, and constraints together for faster revision.

Use this template before generating a shot:

Scene:
Shot code:
Shot intent:
Subject:
Action:
Framing:
Camera:
Lighting:
Environment:
Character references:
Location references:
Prop and wardrobe references:
Frame anchors:
Reference video:
Duration, aspect ratio, and resolution:
Audio or music direction:
Constraints:
Review criteria:

Keep the notes short. The goal is not to fill every field with a paragraph. The goal is to make the shot directable, repeatable, and reviewable.

For one-shot planning, pair this with the Seedance 2.0 shot planning workflow. For connected scenes, use the Seedance 2.0 multi-shot workflow. For API decisions, read the Seedance 2.0 API guide.

Prompting is production design

Seedance 2.0 prompting works as production design when every note ties back to the shot. Keep characters, locations, props, wardrobe, frame anchors, video references, camera notes, lighting notes, constraints, and approvals attached to the work inside the production project.

The best prompt is not always the longest prompt. It gives the model a clear job and gives the team a clean way to judge the result.

That means prompt writing belongs inside the production workflow. When references, approvals, and model settings drift into folders, chats, and filenames, review slows down and spend gets harder to explain.

Lotix gives that work a production home: projects, assets, scenes, shots, takes, and dailies, monthly generation tokens, project roles, and governance workflows built for serious AI film work.

To write Seedance 2.0 prompts like production briefs, sign up free and keep every take tied to the shot it was meant to serve.

Frequently asked questions

Seedance 2.0 prompting works best as a structured shot brief, whether the team uses an API or a production workspace. Teams should separate intent, references, constraints, and review criteria so prompt misses can be diagnosed without rewriting the whole brief.

What’s the best Seedance 2.0 prompt format?

The best Seedance 2.0 prompt format uses a shot brief: intent, subject, action, framing, camera, lighting, environment, references, constraints, and review criteria. This structure keeps the prompt readable and makes failed takes easier to diagnose with less team debate during review.

Should I write one long prompt or separate sections?

Use separate sections for production work. A single paragraph can work for quick tests, but teams need clear fields for references, camera notes, frame anchors, audio direction, constraints, and review standards when several people judge the take during take review.

How many references should a prompt use?

Use the fewest references that clarify the shot. A character close-up may need character and wardrobe references. A prop insert may need a prop reference and frame anchor. More references can add noise when their jobs overlap for the model.

Does Lotix guarantee Seedance 2.0 will follow the prompt exactly?

No. Lotix keeps shot intent, references, generated takes, and review states organized, but Seedance 2.0 can still vary details. Review each take against the brief before approval, then revise the section that caused the miss with clearer next revision notes.

Is this prompt guide only for API users?

No. The same shot-brief logic works for API users and teams using a production workspace. Lotix helps teams keep scene, shot, take, reference, and approval structure around Seedance-focused generation without building that system from scratch by hand for each project.