To prepare reference images for AI video production, give each image a defined production role, identify which details are fixed, and record who supplied or approved it. Organize the package by subject and state, remove contradictory or irrelevant material, and flag anything the team must not infer. Then test the references on a small set of representative shots before using them across the full production.

A large mood board is not automatically a useful reference package. Production needs to know whether an image defines identity, proportion, material, environment, camera language, atmosphere, continuity, or only a general ambition. Without that distinction, two reasonable people can read the same folder differently and approve incompatible results.

Start with the job each reference must do

Reference images can support different decisions. Separate them by function before discussing style:

Reference role What it should help the team decide
Identity Which person, character, product, object, or property must remain recognizable
Construction Shape, proportion, materials, components, wardrobe, or physical relationships
State What changes between scenes, such as costume, damage, season, interface, packaging, or time of day
Environment Geography, architecture, scale, period, surfaces, signage, or spatial anchors
Camera Framing, distance, viewpoint, lens feeling, movement, and subject prominence
Light and color Contrast, palette, source direction, atmosphere, and progression across a sequence
Performance Expression, posture, gesture, energy, or interaction intent
Exclusion Features, treatments, identities, claims, or visual conventions the production must avoid

One image may serve more than one role, but say which role matters most. A portrait may define a face while saying nothing reliable about full-body proportion. A product photograph may establish packaging while offering no useful direction for camera movement. A film still may communicate light and composition without authorizing the production to reproduce its characters or distinctive design.

This classification turns “make it like these” into decisions that can be tested and reviewed.

Mark authority, not just preference

For each important image, record its status. A simple three-level model is enough for many projects:

  • Fixed: an approved source the production must represent accurately, such as current packaging, a licensed character sheet, an approved logo, or a named location reference.
  • Directional: a reference for a quality such as color, framing, texture, pace, or emotional tone. It guides interpretation but is not copied literally.
  • Exploratory: material included to compare possible directions. It should not become a production rule until someone approves it.

Also identify the decision owner. The person who collects references may not be authorized to approve product details, institutional facts, character canon, or identity use. If an image is important but its status is uncertain, label the uncertainty rather than allowing the production team to guess.

Record who supplied scripts, artwork, photographs, logos, likenesses, voices, trademarks, and other protected material, together with the proposed project use. NovMotion’s AI rights and likeness principles describe the site’s production baseline for source authorization, recognizable identity, provenance, and review. They do not establish that a particular use is permitted or replace project-specific agreements and specialist advice where needed.

Build one record for every recurring subject

Do not organize a production package only by where files came from. Organize it around what must recur on screen.

For each character, product, object, or location, create a compact reference record containing:

  • Stable name and identifier
  • Production role and scenes or versions where it appears
  • Approved source files
  • Fixed attributes that must not drift
  • Variables the creative team may interpret
  • Known states and the cause of each state change
  • Views or conditions already covered
  • Missing views, actions, expressions, scales, or lighting conditions
  • Elements that must not be added, removed, or implied
  • Decision owner and current approval status

Use identifiers that remain stable if filenames change. “Hero coat state B” is more useful in shot notes than “final-final-reference-7.jpg.” Stable labels let storyboards, shot records, feedback, and delivery notes point to the same production object.

Cover the views the sequence actually needs

A reference package should be designed around the planned screen work, not around the images that happen to be available.

If a recurring character appears in close-up, profile, full body, motion, and interaction, a single front portrait leaves critical questions unanswered. If a product must rotate, open, display a control, and remain readable in a hand, a packshot alone does not define those states. If an environment supports a pursuit or conversation, isolated beauty images may not establish usable geography.

Compare the planned beats or storyboard with the reference record and identify missing evidence. Typical gaps include:

  • Side, back, high, low, near, or distant views
  • Scale relationships between subjects
  • Hands, accessories, connections, hinges, or moving parts
  • Expressions and body language needed by the story
  • Before-and-after continuity states
  • Day, night, weather, or practical-light conditions
  • Exact text, interface, packaging, or signage states
  • Interaction between two recurring subjects

Do not fill a factual gap with an attractive guess. Ask the responsible owner for an approved source, simplify the shot, keep the uncertain area off screen, or choose a method that can preserve the required evidence.

Separate literal references from visual analogies

Many useful references are analogies rather than instructions to reproduce a scene. A team may like the quiet tension of one image, the color separation of another, and the camera distance of a third.

