Build a Character Reference Sheet for AI Animation: Approve the Master First

Decide what the animation will ask the character to do

Before drawing a full turnaround, write a short shot list. Imagine an illustrated fox mascot in a small welcome sequence: it faces a visitor, reaches toward a sign, then turns to leave. This is a planning example, not an animation result. The three actions expose different parts of the design.

The third view is necessary only if the final shot shows that side. A close-up of a face does not automatically require a rear view; a full-body turn does. Conversely, a front portrait cannot settle the shape of the character's back simply because it is high resolution.

Separate orientation from framing. “Side view” describes the angle; “full body” describes what fits inside the image. A cropped side portrait can show the muzzle correctly while supplying no evidence about the feet or tail. Specify both when requesting a reference.

Also decide whether the final output needs generative footage or an editable animation asset. A reference pack guides images and shots; it does not supply a rig, a skeleton or a manipulable 3D mesh. If those are delivery requirements, choose the appropriate animation production workflow before investing in a large collection of rendered views.

Write a design card that can reject an image

“Keep the character consistent” is too vague to review. List a small set of visible invariants: silhouette, facial landmarks, colors, clothing, accessories and identifying marks. Add the parts that may vary, such as expression, pose, camera angle and background.

For the fox example, a useful design card could look like this:

This is an example design specification. Its purpose is to create an observable decision, not to imply that every feature will be preserved automatically.

Asymmetry needs extra care. In a straight-on image, the character's left normally appears on the viewer's right. In a rear view, the page relationship changes. Keep the instruction in character coordinates and place the explanatory label on the review sheet. Do not flip an image just to make a knot appear on the expected side of the page: that can reverse other asymmetric details too.

Use three review states: matches, does not match, and not visible. A scarf covering the chest patch makes part of the patch uncheckable. A tail hidden behind the body does not prove that its bands disappeared. “Not visible” tells you whether another reference or a different shot is needed; turning it into a pass creates false confidence.

Approve the master before using it as a reference

A saved Dreamina case shows why this step matters. On October 14, 2026, three fox stills were generated with Seedream 5.0 Pro. The prompts requested three dark tail bands. The original waving fox visibly had two, and the two later stills also showed two. Both later generations used the original waving image as their reference; one was not derived from the other.

Original still from the October 14, 2026 Dreamina example. The prompt requested three tail bands; two are visible in the output. This image was reused as the reference for the later pointing and raised-foot poses.

The useful diagnosis is that the master was already wrong against the written brief. The later images retaining two bands is different from a correct three-band design losing a band during a later generation. A review that asks only “Does this look like the first image?” would miss the original mismatch.

There are two legitimate decisions. If three bands are essential, reject this image as the production master and correct the design before deriving more views. If two bands are acceptable, explicitly revise the design card and approve that version. Do not leave “three bands” in the written instructions while silently treating a two-band image as the authority.

The same case does not establish a complete turnaround. A wave, a pointing pose and a raised foot are three scene poses, not a verified front, side and rear model sheet. Nor can the raised-foot still establish how the character walks. Those limits determine what additional reference work is needed.

When reviewing your own master, compare it with the design card at a readable size. Check the face and accessory side, then the full silhouette, then smaller marks. A large facial mismatch can change recognition; a small fixed mark can still be essential to the brief. Decide on both before moving forward. Keep rejected candidates out of the folder used for future inputs so an earlier attractive version cannot be selected accidentally.

Create the master and the needed views in Dreamina

The current Seedream 5.0 Pro guide describes the Dreamina route through AI Image, text or an uploaded image, the Image 5.0 Pro model selection, aspect ratio and resolution, followed by generation and download. Use the settings actually available in your account; the preparation method below does not depend on a fixed credit quote or a universal resolution option.

Make one readable candidate first

Open AI Image. If you already have an approved character drawing, use the upload control to add it. Otherwise, begin from a clear text description. Select the available model and choose an aspect ratio with room for the whole character. A wide image filled with empty scenery is less useful here than a composition that makes the face, hands, feet and tail easy to inspect.

Use a plain background and a calm pose for this first candidate. An action pose can hide the design you need to approve. The following is a proposed starting prompt, not a prompt whose outcome has been validated:

Create one full-body reference image of an original orange fox mascot in a soft illustrated style. Use dark paws, a cream chest patch, a black nose and a teal scarf tied on the character's own left side. The tail has exactly three separate dark bands with orange fur between them. The fox stands calmly in a near-front pose. Show the entire ears, hands, feet and tail against a plain light background. Use even lighting. Show one character only, with no labels, scene props or additional views.

Generate a candidate and open it for inspection before downloading it into the approved folder. Evaluate the requested design, not just the overall appeal. If a feature is wrong, revise the candidate or regenerate the master before requesting the next angle. Changing the prompt is a proposed corrective action; only the next inspected image can show whether it worked.

Once accepted, download the master and record a short version name, such as fox-master-01. Keep the prompt and design card beside it. The version name records a decision: this exact image is the reference for the next round.

