The standard advice — paste the identical character description into every prompt — is correct only when you have nothing better. If your tool saves references with a handle, call the handle instead. A description you retype varies, because people paraphrase and tidy as they go. A saved reference doesn't vary, because there's nothing to retype.
This is the most repeated piece of advice in AI video prompting, and it's right about the problem and wrong about the fix.
What the standard advice says
Every prompting guide in this category converges on the same instruction. Repeat your anchor elements verbatim in every prompt of a sequence: the same character description, the same style descriptors, the same environmental details.
And the reasoning behind it is correct. Generate five shots from five prompts and you get five different-looking scenes — hair shifts, lighting changes, the palette wanders. The model has no memory between generations, so every fact about your world has to arrive with every prompt or it gets reinvented.
Where this falls short. It solves the problem with the only tool available when your interface is a single text box. Give the same person a reference system and the advice becomes the thing causing the drift.
The advice is right about the disease. It's the best available treatment only when there's no reference system, and a bad one when there is.
Why retyping a description varies
Because people don't paste, they rewrite.
You write "woman in her thirties, short black hair, charcoal suit" for shot one. By shot eleven it's "woman, early thirties, cropped dark hair, grey suit." Not because you decided to change her — because you were writing quickly, or you thought "cropped" was better, or you were working from memory rather than from the clipboard.
Every one of those small edits is a different instruction. The model doesn't know you meant the same person; it reads what you wrote.
And the variations compound. Across seventy episodes the drift isn't one visible jump, which you'd catch. It's a gradual slide that looks fine shot to shot and produces a visibly different person between episode three and episode forty.
What a reference actually does
Replaces the description with a pointer.
On Hexcoded, every character you create or cast saves to your library with an @handle, unique to your workspace. You then call that handle in any prompt, in any tool.
The prompt stops carrying the description. It carries a reference to the description, which is stored once and doesn't change unless you change it deliberately.
That's the whole mechanism, and the consequence is the point: there is nothing left to retype, so there is nothing left to vary.
A description you retype varies. A reference you call doesn't. That's the entire difference.
What the two approaches look like
Same shot, both ways.
Woman in her early thirties, short black hair, charcoal suit, standing at a kitchen window in late afternoon light. She turns her head slowly toward camera. Static shot, no camera movement.
Everything about the character is inline. It will be slightly different next time, because you'll type it slightly differently.
@maya standing at a kitchen window in late afternoon light. She turns her head slowly toward camera. Static shot, no camera movement.
The character is a pointer. The scene description is what's left, and that's the part that should change per shot.
Look at what's left in the second version. Location, light, action, camera. All shot-specific, all things that should differ between shots.
That's the useful side-effect. Removing the character description from the prompt doesn't just stop drift — it makes the prompt shorter and easier to read, so the things you actually want to vary are visible instead of buried in a paragraph you've read forty times.
elementsIt isn't only characters
The same substitution works for everything recurring.
Locations. The apartment your series lives in should be a saved reference, not a paragraph you retype. Same failure mode, same fix.
Styles. The visual treatment — grade, grain, palette, lens feel — held as a reference rather than as a descriptor block you paste and gradually revise.
Elements. Props and objects. The category people forget, and the reason a recurring object stops changing shape between shots.
Each of these is a reference type in the library, each takes a handle, and each removes another block of text you'd otherwise be retyping and quietly editing.
When the standard advice is still right
Two cases, and they're real.
When your tool has no reference system. If you're in a single text box with no way to save anything, repeat the description verbatim and paste rather than retype. The advice exists for a reason.
On a model with no references section. Veo 3.1 Lite has no references field at all, so there's nothing to attach. On that model you're back to description, and pasting carefully matters.
Worth knowing which situation you're in before deciding which approach to use — and worth checking, because reference support varies by model more than people expect.
How to switch over
Four steps, and the first is the only one that takes any time.
Pull every recurring description out of your prompts
Characters, locations, styles, recurring props. Anything appearing in more than two prompts is a candidate. This is the only slow step and you do it once.
Save each one as a reference with a handle
Short, unambiguous, and something you'll recognise at episode forty.
Rewrite your prompts around what's left
Location, light, action, camera. If a sentence describes something that appears in more than one shot, it belongs in a reference rather than in the prompt.
Never re-describe a referenced thing
Adding "she has short black hair" alongside @maya gives the model two sources for the same fact. If you want to change her hair, change the reference.
- The standard advice — repeat the description verbatim — is correct only when you have no reference system
- Retyping varies, because people paraphrase and tidy. Those small edits are different instructions
- Drift across a long series isn't one visible jump. It's a gradual slide you don't notice shot to shot
- A saved reference removes the retyping, so there's nothing left to vary
- Call @handle and let the prompt carry location, light, action and camera — the things that should change
- The same substitution works for locations, styles and recurring props
- Don't use both. A handle plus an inline description of the same thing is a conflict
- The old advice still applies on a model with no references section, like Veo 3.1 Lite
Only if you have no way to save a reference. The advice exists because models have no memory between generations, which is true — but a description you retype varies, and those variations are what produce drift. If your tool saves references with a handle, call the handle instead.
Because people rewrite rather than paste. "Short black hair" becomes "cropped dark hair" by shot eleven, not through any decision but through writing quickly or working from memory. The model reads what you wrote, not what you meant, and across a long series those edits compound.
Everything that should differ between shots — location, light, action, camera. If a detail appears in more than one shot, it belongs in a reference. The useful side-effect is a much shorter prompt where the things you want to vary are actually visible.
Don't. It gives the model two sources for the same fact with no way to reconcile them, which is a conflict rather than reinforcement. If you want to change something about the character, change the reference.
Yes, and they're underused. Locations, styles and elements are all reference types with handles. A recurring room retyped in each prompt drifts exactly the way a character does — it just gets noticed less, because viewers watch faces.
Then repeat the description and paste it rather than retyping. Veo 3.1 Lite has no references section at all, and reference ceilings vary widely across the roster — from fifty down to one. Worth checking your model before assuming either approach.
Save once, call forever
Characters, locations, styles and props each take a handle that works in every tool, on one shared library. Create the description once, and stop retyping it.
See the actor libraryMore on prompt structure, per-tool syntax and common mistakes in Prompts.