Runway is Claude Motion’s launch partner: a practical hand-off guide

Runway announced on launch day, October 8, that it is a launch partner for Claude Motion. Any animation made in Motion can be exported to Runway and finished there: generated footage added around it, sound laid on top, and the whole piece edited and reformatted for wherever it will be published. This post explains what the partnership actually covers, how the hand-off works step by step, and how to decide whether a given video is worth taking out of Claude at all.

We stick to what Anthropic and Runway have published. Where something has not been documented yet, we say so, and where we offer our own workflows and example briefs, we label them as ours.

What the partnership is

Runway’s own framing is short: “Edit and augment animated explainers made in Claude with Runway.” In its announcement, Runway says any Claude Motion animation can be exported to Runway to add generated footage and edit the full piece. Inside Runway, you can generate new video and images, edit clips by describing the change you want, and use Runway Agent to plan and assemble a longer cut around the animation.

Runway lists four editing capabilities that apply once the animation arrives: restyle it; add videos, images and sound; edit it scene by scene; and reformat it for every channel. It also lists four team use cases — launch videos, onboarding, all-hands explainers and multi-channel distribution — which we turn into worked workflows further down.

Runway’s launch video, posted from its account on X, puts it even more simply: “Runway is now in Claude Motion. Create your motion designs in Claude, then export them to Runway. Available now.” The demo in that video shows the route: Share, then Send to Runway.

Oct 8

Partnership announced, 2026

7

Export destinations Anthropic lists

4

Team use cases Runway highlights

10/31

Sign-by date in Runway’s enterprise offer

Anthropic’s own announcement names Runway alongside Adobe, Descript, HeyGen, Higgsfield, invideo and Luma AI as places a Motion animation can go next, with Canva and Captions listed as coming soon. Runway is the partner that has published the most detail about what happens after the export, which is why it is the natural first destination to understand.

Why Claude Motion needs a partner

Claude Motion is deliberately narrow. Claude builds each animation as code that animates text, charts, shapes and images, and the result plays like a short video. Because it is code, you can change one word, one number or one timing and the rest of the animation stays the same. That is the core strength: your figures are the figures you supplied, and a correction does not mean regenerating the whole piece.

The trade-off is spelled out in Anthropic’s announcement: Motion has no video generation model, so there is no generated footage and there are no AI-generated people. Audio inside Motion has not been documented either, and MP4 is the only export format the Help Center describes. In our view, that makes Motion an excellent tool for the structured half of an explainer — the chart, the stat, the step, the caption — and leaves the cinematic half to someone else.

The two tools cover different parts of the same job rather than competing for it: Motion is where the facts live, Runway is where the atmosphere is added.

The hand-off, step by step

Here is the flow as the two companies describe it, with our notes on what to do at each stage.

1. Build and finish the animation in Motion

   Start from any chat, Output → Motion, or a Motion template. Brief it with the audience, where it will play and roughly how long, and attach your report, data or images. Refine in chat or in the editor until every number and word is right.

2. Open Share

   Animations are private by default and live in your Artifacts tab. Runway’s launch demo shows the export starting from Share.

3. Send to Runway

   The demo shows a Send to Runway option. From there, in our reading, the animation becomes material for a Runway edit rather than a finished file.

4. Generate around it

   In Runway, generate new video and images, or describe the change you want to a clip. For longer pieces, Runway Agent plans and assembles a cut around the animation.

5. Finish and reformat

   Restyle, add sound, edit scene by scene, and reformat the piece for each channel before publishing.

Two practical points follow from this order. First, finish the facts in Motion before you send anything. Motion is the place where a figure can be changed without side effects; once the animation is one layer in a larger Runway edit, a late correction means going back to Motion and repeating the hand-off. Second, keep the Motion artifact. Because it stays in your Artifacts tab, you can reopen it, change a number and export again — which is exactly how you would handle next month’s version of the same video.

Four team workflows, worked through

Runway highlights four team use cases. Below, each one is turned into a mini-workflow. The use cases come from Runway; the example briefs and the step-by-step suggestions are ours, written to show how the division of labour plays out in practice.

1. Launch videos

