Orelon logoOrelon
Pricing

Prompt Naming Conventions That Keep AI Video Workflows Tidy

Nov 6, 2026 · By Orelon Team

Explore AI video templates

Browse a few community creations for inspiration, then open any template to continue creating in Orelon.

Build a prompt naming system for AI video: slot-based names, versioning, continuity anchors, review loops, and fixes for messy prompt libraries.

A prompt is a small program written in plain language, and like any program it needs a name you can call later. In AI video work that naming decision arrives faster than in text generation. A single shot encodes subject, look, camera behavior, and duration at once, and each render costs minutes rather than seconds. After a week of experimenting you have forty candidate clips. After a month you have four hundred, and the only thing standing between you and a repeatable look is whether you can find the prompt that produced the shot you actually liked.

This guide is about prompt naming for AI video specifically: how to structure names, how to version them, how to keep a library navigable, and how to use names to hold visual continuity across a multi-shot sequence. It avoids theory and focuses on conventions you can adopt in an afternoon, plus the failure modes worth avoiding.

Why a name is production infrastructure

In text generation, a prompt is usually disposable. You write it, you get an answer, you move on. Video behaves differently. Output takes time, results vary between runs, and a successful shot becomes capital you will want to rebuild — for a recut, a resized delivery, or a second campaign with the same look.

There is also a collaboration cost that text work rarely exposes. Video almost never stays with one person. An editor needs to know which shot is the hero and which is the safety take. A client needs to compare option A against option B without watching both three times. A colorist needs to trace where a graded plate came from. A good name answers those questions before anyone opens a file.

The three jobs a prompt name has to do

Every name should serve at least one of these purposes:

  • Retrieval — can you find it with a keyword you would genuinely type under pressure?
  • Distinction — does it separate this version from the seven near-identical siblings beside it?
  • Continuity — does it tell you which shot, scene, or sequence it belongs to?

A name that only does the first job is a label. A name that does all three is a tool.

The cost of a sloppy name shows up late

The damage is rarely immediate. It appears three weeks later when a client asks for the version with the warmer light and you have eleven files that share one vague name. You re-render. The new render drifts. The wardrobe reads slightly different. Now you are matching shots by eye instead of by record, and the sequence loses the quality that made it work.

The four-slot skeleton

The most durable convention for video prompts is a slot-based name: a fixed order of short attributes separated by a consistent character. Four slots cover most work.

hero-sneaker_amber-studio_slow-push_9x16
  • subject — what is on screen (hero-sneaker, courier-night, kitchen-macro)
  • look — the visual treatment (amber-studio, overcast-doc, neon-wet)
  • motion — camera or subject movement (slow-push, handheld-follow, static-lock)
  • format — aspect ratio or delivery target (9x16, 16x9, square)

Four slots are enough because they mirror how decisions actually happen. You choose the subject, pick a look, decide how the camera behaves, then confirm delivery shape. Naming in that order means your file list sorts into something resembling your thinking.

What belongs in the body instead

The name is an index, not a script. Keep lens details, lighting ratios, film stock references, motion blur notes, and negative instructions in the prompt body. If your filename reads like a paragraph, you have created something that is hard to scan and impossible to autocomplete.

A useful test: if you would not say it out loud when describing the shot to a colleague, it does not belong in the name.

The sixty-character ceiling

Most file browsers, prompt panels, and chat windows truncate between forty and eighty characters. A name cut off mid-word is worse than a shorter name that stays whole. Abbreviate aggressively and consistently: pick bg or background, never both in the same library.

Building a vocabulary your team can share

A convention is only as good as the words inside it. Undefined style labels are the most common reason naming systems collapse, because two people assign different meanings to the same token and the library quietly forks into dialects.

Ten to fifteen looks is enough

Most projects do not need a taxonomy. They need a short list written where everyone can see it. Fifteen looks will carry a campaign, a product line, or a short film. Write each one with a half-line description: amber-studio means warm key, deep falloff, controlled highlights. When a new look appears, add it to the list before you use it in a filename.

Characters and locations get permanent identifiers

If a character or location appears in more than one shot, give it a canonical identifier and reuse it verbatim: mara-red-coat, apartment-hallway-b. Never let a second spelling slip in. As far as search is concerned, mara and mara2 are different people, and mismatched identifiers are the leading cause of continuity breaks in AI-assisted sequences.

