Wan 2.2 Animate Guide: Move vs Replace, Input Rules, and What to Fix First

If your real job starts from an existing motion pattern, not from a blank prompt, Wan 2.2 Animate is one of the clearest tools in the Wan stack.

That is why people keep searching:

• wan 2.2 animate guide
• wan animate
• wan 2.2 character replacement
• animate move vs animate replace

They usually do not want a broad “what is Wan?” explainer.

They want one practical answer:

Should I use animate move or animate replace, and what do I need to upload?

This guide answers that directly for the workflows available on wan27.org.

The Short Answer

Use animate move when the source motion is the thing you want to keep and the image is the new visual driver.

Use animate replace when the real job is swapping a visual element inside that existing motion pattern.

On wan27.org, both modes:

• require one source video
• require one image
• generate a fixed 1-second output
• support 480p, 580p, and 720p

That makes Wan 2.2 Animate less like a full narrative generator and more like a narrow transformation utility.

Wan 2.2 Animate vs the Two Nearby Alternatives

Before you go further, separate these three intents:

This is the easiest mistake in Wan search results.

People search “animate”, but sometimes the job is really speech-driven avatar video.

Or they search “replace”, but the real need is a bigger reference-led workflow with editing and longer output.

What Wan 2.2 Animate Actually Means on wan27.org

On this site, Wan 2.2 Animate is the shared name for two source-media workflows:

• Animate Move
• Animate Replace

Both workflows are built around the same contract:

• upload one source video
• upload one image
• generate a short output to validate the transformation

That structure matters.

Unlike prompt-led video generation, these modes do not ask you to invent the whole shot in text.

The source video already carries the movement logic. The image carries the new visual layer.

That is why users searching this topic often care about:

• motion transfer
• character replacement
• identity consistency
• source video quality
• whether they need ComfyUI or just a browser workflow

Animate Move vs Animate Replace

This is the decision most users need first.

Use Animate Move when motion is the anchor

Choose animate move when the existing motion pattern is already right and you want to carry that motion into a new visual setup.

That usually means:

• motion preview from a template clip
• stylized motion tests from a performer video
• quick character movement validation
• short transformation previews where the movement matters more than the scene rewrite

In plain English:

keep the movement idea, change the visual driver

Use Animate Replace when replacement is the anchor

Choose animate replace when the real task is replacing a person or visual element inside an existing motion pattern.

That usually means:

• character swap tests
• replacement-oriented previews
• scene-preserving motion experiments
• quick checks for whether a new subject fits the original action

In plain English:

keep the motion pattern, swap the visual element

Current Output and Pricing on wan27.org

On wan27.org, both animate workflows are intentionally small and direct.

Output profile

• fixed 1-second output
• 480p
• 580p
• 720p

Current pricing

That pricing model is useful for one reason:

you can validate the transformation idea cheaply before you move to a larger workflow.

This is not the lane for “make me a full polished final scene.”

This is the lane for “does this motion-carry or replacement idea work at all?”

How to Use Wan 2.2 Animate Without Overthinking It

Keep the process simple.

Step 1: Decide whether the job is move or replace

Do this before touching settings.

If your sentence starts with “keep the movement, but...”, you are probably in the right place.

If your sentence starts with “make a longer cinematic clip from scratch...”, you probably want a different model.

Step 2: Start from clean source media

This matters more than clever prompting.

Your source video should have:

• readable subject motion
• stable enough framing
• clear separation between the thing that moves and the background
• no unnecessary noise or blur if you can avoid it

Your image should have:

• a clear subject
• enough detail to hold up during the transfer
• a look that does not fight the source motion too hard

Cleaner input makes these narrow workflows behave more predictably.

Step 3: Use the 1-second output as a decision tool

This is the mindset shift.

Do not treat the 1-second clip like the final deliverable.

Treat it like a fast preview that answers:

• is the motion read working?
• is the replacement plausible?
• is the image choice good enough?
• is this worth pushing into a bigger workflow?

That is where Wan 2.2 Animate earns its place.

What to Fix First When Results Look Wrong

This is another big search intent around Wan 2.2 Animate.

Most bad outputs come from expectation mismatch, not from mysterious model behavior.

Problem 1: “The output feels broken or messy”

Usually the source video is doing too much.

Fix this first:

• pick a cleaner source clip
• reduce background chaos
• use more readable body movement
• stop testing with the hardest possible shot first

Problem 2: “The replacement does not feel natural”

Usually the new image and the source motion are fighting each other.

Fix this first:

• choose an image that matches the motion logic better
• use a clearer front-facing or readable subject image
• test a simpler motion pattern before a harder one

Problem 3: “I expected a full usable scene”

That is the wrong success criterion.

On this site, Wan 2.2 Animate is a fixed 1-second utility workflow.

Use it to validate motion-carry or replacement direction.

If the job needs longer output, broader shot planning, or revision loops, step up to a larger workflow after the preview works.

Problem 4: “I really needed a talking-head clip”

Then you probably wanted Wan 2.2 Speech to Video instead.

That workflow is built for:

• one portrait image
• one speech audio file
• short talking-style clips
• up to 10 seconds in this project

Current speech-to-video pricing on the site is:

• 5 credits/sec at 480p
• 8 credits/sec at 580p
• 11 credits/sec at 720p

If the job is speech-led, that path is cleaner than forcing Animate to behave like an avatar tool.

Do You Need ComfyUI for Wan 2.2 Animate?

Search results around this topic often lean hard into ComfyUI.

That makes sense. Many advanced users want node-level control, source-video preprocessing, masking, and local workflow tuning.

But the better question is simpler:

What problem are you solving first?

Use a browser workflow first when you want to answer:

• is this a move task or a replace task?
• does my source media work at all?
• is the transformation idea worth pursuing?

Use a more advanced local workflow when you already know the concept is valid and now need:

• heavier preprocessing
• custom node chains
• deeper source-video surgery
• more workflow-specific control

So the real rule is:

validate the job in the simplest workflow first.

Then add local complexity only if the job proves itself.

When Wan 2.2 Animate Is the Right Tool

Wan 2.2 Animate is a strong fit when:

• the project already starts from a source video
• the motion pattern matters more than prompt creativity
• you want a fast operational preview
• the job is narrow enough that 1 second is enough to validate the idea

It is especially useful for:

• template motion previews
• character swap experiments
• stylized motion-carry tests
• replacement validation loops
• operational content workflows where fast yes/no checks matter

When You Should Use Something Else

Do not force Wan 2.2 Animate into a bigger role than it has.

Choose a different workflow when you need:

• longer output
• prompt-led scene invention
• first-frame and last-frame control
• reference-heavy continuity
• revision and editing after generation

That is where the wider Wan stack becomes more useful.

Start with Wan 2.2 if you still need a task-specific family view, or compare the bigger control jump in Wan 2.2 vs Wan 2.7.

Bottom Line

If you only want the fast rule:

• use Animate Move when motion should carry through
• use Animate Replace when the visual element should change inside that motion
• use Speech to Video when the job is really portrait + audio
• use a bigger Wan workflow when 1 second is not enough

That is the practical value of Wan 2.2 Animate on wan27.org.

It is not a catch-all generator.

It is a small, clear, useful tool for source-media transformation jobs.

If that is your job, start with Wan 2.2 Animate and validate the motion idea fast.