Runway’s example: animate headline stats such as battery life or speed gains, then add product shots generated from a single reference photo.

Our example Motion brief:

Make a 20-second launch animation for our website and social posts.
Use the attached spec sheet. Three headline stats count up one at a time:
battery life, charging speed, weight. End on the product name and our logo.
Bold pace, dark background, our brand orange for the numbers.

In Runway, the plan is to keep the stat sequence intact as the spine of the video and build around it: generate product shots from your one reference photo for the opening and the gaps between stats, then add music. The numbers came from your spec sheet in Motion, so the main new risk is the generated product shots, which need a careful look against the real product; still glance at the stats after any restyle.

2. Onboarding walkthroughs

Runway’s example: add generated scenes of customers using the product between the steps of a walkthrough.

Our example Motion brief:

A 45-second setup walkthrough for new customers, from these 4 screenshots.
One step per scene, with a short caption and a highlight on the button to press.
Calm pace, hold each step for at least five seconds.

In Runway, insert short generated scenes between the steps — someone at a desk, a phone notification arriving — so the walkthrough feels less like a slideshow. Keep those scenes short and clearly decorative; the screenshots carry the instructions. If the interface changes later, update the screenshot in Motion and repeat the hand-off rather than trying to patch the Runway edit.

3. All-hands explainers

Runway’s example: add voiceover and music to an all-hands explainer. This matches one of Anthropic’s own example uses for Motion: a 30-second all-hands explainer built from a quarterly report.

Our example Motion brief:

Turn the attached Q3 report into a 30-second explainer for our all-hands.
Lead with revenue growth, show the three regional figures as bars,
end on the Q4 goal. Calm pace, purple accents, leave room for a voiceover.

In Runway, add a voiceover script that follows the scene order and a music bed underneath. Our tip: write the voiceover after the animation is locked, reading off the final numbers in Motion, so narration and screen never disagree.

4. Multi-channel distribution

Runway’s example: reformat a 16:9 explainer into vertical and square versions, and localize the voiceover for regional teams without rebuilding the animation.

Our example Motion brief:

A 30-second 16:9 product update for our blog and YouTube channel.
Three shipped features, each with one screenshot and a one-line caption.
Keep important text away from the left and right edges.

That last line is our own precaution: if the master will be cut down to vertical and square in Runway, keeping key text near the centre should make the reformat easier. In Runway, create the vertical and square versions, then produce regional voiceovers. The animation itself is built once; only the sound and the frame change per channel and per region.

When the hand-off is worth it

Not every Motion animation needs to leave Claude. Exporting an MP4 straight from Motion is quicker and keeps the whole piece in one editable place. In our view, the hand-off earns its extra steps when at least one of these is true:

• The video needs sound — narration, music or both — since audio inside Motion has not been documented.
• It is public-facing and would feel thin with only animated text and charts.
• It needs imagery you do not have: product shots, people, places or scenes that a video model can generate and Motion cannot.
• It must ship in several aspect ratios or several languages.
• It is longer than a single explainer and needs a cut assembled around the animation, which is what Runway Agent is described as doing.

A plain MP4 is usually enough when the animation will sit inside a slide, play silently in a meeting, or be watched by colleagues who care about the figures more than the production. A chart reveal for a board deck is the classic example: adding generated footage to it would, in our view, distract from the one thing the board needs to see.

A sensible first test is to take one video you already make regularly — a monthly recap, say — and produce it both ways once. If the Runway version is noticeably better for its audience and the extra time is acceptable, make it the default for that video type; if not, stay in Motion.

Division of labour and review tips

The cleanest way to run the hand-off is to give each tool a clear job and not let them overlap. Here is the split we recommend.

Keeping numbers in Motion matters because that is where they are exact. Motion draws the values you supply; a generative model in any tool creates new pixels. If a figure ends up being re-created or restyled in a generative step, check that it still reads correctly.

A review routine that fits this split:

