
Most AI video that looks "off" is not failing because the model is weak. It fails because two completely different jobs were compressed into a single prompt. Someone writes one dense paragraph describing a ruined cathedral, a tired knight, golden hour light, a slow dolly-in, and anamorphic flare — then wonders why the result feels like a screensaver instead of a shot.
The cathedral, the knight, and the wear on the armor belong to production design. The dolly-in, the flare, and the hour of light belong to cinematography. When you ask a generative model to solve both at once, it negotiates between them, and the negotiation usually lands somewhere forgettable. The set gets simplified so the camera move can happen. The lighting gets generic so the character stays recognizable. You end up with neither a designed world nor a deliberate camera.
The fix is structural, not magical. Separate the two disciplines into distinct passes, define what each pass is allowed to control, then reconcile them. This article lays out that workflow in detail: what production design means in an AI pipeline, what cinematography means when the camera is a prompt, how to keep characters and sets consistent across shots, how to pick tools by capability rather than marketing, and how to review output like an editor instead of a gambler.
In traditional filmmaking, the split is clean and well understood. In AI video, it blurs constantly because both jobs are expressed through the same interface: text, reference images, and a handful of parameters.
Production design answers a set of questions about the world before anyone decides where to put the camera:
In an AI pipeline, these answers become your world state: a written and visual reference set that every generation must respect. If your world state is vague, the model invents. If it invents differently in shot 3 than in shot 12, your film breaks.
Cinematography answers a different set of questions:
None of these change the world. They change how the world is seen. That distinction is the entire basis of the workflow below.
They overlap in exactly one place: mood. Design proposes a mood through the environment, and cinematography proposes a mood through light and framing. When you describe mood in a single prompt, the model satisfies it through whichever lever is cheapest — usually a global color grade. That is why so many AI clips feel like the same teal-and-orange filter applied to different sets. Splitting the two passes forces the model to satisfy the mood twice, from two different directions, which produces depth instead of a filter.
The workflow that holds up under real production pressure has three passes. Each pass has one job, and you do not let a later pass rewrite an earlier one.
Generate or assemble still frames of your world with the camera treated as incidental. You are not making shots yet. You are making evidence that the world exists. Use wide, neutral, evenly lit compositions — think architectural survey photography rather than cinema. These frames become your canonical reference set.
Output of this pass: a folder of stills representing locations, costumes, props, and character faces, plus a one-page written style guide.
Now introduce cinematography. Take your approved design frames and treat them as plates. Generate the shot with camera language applied: lens, height, movement, light direction, and exposure. Because the world is already fixed by reference, the model has fewer variables to improvise, and the camera decisions become the visible variable.
Output of this pass: 2–4 variations per shot, all sharing the same world state but differing in camera treatment.
Compare the capture variations against the design frames. Three things go wrong at this stage: the camera treatment has quietly altered the set, the lighting has altered skin and costume color, or the movement has destroyed detail in the background. Fix each by adjusting one variable at a time, never by rewriting the whole prompt.
Output of this pass: locked shots, plus a written note of which variables you changed, so you can repeat the fix elsewhere.
A world bible is only useful if it is machine-compatible. Poetic language is for the pitch deck; the bible needs to be precise enough that two different sessions produce compatible results.
Define a primary palette of three colors with named references, a secondary palette of two, and an explicit exclusion list. "Warm palette" is useless. "Ochre, oxidized copper, bone white; secondary slate grey and dried-blood red; no saturated blue anywhere" is usable.
Materials deserve the same treatment. Instead of "futuristic city," write "brushed aluminum panels, matte black rubber gaskets, glass with visible dust film, no chrome, no holograms." Materials drive how light behaves, which means they also constrain your cinematography in useful ways.
Models are bad at spatial memory across shots. Fix this with geography, not adjectives. Write a short floor plan in words: "The workshop has one door on the left wall, a workbench along the back, and a barred window on the right; the city is visible only through that window." Then, in every shot, state which direction the camera faces relative to those landmarks. This single habit eliminates most continuity errors before they happen.
Choose two or three specific imperfections that recur across the whole project: a chipped tile pattern, rain streaks on the lower third of a wall, scarred wood on the left side of the bench. Repetition of a specific flaw reads as a real place. Repetition of a generic flaw reads as noise. Pick details that are visually small but unmistakable.
Cinematography is where most prompts collapse into vague mood words. Replace mood words with craft vocabulary. It gives the model a narrower target and gives you a better diagnostic when something looks wrong.
Vague words like "cinematic" and "moody" are not instructions; they are hopes. Specific words like "hard backlight, subject in silhouette, lens flare from a practical behind the shoulder" are instructions.
Describe the move in physical terms and the mount it implies. A slow push on a gimbal, a locked-off tripod shot with subject movement only, a handheld follow with slight breathing, a crane rise revealing the scale of the room. Add the shutter character when it matters: crisp and stutter-free, or slightly smeared long exposure. Movement should serve the information in the shot — if the move does not reveal or conceal something, cut it.
A shot list is the contract between your two departments. Every line should separate what must stay constant from what is allowed to change.
| Field | Belongs to | Example |
|---|---|---|
| Location state | Design | Workshop interior, evening, door on left |
| Costume and props | Design | Oil-stained canvas apron, brass calipers in right hand |
| Palette | Design | Ochre, oxidized copper, bone white |
| Framing | Camera | Medium, camera at chest height, subject camera-left |
| Lens behavior | Camera | Long lens compression, shallow focus on hands |
| Lighting | Camera | Hard backlight through barred window, no fill |
| Movement | Camera | Slow push in, 2 seconds of travel |
| Duration and beat | Camera | 3 seconds, ends on the calipers |
When a shot fails, this table tells you which column to edit. If the room changed, fix the design reference, not the camera line. If the lighting went flat, fix the camera line, not the reference set.
Consistency is not one feature; it is the result of several habits stacked together.
Generate a small set of anchor frames per character: front, three-quarter, profile, plus one full-body shot in costume. Use the same references in every shot involving that character. Avoid mixing references from different generations, even if both look good — the model will average them and produce a third, slightly wrong face.
You want identity to persist and pose to be free. That means locking facial structure, hair, and costume details while explicitly allowing body orientation and expression to change per shot. If identity drifts, tighten the reference set. If poses look stiff and repetitive, loosen the pose instruction rather than the identity anchor.
Track props the way a script supervisor would. Write down which hand holds the object, whether a jacket is open or closed, whether a wound is bandaged yet. Then check each generated shot against that list before approval. It takes thirty seconds per shot and saves entire reshooting sessions later.
Every few weeks a new video model claims the throne. The practical question is narrower: which model solves the specific problem in front of you?
Run the same short test battery on any candidate tool:
Score each test on a simple scale and keep the results. A tool that wins on faces but loses on material description should be used for character coverage only, with a second tool handling environments. Hybrid pipelines are normal, not a compromise.
Use image generation for the design pass — it gives finer control over still composition and is faster to iterate. Use video generation for the capture pass, where motion and temporal coherence matter. Use upscaling and cleanup tools for the reconciliation pass. Keep the boundaries clear so you never ask one tool to do a job another does better.
Watch every generated shot three times with a single question each time:
A shot can pass the first two and fail the third. Those are the expensive ones to catch late.
Keep a running fix list with one line per defect and the variable that caused it. Over a project, patterns appear: if sixty percent of your fixes are lighting-related, your lighting vocabulary needs sharpening rather than your model choice. Treat the fix list as a diagnostic tool, not a chore list.
For anything longer than a single clip, yes. Half a page is enough: palette, materials, geography, and two recurring imperfections. The document's value is that it stays constant while your prompts evolve.
Both approaches work. Stills-first gives tighter control over composition and cheaper iteration. Direct video generation gives better motion realism from the start. Many teams do stills-first for hero shots and direct generation for coverage.
Two to four. Fewer and you accept compromises too early. More and you spend your review time comparing near-duplicates instead of improving the shot.
Reduce the number of references to the smallest set that still captures identity, use identical lighting direction where possible, and avoid extreme angles until consistency is stable. Consistency usually breaks because the model is solving too many unknowns at once.
Decide which one carries the story beat. If the room's condition matters, keep the design and simplify the camera. If the move matters, keep the camera and simplify the set dressing in that shot only. Never sacrifice both.
Yes, but keep the design block and the camera block as separate sections in the template. That way you can swap camera treatments without touching world state, which is the entire point of the workflow.
With a solid reference set, a simple shot usually lands in two or three iterations. Complex shots with movement, crowds, or detailed hands take longer. Budget for the outliers and treat the average as a rough guide only.
On short projects, yes — but do them in sequence, not simultaneously. Write the design brief first, approve it, then switch into camera mode. Role-switching mid-prompt is what produces muddled frames.
Work through those nine items and the difference is immediate. Shots stop feeling like lucky accidents and start feeling like decisions. The visuals hold together across a sequence because the world was designed once and the camera was chosen deliberately for each moment — which is exactly how visual harmony has always been made, whatever tool happens to be rendering the frames.

Alexander
Vidu Q4 alternatives compared: Kling 4.0, Seedance 2.5, Wan 3.0, and Runway Gen-4 — 4K support, input modes, durations, audio, and what each costs in credits on Domer.
The top 4K AI image generators on Domer compared: Flux 3 Klein, Nano Banana 2.1, GPT Image 2.5, GPT Image 2, and Nano Banana Pro — 4K credit costs, reference limits, and speed.
Nano Banana 2.1 vs GPT Image 2.5 Flare compared: credit costs per resolution, aspect ratios, reference images, text rendering, and which tasks fit each model.