Decide the separator once

Underscores read cleanly in filenames; hyphens read cleanly in URLs. Choose one, document it, and stop revisiting the decision. The mixed-separator library is a classic symptom of a team that never wrote its rules down.

Versioning without a trail of confusion

Versioning is where naming stops being cosmetic. Three rules keep it legible.

  1. Increment on a creative change, not a settings tweak. A new wardrobe, a different time of day, or a changed lens character earns a new version number. A seed variation or a two-frame trim does not.
  2. Never delete a version that produced a shot you used. Mark it as the pick and leave it in place. Storage is cheap; a lost hero take is not.
  3. Promote long chains. When a version line reaches five or six entries, the prompt has usually drifted into a different idea. Give the winner a new base name and start the count again.

That third rule matters more than it sounds. A chain of eleven versions is a signal that you have been editing an idea that no longer fits, and reading those names later tells you nothing about what changed or why.

Names as continuity anchors in a sequence

This is where prompt naming stops being housekeeping and becomes direction. A sequence is not a pile of shots; it is a set of relationships. Names are how those relationships survive a render queue and a week of iteration.

Lock the nouns, vary the verbs

In each scene, define a small set of anchors — wardrobe, location, time of day, light quality — and treat them as constants in the name. Vary only the camera slot.

kitchen-dawn_soft-backlight_static-lock_16x9
kitchen-dawn_soft-backlight_slow-tilt_16x9
kitchen-dawn_soft-backlight_handheld-follow_16x9

Three names, one scene, three coverage angles. The repeated prefix does the work of a shot list. If one angle needs regenerating, you copy the prefix and change a single creative variable, which is exactly the discipline that keeps a sequence from drifting.

Fork or edit in place

Fork when the change is visible in the final cut: new wardrobe, new time of day, different lens character. Edit in place when the change is technical and invisible: seed variation, slight duration trim, export setting. Forking too often produces a library nobody can read. Editing too often destroys the record of what worked.

Reference-driven and image-to-video naming

When you feed a reference frame or an earlier clip into a model to steer style, record the source in the prompt body and leave a short trace in the name, such as a _ref-b suffix. Image-to-video work benefits from a dedicated lane, and the AI image generator is often where that reference frame is produced, so both libraries should share vocabulary rather than invent parallel terms.

Organizing the library so it stays searchable

Naming solves half the problem; structure solves the rest. A prompt library has two competing needs — browsing and searching — and most people optimize for one and break the other.

Folders should follow the work: client, campaign, sequence. Tags should follow the craft: look, motion, format, subject type. When you tag instead of nesting, one prompt can belong to several contexts without being duplicated. Studying how attribute filtering behaves in a prompt library is a fast way to see why this matters at scale.

The two-field rule

Every saved prompt gets a name and one sentence of intent. One sentence, not a paragraph. Something like: warm interior key with a slow orbit, used for the product hero and the closing packshot. That sentence is what you read two months later when the name alone is not enough.

Archive deliberately

Keep what produced a shot you used, plus the strongest two alternatives per sequence. Everything else is a note, not an asset. A lean library you trust beats a large one you avoid opening, and the pruning instinct gets easier once names tell you what each file is for.

Naming inside the review loop

Most feedback problems are referencing problems. Make it warmer is ambiguous when nobody knows which version is under discussion.

Ask reviewers to cite the name rather than describe the clip: coffee-pour_window-light_slow-orbit_v3 is the one, but the steam reads thin. That single habit removes an entire class of miscommunication and makes revision notes searchable later.

When a decision is close, put both names at the top of a short comparison note with one line each: what the first does better, what the second does better, which one the sequence needs. This is faster than watching both clips three times, and it produces a record you can reuse on the next job. More workflow patterns that pair with a structured library appear across the Orelon blog.

Worked example: a six-shot product teaser

Here is the system end to end on a small real job: one product, one location, six shots, social delivery plus a site cut.

Step 1 — define vocabulary. Subject: bottle. Looks: studio-white, window-warm. Motions: static-lock, slow-push, macro-glide. Formats: 9x16 for social, 16x9 for the site.

Step 2 — write the shot list as names before generating anything.