Derive one required view at a time

Start a new image generation and upload the accepted master as the reference. Request one angle and one framing choice. For example:

Use the attached image as the character identity reference. Create one full-body left-side profile of the same fox, facing toward the left edge of the image. Preserve the accepted proportions, orange fur, dark paws, cream chest marking, black nose, teal scarf and tail design. Keep the character's own left side visible. Use a neutral standing pose, even lighting and a plain light background. Include the entire character and tail. Do not combine several views into one image.

The prompt supplies an intended relationship; it is not proof of identity preservation. Check the resulting profile against the master and design card. Pay attention to details newly exposed by the angle. If the front image never showed the scarf fastening at the back, the new fastening is a design proposal that needs approval.

For a rear three-quarter view, change the angle request while preserving the same identity instructions and accepted master. If a newly approved side view is also useful as an input, give each reference a clear role in a mode that supports it. Avoid adding every attractive candidate without explaining which design is authoritative.

This input discipline is also reflected in Runway's Gen-4 Image References guidance, which discusses reference use and readable starting images. Its named controls and input limits belong to Runway. The transferable preparation principle is to remove ambiguity about what each supplied image represents.

Review expressions after the neutral design

Add an expression only when a shot needs it. For the welcome scene, a mild smile may be enough. A surprised face or an open mouth can expose teeth, eyelids or cheek shapes absent from the master. Approve those as additional design details instead of assuming that a familiar color palette makes them correct.

Keep an expression reference separate from a camera-angle reference where possible. If the only profile is also an exaggerated shouting face, it is harder to tell whether a different muzzle came from perspective or expression. A neutral profile gives you a cleaner comparison.

Assemble a review sheet and a clean input pack

The review sheet is for making decisions. Put the accepted master first, followed by the views your shot list requires. Keep each image large enough to inspect and label its orientation, version and status. Add a short legend for asymmetric details and a list of anything still unresolved. You can arrange this in a document, slide or image editor; it does not require a new generated collage.

A useful sheet might contain four labeled panels: accepted near-front master, accepted profile, rear view awaiting fastening approval, and approved smile. Marking the rear view as pending prevents someone from mistaking a visually complete page for a completely approved design.

The generation input pack serves a different purpose. Export or retain the individual clean images without the review labels. Choose the relevant image when constructing a scene. A multi-panel sheet contains several representations of the character, so it is not interchangeable with a single scene image showing the character in its starting position. Whether a particular model accepts a sheet as an identity reference depends on that mode's documented inputs.

Keep a compact handoff folder with:

• The exact accepted master and its version name.
• Each approved view as an individual image, with orientation in the filename.
• The labeled review sheet and design card.
• A short note mapping the planned shots to the relevant references.
• Any unresolved design questions, clearly separated from accepted assets.

Opening the files is part of the handoff. Confirm that the saved images are the approved versions, the whole character is visible where required, and the filenames match the sheet. Do not promise transparency merely because the background looks plain. If transparent pixels or an editable source are needed, inspect the actual exported file and supply the required asset separately.

Use a small acceptance record to decide whether animation can start

An acceptance record can be brief. The following is an illustrative review, not an additional completed product test:

The result is a shot-level decision, not a single score. If the front view is approved but the rear fastening remains unresolved, you may be able to make the frontal shot while holding the turn-away shot. If the master itself contradicts the approved brief, pause all derived shots that depend on that disputed feature.

Start animation when the identity-defining parts visible in the planned shot have an accepted reference and the scene's starting image has been checked. Save that starting image with the shot, so a later failure can be compared with the exact input. The three-shot mascot workflow follows that reference relationship into multiple generated clips and shows what the saved case can actually establish.

If a problem appears later, locate its first visible occurrence. A wrong detail in the master calls for a design decision. A correct master with a wrong scene still calls for still-image correction. A correct still that changes during motion needs investigation at the animation stage. The character continuity troubleshooting guide develops those branches across the production sequence.

Hand over the decision as well as the images

Before sending the pack to another person, open the shot list and select the image you would actually use for each shot. For the frontal welcome, that might be the accepted master or a scene still built from it. For the side reach, it might be the approved profile plus the planned scene composition. If you cannot choose a suitable input for the turn-away shot, record that shot as unresolved instead of letting the next operator guess.

Add one plain instruction to the handoff: which master is current, which features are fixed, and which references are intended for which shots. If a design changes later, keep the old pack identifiable and mark which downstream shots need rechecking. Changing the scarf fastening in the rear view does not automatically repair a scene image that was already generated with a different fastening.

The pack cannot guarantee consistent motion. It can make responsibility precise: the design was approved here, this image entered the shot, and this visible feature needs review. That clarity is more useful than accumulating additional angles without deciding which version to trust.

Begin in Dreamina with the smallest useful deliverable: one approved master and one additional view required by your next shot. Expand the pack when the story demands it, keeping the written design and the actual images in agreement.