Seedance 2.0 Prompt Guide for AI Film Teams

A strong Seedance 2.0 prompt starts with one rule: write the prompt like a shot brief, not like a wish. The model needs a clear job, a clean reference stack, camera and lighting direction, and a way for your team to judge the take when it comes back.

As of May 21, 2026, ByteDance Seed describes Seedance 2.0 as a multimodal audio-video generation model for short-form video creation. The official launch post and model card describe text, image, audio, and video inputs, while BytePlus maintains ModelArk docs for video generation and prompt writing.

Those inputs are useful, but they don’t remove the filmmaker’s job. This guide gives you a practical structure for writing Seedance 2.0 prompts that fit scenes, shots, references, takes, and dailies.

Key takeaways

• 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

Prompt quality depends on intent. Before you describe the frame, write the reason the shot exists.

A shot may need to 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 becomes the anchor for the rest of the prompt. It tells you what matters and what can be cut. If a wardrobe note, camera move, prop detail, or lighting idea doesn’t serve the intent, it probably belongs in a different shot.

Lotix is built around this 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 so the team isn’t guessing what a clip was meant to do.

Use a filmmaker-first prompt structure

The best Seedance 2.0 prompts are specific without becoming a wall of prose. Think in sections, the way a director, cinematographer, and editor would read a shot brief.

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’s 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’s easier to revise. 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

References can help a prompt, but a crowded reference stack can also create noise. The answer isn’t “more references.” It’s clearer reference roles.

Before generating, label each reference by job:

• 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 also build reusable production assets for characters, locations, props, wardrobe, and reference videos, then pull them into shot prompts instead of rebuilding continuity from memory.

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 are useful when they protect continuity or tone. They shouldn’t become a giant list of everything the model could possibly get wrong.

Good constraints are specific:

• 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 are vague:

• Make it cinematic.
• Don’t make it bad.
• Avoid weird artifacts.
• Make everything consistent.

The model may still vary details. That’s why the prompt shouldn’t carry the whole workflow alone. Constraints work best when they’re paired with references, shot intent, and review criteria.

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

Seedance 2.0 prompting gets better when you expect iteration. The first take may show you that the action is too ambitious, the frame anchor is unclear, or the reference stack is fighting itself.

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 be visually 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 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 isn’t 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

The best prompt isn’t always the most elaborate prompt. It’s the prompt that 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. Characters, locations, props, wardrobe, frame anchors, video references, camera notes, lighting notes, constraints, and approvals should stay attached to the shot. When they drift into folders, chats, and filenames, review gets slower and spend gets messier.

Lotix gives that work a production home: projects, assets, scenes, shots, takes, and dailies, with prepaid token packs, project roles, and governance workflows built for serious AI film work.

To write Seedance 2.0 prompts like production briefs, start creating in Lotix and keep every take tied to the shot it was meant to serve.

Frequently asked questions

What’s the best Seedance 2.0 prompt format?

Use a shot-brief format: intent, subject, action, framing, camera, lighting, environment, references, constraints, and review criteria. It keeps the prompt readable and makes failed takes easier to revise.

Should I write one long prompt or separate sections?

Separate sections are usually easier for a team. A single paragraph can work for quick tests, but production prompts need clear places for references, camera notes, frame anchors, and review standards.

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 a frame anchor. More references aren’t automatically better.

Does Lotix guarantee Seedance 2.0 will follow the prompt exactly?

No. Lotix keeps shot intent, references, generated takes, and review states organized. The model can still vary details, so each take should be reviewed against the brief before approval.

Is this prompt guide only for API users?

No. The same shot-brief logic works whether you’re using a direct API path or a production workspace. Lotix is for teams that want the production structure around Seedance-focused generation without building that system from scratch.