bottle_studio-white_static-lock_9x16
bottle_studio-white_slow-push_9x16
bottle_window-warm_macro-glide_9x16
bottle_window-warm_slow-push_9x16
bottle_studio-white_macro-glide_16x9
bottle_window-warm_static-lock_16x9

Six names, and the edit is half-decided already: two looks, three motions, two formats, no combination repeated.

Step 3 — generate and version. The macro glide is too fast. Instead of overwriting, produce a second version and mark the first as the alternate. When the client chooses, mark the winner as the pick.

Step 4 — build the sequence. Assemble in shot-list order, using the repeated prefixes as your continuity check. If a shot feels wrong, the name tells you whether you changed look, motion, or format — one variable at a time.

Step 5 — archive. Keep picks and the strongest alternatives, delete dead ends, and write one line of intent per survivor. A six-shot teaser should leave you with around ten saved prompts, not sixty.

Tools respond differently to prompt length and structure, so it helps to browse Seedance 2.5 examples and note how much of each prompt is style versus motion before committing to a template.

Mistakes that quietly cost renders

Mistake Symptom Fix
Generic names test, final, new-final Add subject and motion slots
Mixed separators _ and - in one library Pick one and bulk-rename
Undefined look labels look-a, look-b Write a fifteen-entry glossary
Endless version chains eleventh iteration of one idea Promote the winner to a new base name
No record of the reference Renders you cannot repeat Note the reference in the prompt body
Two spellings of one character Continuity breaks between shots One canonical identifier

If you fix only two rows, fix the first and the last. Generic names cost you time; inconsistent character identifiers cost you the film.

Decision criteria: light rules or a full system?

Not every project needs the same discipline. Use these signals to decide how much structure to impose.

  • Solo, one-off clip — four slots and nothing else. Do not build a taxonomy for a single shot.
  • Client work with revisions — add the one-line intent and versioning rules. Revisions are where names earn their keep.
  • Sequence or narrative — add continuity anchors and canonical character identifiers before generating.
  • Multiple collaborators — write the five decisions into the brief and freeze the vocabulary for the duration of the project.
  • Ongoing brand library — add tags, a look glossary, and a quarterly prune.

If you are still choosing which generation tool should sit behind the system, a structured comparison beats testing five tools blind — the AI video generator alternatives overview is a faster read.

Frequently asked questions

How long should a prompt name be?

Thirty to sixty characters. Long enough for four slots, short enough to stay fully visible in a file browser, prompt panel, or message. Extra detail belongs in the one-line intent note.

Should the model or tool name appear in the filename?

Only if you routinely compare outputs across tools and need to tell them apart at a glance. Otherwise record the tool in the intent note. Tools change; your shots should not need renaming because of it.

Do I need a convention if I work alone?

Yes, for a self-interested reason: future-you is a collaborator with no memory of today's context. Solo creators benefit most from versioning, because nobody else remembers which render was the good one.

What is the difference between a prompt name and a project name?

A project name is a container — a client, a campaign, a film. A prompt name is one reusable recipe inside it. Confusing the two is how libraries end up with forty folders each holding a single file.

How do I name prompts for image-to-video work?

Treat the source frame as part of the subject slot and note the reference in the intent line. Keep the same look vocabulary across image and video prompts so a frame produced in one place is recognizable the moment it becomes motion.

Can naming help with negative prompts?

Indirectly. Group prompts that share exclusions under a common look prefix, then keep the exclusion list in the prompt body. When a look starts producing artifacts, one search finds every prompt using it instead of opening files one by one.

How many prompts should I keep?

Keep what produced a shot you used, plus the two strongest alternatives per sequence. Everything else is a note. A lean library you trust beats a large one you avoid.

Where do storyboards fit in this system?

Before the naming. Sketch or generate the sequence first, then name shots as you commit to them. Naming a shot you have not designed produces plausible filenames for work that never gets made.

Turn named ideas into motion

A naming convention is a small act of production discipline that pays out every time you reopen a project. Once the names are clean, the interesting work starts: designing shots, testing motion, and watching a sequence come together shot by shot. That is where Orelon fits — an AI video generator built for cinematic ideas in motion, with a video creation workspace that keeps prompts, versions, and sequences in one place, and templates when you want a running start instead of a blank page. Bring your naming rules with you; the work moves faster for it.