The Tool That Refuses to Roll the Dice
Remotion is a framework that builds video out of React code. You write components, the frames are computed, and a renderer turns them into a file. There is no model in the middle deciding what the shot looks like. Every pixel is the consequence of something you wrote, which means the same input produces the same output on Tuesday that it produced on Monday.
That last sentence is the entire argument, and it is the opposite of what the rest of my work looks like. I direct commercials in São Paulo and I run Kling, Seedance and Gemini Omni on paying jobs. Those models are extraordinary and they are also slot machines. You prompt, you get something, you prompt again with the same words and you get a cousin of it. For a hero shot that is fine, because you only need the one. For the forty things that come after the hero shot, it is a catastrophe.
Remotion is what I reach for at exactly that moment. Not to generate. To stop generating.
What Is Remotion, and What Does It Have to Do With Claude?
The framework has been around for years. What changed in 2026 is that it became something you can direct through an agent instead of typing yourself, and that is why the search traffic around it exploded into questions like "how to use Remotion with Claude Code" rather than "what is Remotion".
The connection is a set of Agent Skills that Remotion publishes and maintains. They are plain instructions that teach a coding agent the house rules of a Remotion project: how the markup differs from a normal React app, how to preview in the Studio, how to render, how to handle captions and media. Eleven of them ship today, with /remotion-best-practices acting as the umbrella that covers the rest. The documentation names Claude Code, Codex, Kimi Code and Cursor as the agents they are written for.
The install is two commands and about a minute:
npx remotion skills add
npx remotion skills updateThe first pulls the skills into .agents/skills in your project, and symlinks .claude/skills to the same place so Claude Code finds them without extra configuration. The second is the one people forget: the skills are versioned alongside a framework shipping at a near daily pace, so an install from three months ago is teaching your agent stale patterns. As I write this, the remotion package sits at 4.0.520, published on September 1, 2026, four releases after 4.0.516 on August 24. That cadence is the reason the update command exists.
You can also install through the general skills registry with npx skills add remotion-dev/skills, which is the route to use if you are collecting skills from several projects in one place.
The Job Nobody Writes About
Most of what is published about Remotion and Claude right now is a demo. Somebody prompts an agent, a video appears, the video is a bar chart with a title card, everyone claps. That demo is true and it is also the least interesting thing the pairing does.
The job I use it for is variation. A campaign gets approved as one film. Then the client needs it in nine to five and sixteen to nine and one to one. Then in three languages. Then with the price changed in six markets, then with the legal line updated because someone in compliance woke up. On a traditional job that is a week of an editor conforming versions and a producer checking that nothing broke in version seven.
If the piece was generated by a model, you cannot re-render it. You can only regenerate it, and regeneration gives you a different film. The lighting shifts. The face drifts. The product loses the label. This is the same wall I described when I argued that character consistency is a preparation problem rather than a model problem, and it is the reason the promise of infinite variations from generative video keeps collapsing on contact with a real deliverable.
If the piece is a Remotion composition, the price is a prop. The language is a prop. The aspect ratio is a parameter the layout already responds to. You change the data, you render again, and every frame that was approved stays exactly as approved. That is not a small convenience. That is the difference between selling a campaign and selling a system.
Where the Agent Earns Its Place
Claude Code matters here for a reason that has nothing to do with generation. Remotion is code, and code is the medium agents are genuinely good at. Asking an agent to write a React component that animates a lower third on a spring curve is a well posed problem with a checkable answer. Asking a model to imagine a lower third is not.
So the division of labour is clean, and it is the same one I keep arriving at from every direction. I decide what the piece is. Claude writes and rewrites the composition. The Studio shows me the result and I judge it. When something is wrong I say what is wrong in words, not in keyframes.
The check is what makes it work. A Remotion render either matches the frame you approved or it does not, and you can see that in one look. This is the same structure as the verification loop I use with Claude Code agents on everything else: let the agent do the labour, keep a harsh and fast check in front of it, and never accept output that has not been looked at. Motion graphics are unusually kind to that method, because bad motion is obvious at a glance and does not need a specialist to spot.
What the agent does not do is decide. It has no taste about whether a transition lands, whether the type is too loud against the plate, whether the thing feels like the brand. Those are still the only parts of the job that were ever worth paying for.
What It Costs, and the Part People Miss
Remotion is free for individuals and teams of three or fewer, with all features and unlimited commercial use. That covers most independent directors and small shops outright, which is why it is worth trying before you budget for it.
Above three people you need a company license. The published pricing splits into Creators at 25 dollars per seat per month, for teams making videos by hand, and Automators at one cent per render with a minimum spend of 100 dollars a month, billed in increments of a thousand renders, for anyone wiring it into a pipeline. Enterprise starts at 500 dollars a month. Check the current terms before you commit, because a 5.0 release is queued and the license is one of the things moving in it.
The part people miss is that the pricing tells you what the tool is for. Nobody charges by the render for a tool you use once. They charge by the render because the intended use is the thousandth render of the same composition with the thousandth row of data, and that is precisely the work generative video cannot do.
How to Start Without Wasting a Week
Do not start with a film. Start with the piece of your work that is already repetitive and already annoying: the end card, the price tag, the subtitle burn, the social cutdown that gets rebuilt every month.
Create a project, install the skills, open the Studio, and ask your agent for that one component. Give it real data on the second attempt, not placeholder text, because placeholder text hides every layout problem you are going to have. Then render two variants and put them side by side. If the two are identical apart from the data, you have the thing that generative models will not give you.
The full documentation lives at remotion.dev/docs/ai/skills, and the skills are open at github.com/remotion-dev/skills. The skills I keep loaded alongside my own are listed on the skills page here.
I am not arguing you should abandon generative video. I use it every week and it does things nothing else can do. I am arguing that the two tools answer different questions, and that most of the frustration I see from people trying to run a real campaign on generated footage comes from asking a slot machine to be a printing press. Remotion is the printing press. Keep the slot machine for the shot that only has to exist once.
