Wan 2.2 Animate Prompts
Turn source-video observations into a Wan 2.2 Animate brief while keeping the driving video, character image, and preprocessing in your chosen animation workflow.
Describe your source clip there, then paste the relevant notes into this text-based tool.
Free · no sign-up · Fast model.
How it works
From video notes to an editable brief
1. Observe the driving clip
Analyze your source on the homepage or write your own notes. Capture the movement sequence, framing, occlusions, and important contact points.
2. Explain the intended adaptation
Paste concise notes and say whether you are planning animation or replacement. Identify what should stay from the motion and what should change in the character.
3. Prepare the real animation inputs
Review the generated cards, then supply the driving video and character image in your selected Wan 2.2 Animate workflow. Inspect preprocessing and the actual result.
Plan a clearer Wan 2.2 Animate brief
Wan 2.2 Animate is not just a text-to-video preset
Wan 2.2 Animate is the focus of this page: preparing a clear character-animation brief from a source video. The broader Wan 2.2 family also includes other generation workflows, but those names should not be treated as interchangeable. The official Animate workflow uses a driving video and a character image. A written description is useful for planning and communicating intent; it does not replace those conditioning inputs or perform their preprocessing. This tool produces editable prompt cards from your notes. It does not run Wan, extract a pose sequence, create a character mask, or upload a reference image to an animation service. If you begin with a clip, use the homepage video analyzer for a written breakdown, then paste a concise selection of its observations here. Your next step is to prepare the real assets in a compatible workflow. That boundary matters more than adding impressive but unsupported claims to the generated text.
Choose animation or replacement before writing the brief
The official Wan 2.2 Animate instructions distinguish animation and replacement modes. Decide which kind of job you are planning before you collect references. Are you primarily asking a character to perform the driving motion, or are you replacing a character within the source scene? Write that decision at the top of your notes. It affects what you need to preserve and which parts of a generated description should be treated as fixed rather than freely redesigned. For an animation brief, describe the intended character and the performance you want to transfer. For replacement, also record scene interactions that must remain plausible: feet touching the floor, a hand holding a railing, or a body passing behind a desk. The planning text cannot repair a poor mask or failed tracking by itself. When a result looks wrong, distinguish a prompt ambiguity from an asset or preprocessing problem before you spend time rewriting every sentence.
Inspect the driving video before generating prompt cards
Choose a reference segment with an action you can describe accurately. Watch where the performer enters and leaves the frame, which limbs are visible, and when important objects obscure the body. A stable framing and a readable action make a useful initial test, even if your eventual project is more complex. This is practical preparation for Wan 2.2 Animate, not a claim that difficult motion is unsupported or that every clean clip will produce a good result. Write a compact movement timeline: the subject begins facing forward, shifts weight to the left leg, raises the right arm, turns toward the window, and settles. Keep the order rather than reducing it to a vague word such as dancing. Distinguish a camera pan from the performer rotating. Note sudden cuts or speed changes because those belong to the source structure, not merely its style. When pasting into this tool, prioritize the moments that must survive the adaptation over decorative scene language.
Match character identity and motion expectations
A character reference and a driving performer may have different proportions, clothing, or silhouettes. Make those differences visible in the brief instead of assuming a motion transfer will ignore them. For example, a long coat can hide leg movement, while a much larger head changes the apparent balance of a pose. Record the target character features that should remain recognizable, including the outline, colors, and essential accessories, without inventing a guarantee of exact identity preservation. The official preprocessing guide recommends pose retargeting for animation mode, especially when proportions differ, and warns that its simplified results need inspection. In replacement mode, retargeting is disabled by default to account for scene interactions. These are workflow considerations, not options provided by our prompt generator. For Wan 2.2 Animate, review the prepared pose and face outputs in the actual implementation before deciding that a new text description is the right fix. Keep the successful asset preparation together with the final brief.
Practical animation decisions
Describe what stays and what changes
A good adaptation brief makes a clear separation between preserved motion and desired appearance. Write that the original arm gesture and timing should remain, while the character becomes the supplied illustrated mascot. Then specify whether the scene should keep the source background or use a new setting in the workflow you selected. Avoid simultaneously asking for an unchanged performance and a completely different body action. Those instructions compete rather than add useful detail. For Wan 2.2 Animate planning, list essential contact points and occlusions as review criteria. A hand must meet the table, a foot should not slide through the floor, and a foreground object should obscure the correct part of the character. The prompt cards can help organize those intentions, but checking actual frames remains necessary. If the selected provider exposes extra text controls, adapt only the relevant parts of the brief to them; do not assume every implementation accepts the same syntax or negative-prompt fields.
Example brief for a character greeting
Example input: I am planning an animation-mode character greeting. The driving clip shows a person standing in a full-body view, raising the right hand, waving twice, and lowering the arm. My character reference is a small orange mascot with round glasses and a blue jacket. Preserve the wave timing and the direction the face turns. Keep the glasses and jacket recognizable. The desired framing leaves room above the raised hand. Treat this as a preparation brief, not a request to produce the finished video here.
Review the example before rendering
Read the generated draft against the source. Remove any invented jump, camera orbit, or extra character. Then provide the actual driving video and mascot image to your chosen Wan 2.2 Animate workflow. Review the processed inputs and rendered result for hand position, character shape, foot contact, and the moment the arm returns to rest. If the silhouette is wrong, examine the reference and preparation first. If the brief contains an unwanted action, revise that instruction before repeating the render.
A repeatable Wan 2.2 Animate workflow
Use broader Wan 2.2 guidance only where it fits
You may have arrived here after reading a general Wan 2.2 prompting tutorial. Some visual planning principles still help: identify the subject, describe the environment, choose a readable composition, and explain the action. But a text-to-video recipe is not automatically an Animate recipe. Do not paste command-line options from another task or assume that a long cinematic paragraph substitutes for a driving clip. Check the task and input requirements in the implementation you actually use.
Keep the experiment reproducible
When the desired result is a new scene without motion transfer, a different Wan workflow may be more appropriate. This page keeps its Wan 2.2 Animate focus because reference-driven character work has different preparation needs. The generated cards are a portable creative brief rather than a universal executable configuration. Record model selection, source files, preparation settings, and actual output together so another person can understand the experiment. A prompt alone is not enough evidence to reproduce an animation result.
Review results without mistaking a draft for a guarantee
Before publishing, watch the whole clip at normal speed and inspect difficult moments more closely. Look for drifting accessories, inconsistent face direction, broken contact points, and background changes around the character. Separate those observations from personal preference: an incorrect hand movement is a different issue from wanting warmer lighting. Change one variable for the next test so you can tell whether it solved the specific problem you recorded.
Check the finished result
This independent Wan 2.2 Animate guide is not a model download hub or a hosted animation renderer. Prompt-tool access does not include GPU time, provider credits, or a promise of unlimited generations. Use assets you are entitled to use and verify the terms of the implementation you select. The practical goal is a concise, accurate brief plus well-prepared references. Keep the prompt editable, retain the source notes, and judge success from the actual animation rather than the confidence of the generated wording.
Questions before you generate
Prepare your animation brief
Prepare a Wan 2.2 Animate brief from video notes. Learn driving clips, character references and mode selection before using a compatible animation workflow.