• Review one, in Claude. Share the animation with the colleague who owns the numbers. In Anthropic’s launch video, teammates comment directly on the animation and steer it together; use that stage to settle every figure and caption before export.
• Review two, in Runway. Look only at what Runway added: do the generated shots look right for the product, does the voiceover match what is on screen, do the vertical and square cuts still show every key number?
• Localize with sound, not rebuilds. Runway’s multi-channel use case says the voiceover can be localized for regional teams without rebuilding the animation. If on-screen text must also change language, that is a Motion edit — change the words, export, hand off again.
• Version from the source. When next month’s figures arrive, edit the Motion artifact, not the Runway project, and repeat the hand-off.

What it costs

There are two separate bills to think about. On the Claude side, Motion is a beta feature on Team and Enterprise plans and counts toward your plan’s usage limits; longer or more complex animations use more than a typical message. Our pricing guide covers seat prices reported at launch. Keeping first drafts short and finishing them before the hand-off avoids spending usage on versions you will throw away.

On the Runway side, generation and editing happen in Runway, under Runway’s own plans and terms. Runway has not published Claude-specific pricing in its announcement, and we do not quote Runway prices here — check Runway’s site for the plan that fits how much footage you expect to generate.

In our view, the cost question is mostly about volume: a handful of public videos a quarter is a small add-on, while sending every internal recap through Runway adds a second bill and a second review each time.

How Runway compares with the other destinations

Anthropic lists seven export destinations for Claude Motion: Adobe, Descript, HeyGen, Higgsfield, invideo, Luma AI and Runway, with Canva and Captions coming soon. Most of these partners have not published detailed workflows for Motion, so a feature-by-feature comparison is not possible from official sources.

What can be said at a high level:

• Runway has published the clearest end-to-end story: export from Motion, then generated footage and images, describe-to-edit, Runway Agent for longer cuts, sound, scene-by-scene edits and reformatting, plus four named team use cases.
• Higgsfield works the other way round as well: its own Help Center describes connecting Higgsfield to Claude as a custom MCP connector, which needs a paid Higgsfield subscription and spends Higgsfield credits on each generation. It has also announced Katana, which it describes as powered by Claude Motion. Our separate post covers Higgsfield in detail.
• Adobe, Descript, HeyGen, invideo and Luma AI are named as destinations, but their Motion-specific workflows have not been documented in the sources we rely on.

If you need generated footage and sound around a Motion animation and want the route that is documented most clearly today, Runway is the obvious first stop. If your team already works in one of the other listed tools, it is worth checking whether that tool’s own documentation has caught up before switching.

Limitations and open questions

The partnership was announced on launch day, and several practical details are still undocumented:

• What actually transfers. Neither side has said what format or resolution reaches Runway, or whether the animation arrives as a single clip or as separate scenes.
• Accounts and permissions. How a Claude workspace and a Runway account are linked has not been described.
• Round trips. Nothing has been published about sending an edited piece back to Claude. Assume the Motion artifact remains the source and the Runway project is downstream.
• Admin controls. Anthropic documents admin controls for Motion itself — Enterprise owners turn it on in Organization settings > Artifacts and can restrict it to groups — but not a separate switch for the Runway export.
• Motion’s own limits. Resolution, frame rate, maximum length and audio inside Motion are not documented in the Help Center.
• Beta status. Motion is in beta on Team and Enterprise, so the hand-off route may change.

FAQ

Do I need a Runway account to use the hand-off?

The editing and generation happen in Runway, so you should expect to work under a Runway plan. How the two accounts connect has not been documented.

Can Claude Motion add music or voiceover by itself?

Audio inside Claude Motion has not been documented. Runway lists voiceover and music among the things you can add after export.

Will my numbers stay accurate after the hand-off?

They are exact in Motion, because Motion animates the values you supply. Settle every figure there first, then check in Runway that restyling and reformatting have not hidden or altered any of them.

Can I make vertical and square versions?

Runway says a 16:9 explainer can be reformatted into vertical and square versions. Motion’s own documented export is MP4.

Is the Runway enterprise offer still available?

Runway’s banner says enterprises signing by 10/31 get two months of usage free. Confirm the current terms on Runway’s site.

Which Claude plans can use Claude Motion?

Team and Enterprise, during the beta. Team has it on by default; on Enterprise an Owner must turn it on.