Motion design · 7 min read
Claude + Remotion: writing video code with Claude vs using an AI motion engine
Claude writes Remotion components well. Here is how that workflow looks, where it gets hard, and when an AI motion engine like Claude Video is the faster path.
By Claude Video Team ·
Remotion popularized a simple, powerful idea: a video is a React component rendered frame by frame. Claude is a capable React developer, so “ask Claude to write a Remotion video” is a natural workflow. It works. It also comes with costs worth knowing up front.
The Claude + Remotion workflow
- Set up a Remotion project and its dependencies.
- Describe the video to Claude and ask for compositions and components.
- Iterate on timing with useCurrentFrame, interpolate and spring.
- Add assets: fonts, images, screenshots, audio.
- Render locally or on your own infrastructure.
Where it gets hard
- Design quality depends on what you prompt. Claude writes correct code faster than it invents a visual system.
- Every effect is code you maintain: 3D type, particles, physics and transitions take real work.
- Audio, beat sync and music licensing are on you.
- Non-developers on your team cannot edit the result.
- Check Remotion’s license terms for your company size.
The AI motion engine path
Claude Video runs on Kinetik, an engine built on the same frame-by-frame React model. The difference is what comes included: an AI director that writes the storyboard, 34 scene types, 21 transitions, nine art directions, 3D titles, particles, physics, procedural music with beat-synced cuts, a browser editor and hosted rendering up to 4K.
Which one should you pick?
- Pick Claude + Remotion if the video must live as code in your repo and you have engineering time to own it.
- Pick Claude Video if you want finished, on-brand videos quickly, an editor for marketing, and API or MCP automation.
- Mix both: Claude Video supports custom React scenes when the library is not enough, and Claude can write them.