State the transferable quality in plain language:

  • “Use the large negative space and small subject scale.”
  • “Keep warm practical light against a cooler environment.”
  • “The product remains dominant while supporting action stays soft.”
  • “Performance is restrained; avoid exaggerated expression.”

Avoid labels such as “premium,” “cinematic,” “epic,” or “modern” without observable criteria. They describe a reaction, not a production rule. Ask what in the image creates that reaction and whether the answer belongs to composition, materials, light, motion, edit, sound, or narrative context.

This step also reduces accidental copying. The production can translate an approved principle without treating every distinctive object, character, costume, or composition in a reference as reusable material.

Resolve contradictions before shot production

Reference packages often contain conflicts: different product generations, several character costumes, incompatible architectural periods, mixed aspect ratios, or lighting examples that imply different worlds.

Create a short conflict log. For each conflict, record:

  1. The images or rules that disagree
  2. The production decision affected
  3. Which source has authority
  4. Who resolves the conflict
  5. The approved result and date

Do not solve every difference by averaging the references. Combining several unrelated designs can produce a new result that satisfies none of them. Choose a hierarchy, define intentional state changes, or keep separate visual directions for comparison until one is approved.

Negative references can help when they are precise. “Do not use glossy plastic surfaces” is actionable. “Not this vibe” is not. Explain the observable feature to avoid and whether the restriction applies globally or only to a particular subject, market, or scene.

Prepare files for reliable review

Keep source quality and review convenience separate. Retain the best available source file, but provide a contact sheet or index that stakeholders can scan without opening an undocumented folder.

Each indexed item should include:

  • Stable identifier
  • Thumbnail and source filename
  • Subject and reference role
  • Fixed, directional, or exploratory status
  • Short instruction describing what to use
  • Short instruction describing what not to infer
  • Source or supplier record
  • Approval owner and status

Preserve original files where appropriate and avoid repeatedly exporting compressed copies as if they were masters. At the same time, do not assume that higher resolution fixes a weak reference. A sharp image can still show the wrong product version, hide a required angle, contradict canon, or lack authority.

For sensitive or confidential material, agree on an appropriate project channel, access, and retention approach before transfer. The site’s privacy information asks enquirers not to send confidential source materials until an appropriate channel has been agreed.

Test the package with representative shots

Before scaling production, choose a small test set that exercises different reference demands. It might include:

  • A close identity shot
  • A wider shot that tests body, object, and environment scale
  • A recurring subject under different light or from a difficult angle
  • An interaction or state change
  • A shot containing exact product, text, interface, or canon details

Define the acceptance questions before producing the test. Can reviewers recognize the fixed subject? Are construction and materials coherent? Does the environment support the required action? Are state changes readable? Can the team distinguish intentional interpretation from an error? Do the references provide enough information to repeat the method?

Review the shots as a sequence where continuity matters. A single successful frame does not show whether identity, spatial relationships, lighting logic, or product state will survive the edit.

NovMotion’s six-phase production workflow places visual definition before a representative pilot and scale delivery. The reference package should therefore help the pilot expose uncertainty, not hide it behind an easy or unrepresentative image.

Know what references cannot prove

A thorough package cannot guarantee exact consistency across every generated shot. It cannot by itself prove source authorization, settle copyright or likeness questions, guarantee a platform decision, or predict audience and commercial results.

References also cannot make every shot suitable for an AI-native method. Exact interfaces, small typography, complex product mechanics, sustained physical interaction, documentary evidence, and highly specific performance may require controlled source elements, compositing, traditional capture, or another production approach.

Project scope, schedules, approval stages, deliverables, usage rights, confidentiality, and responsibilities must be defined for each engagement. The website terms explain why general site information is not a substitute for a project-specific proposal or agreement.

Decision guidance for commissioning teams

The reference package is ready for visual development when every recurring subject has a stable record, important images have a defined role and authority level, contradictions have owners, missing views are visible, and reviewers can state what must remain fixed versus what may be interpreted.

Return to strategic intake when the audience, release use, source authority, or central creative direction is still unresolved. Move into a representative pilot when the rules are clear but the team still needs evidence that they work across actual shots. Choose controlled capture or a hybrid method where the release depends on literal proof that visual references alone cannot guarantee.

Do not measure package quality by image count. Measure it by whether the production and review teams can make the same decision from the material. To discuss a reference-led production with NovMotion, share the audience, intended use, source types, recurring subjects, fixed details, planned formats, and hardest representative shot through the project enquiry page.