APIUp to 25% cheaper than official pricesTry the API →
HermesHERMES
← Creation guides

Official feature

Claude Motion: from a document to an animation

Turn one comparison into an understandable short animation.

A useful animated chart should make a relationship easier to understand. This tutorial pairs the official access and export instructions with a worked editorial exercise: introduce two values, compare them on one scale and hold a clear conclusion. The exercise uses fictional data and is not an independently tested Claude Motion output.

INTERACTIVE STUDYHERMES STUDY · EXAMPLE DATA

A SMALL CHANGE

Make the difference visible.

BEFORE24
AFTER42
04.00 s
120 / 359
12 s · 30 fps · Reveal

Seek to any frame, then return to it: the scene and readout match. Change the curve to compare the pacing. This Hermes teaching study explains a timeline; it is not a tool-generated result or performance benchmark.

What to know before you begin

Who can use it

As checked on October 14, 2026, Motion is in beta for Team and Enterprise. Team has it enabled by default; an Enterprise owner enables it under Organization settings → Artifacts. Check that setting before troubleshooting a missing entry.

Create, revise, export

Choose Motion from Output in a chat, or start with a Motion template in Artifacts. Supply your own material and ask for a short animation. Revise in chat or in the editor, then choose Export → MP4. Longer or more complex work uses more of your plan allowance.

Choose a suitable first project

Try one chart with a clear comparison. Our suggested review: check each number against the input, keep labels on screen long enough to read and hold the final conclusion. The official feature animates code; it is not a generator for realistic footage or people.

From input to delivery, step by step

01Prepare a small, unambiguous source

Use two values with the same unit and time window. Our exercise compares 24 and 42 completed sample tasks. State that the dataset is fictional, define “completed” and forbid adding a percentage improvement unless it is separately calculated and checked. Attach a plain table instead of asking the model to extract numbers from a busy slide.

02Write the message before the motion

The lesson is the comparison, not the decoration. Give the animation one conclusion and three beats: establish the labels, reveal the values, hold the comparison. Keep the same scale throughout. A changing axis can exaggerate a difference even when the underlying numbers are correct.

03Review the first version in two passes

First pause and check the facts: labels, units, values and the conclusion. Then watch at normal speed and judge reading time. If both content and movement are wrong, fix the content first; otherwise every animation revision rests on an unstable message.

04Ask for one controlled revision

Instead of “make it better,” ask to keep the first scene, hold the final values for three seconds and move the caption away from the bars. Name what must remain unchanged. Compare the next result against that request before starting another revision.

05Validate the exported artifact

Open the MP4 outside Claude, then watch it muted at the size where it will be used. Confirm the first frame communicates context and the final frame remains readable. Keep the source table and the final prompt with the export so a later number correction is traceable.

A suggested 15-second storyboard

Use this editorial plan as an editable working document, adapting it to the actual assets and placement.

TimeWhat appearsWhat to verify
0–3 sOne question and two labeled categoriesThe audience knows what is being compared
3–8 sBars reveal 24 and 42 on one scaleValues, units and bar heights agree
8–12 sA concise comparison with the data labelNo invented cause or business claim
12–15 sHold the complete chartEnough time to read on a phone

A complete request to adapt

This is an original example for this tutorial. Replace the placeholders with your task and retain the preparation, review and delivery requirements. Ask the agent to identify missing inputs before production.

Create a 15-second animated comparison for a team presentation. Use only this fictional dataset: sample tasks completed, A=24 and B=42, same reporting period. Label it “Example data.” Use one consistent scale and keep exact values visible. Story: question → values → comparison → 3-second final hold. Do not invent causes, percentages or business claims. First explain the storyboard. After the first draft, allow targeted edits to labels and timing.

Where the process can get stuck

I cannot find Motion

Check the account and organization settings against the current official help page. A missing entry is not fixed by installing the unrelated Motion Director skill.

The chart is correct but hard to follow

Reduce the message to one comparison. Keep the labels visible while the bars move, and leave the final state on screen. Remove motion that competes with the data.

The export differs from the preview

Identify the exact frame and symptom before requesting another export. Check missing fonts, clipped labels and whether the saved artifact is the intended revision.

Finish one small, reviewable output

Walk through the process with your own inputs. Save the first output and specific review notes: what works, what needs changing and how to reproduce it. Once the small test passes, extend the duration, complexity and delivery variants.

References & editorial notes

Consult the original projects for current capabilities, eligibility and setup. Exercises, timings, sample requests and review advice are Hermes editorial work. Creator outputs and teaching illustrations are labeled where shown.