Skip to main content
••14 min read•By Nathan Ibgui, fractional CIO

Remotion and Claude Code: a step-by-step tutorial to create an animated video

Remotion tutorial with Claude Code: setup in 4 commands, a brief template, still-frame checks, MP4 rendering and a reusable video format for a small business.

Remotion is the most widely used framework for having Claude Code write videos. Its documentation sums up the setup in four commands, and that’s true: twenty minutes are enough to get a first animation. What it doesn’t tell you is how to go from a fun demo to a format a small business can produce every month without losing a day to it. That’s what this tutorial covers: install, brief, have the agent check its own work, render, then make it repeatable.

It is based on the Remotion documentation as consulted on October 6, 2026 (pages updated the day before). It’s the second article in our series; for the overview of tools and whether it’s worth the effort, start with the guide to Claude Code and motion design.

Before you start: three prerequisites

1

Node.js installed

Remotion is a JavaScript project: every command goes through npx and npm. A Windows, Mac or Linux machine works.

2

Claude Code up and running

Installed and signed in to an account. The Remotion docs point out that most coding agents require a paid subscription. For installation, see our getting-started guide to Claude Code.

3

The license question settled

Free for companies of up to 3 people. From 4 people, a Company License is required: $25 per month per seat for the Creators plan (as of November 2026).

The third point is worth settling before your first render. Remotion’s license page states that the Creators plan covers manually creating videos for your own organization “including with AI agents and Remotion Studio,” with one seat per person producing videos. If, on the other hand, your project is to generate videos in bulk (one per client, one per product), the Automators plan applies: $0.01 per render, with a $100 monthly minimum (as of November 2026). The plans are detailed in the pillar guide.

Step 1: the four setup commands

Open a terminal in the folder where you keep your projects, then follow the official sequence. You need two terminal windows: one runs the preview, the other hosts Claude Code.

Command What it does Terminal
npx create-video --yes --blank --no-tailwind my-video Creates a blank project in the folder my-video, without Tailwind 1
cd my-video then npx remotion skills add Installs Remotion’s Agent Skills in the project 1
npm run dev Launches Remotion Studio: the preview opens in the browser 1 (stays open)
cd my-video then claude Starts Claude Code in the same folder 2

Why a blank project? Because Remotion’s templates already contain sample animations the agent would tend to reuse. Starting from a blank page gives results that are more faithful to your brief. Tailwind is turned off for the same reason: fewer layers, fewer surprises.

The skills are the centerpiece. They are twelve best-practice guides that Claude Code loads when it needs them: /remotion-create to create a composition, /remotion-markup for animation, typography and timing, /remotion-render for rendering, /remotion-captions for subtitles, /remotion-docs to look up the current documentation, and so on. Without them, the agent writes Remotion from memory, sometimes with outdated parameters. If you configured the old Remotion documentation MCP server, remove it: it is officially deprecated in favor of /remotion-docs.

Step 2: understand what the agent is going to write

You don’t need to know React, but three vocabulary words will save you time in your exchanges with the agent:

Composition

A “renderable” video: a component, a width and height, a frame rate, a duration and an ID. A single project can contain several, for example a 16:9 version and a 9:16 version.

Frame

One image. At 30 frames per second, a 15-second video has 450 frames. All timing is reasoned in frames: “the logo appears at frame 60,” meaning at 2 seconds.

Props

The data that changes from one video to the next: a title, a number, a color. Kept cleanly separate from the rest, they let you produce ten variants without touching the animation.

The third word matters most for a small business. A video whose text is hard-coded into the animation is a one-off. A video whose text goes through props, with default values, becomes a template: Remotion Studio then shows those fields in a panel you can edit without opening the code. Ask the agent for it explicitly in your very first brief.

Step 3: the brief that gets a good first draft

The quality of the first render depends almost entirely on the brief. A “make me a video for our new product” will produce a generic animation. Here is the structure we use, with an example for a LinkedIn “number of the month” video:

Brief template to paste into Claude Code

  • Goal: a “number of the month” video for LinkedIn, one single message.
  • Format: 1080 × 1350 (4:5 portrait), 30 frames per second, 12 seconds.
  • Sequence: 0–2 s logo; 2–7 s the number “1,240 orders” counts up from 0 to its value; 7–10 s a context sentence; 10–12 s logo and website address.
  • Brand: background #0B1220, accent #38BDF8, Inter font, logo in public/logo.svg.
  • Parameters: the number, the label and the context sentence must be props with default values, editable in the Studio.
  • Constraints: no music, no external images, understated transitions.

First copy the logo and any images into the project’s public folder: the agent works with the files it can see, and won’t go looking for your brand guidelines on your website. For fonts, name them; the /remotion-markup skill knows how to load them properly. If you write this kind of instruction often, our Claude prompting method gives you a reusable framework.

Before letting the agent write anything, a useful reflex: ask it to restate the plan (planned compositions, breakdown into sequences, props) and only code once you approve. Two minutes of reading saves a twenty-minute round trip.

Step 4: make the agent look at a still frame

This is the trick that improves quality the most, and few tutorials mention it. Claude Code writes code; it can’t see the preview running in your browser. But Remotion can render a single frame of a composition, at a precise moment, and Claude Code can read a PNG image. So we give it eyes.

Giving the agent eyes: the “still” loop 1. Write Claude Code edits the composition 2. Freeze npx remotion still --frame=150 3. Look the agent reads the PNG and compares it with the brief 4. Fix cut-off text, contrast, misplaced logo… until the image matches the brief Then a human judges the motion in Remotion Studio rhythm, smoothness, readability: what a still frame can’t show Source: Remotion documentation, still command (single frame, PNG by default), consulted October 6, 2026.
The still frame catches layout defects; judging the motion stays a human job.

The command is npx remotion still, followed by the composition ID and the --frame option: by default it produces a PNG in the outfolder. To check several moments at once, the documentation says to use npx remotion render with --frames=0,30,90 and --image-format=png. A typical instruction:

“After each change, render frames 30, 150 and 330 as PNG, open them and check: no text cut off or out of frame, readable contrast, logo fully visible, number fully displayed at frame 210. Fix it before handing back to me.”

This check catches most of a first draft’s defects: a title that’s too long and overflows in portrait format, white text on a light background, an element that goes off-frame. It says nothing about the motion itself. For that, you have to watch the preview.

Step 5: iterate with precise corrections

Once the still frame is clean, watch the animation in Remotion Studio, which has been running in your browser since step 1. Note what’s wrong, then phrase requests the agent can execute without interpreting:

Vague requests

  • “Make it more dynamic.”
  • “The number doesn’t stand out enough.”
  • “It looks a bit cheap.”
  • “Improve the ending.”

Actionable requests

  • “Shorten the logo intro from 2 s to 1 s; everything else moves up by the same amount.”
  • “Number at 160 px, bold, accent color, slight bounce at the end of the count.”
  • “Remove the drop shadow and the background gradient, keep a flat color.”
  • “The final logo stays still for the last 2 seconds.”

Two habits complete the method. Version the project in Git as soon as a version works for you: if a correction makes things worse, you roll back with one command, and the agent can do it for you. One correction at a time, or three at most: a batch of ten mixed tweaks makes it impossible to know which one broke what.

Step 6: the final render

There are two ways to produce the video file. The simplest: Remotion Studio’s Render button, which opens the settings and then starts the render. The most reproducible: the command line, npx remotion render followed by the composition ID; without an output path, the file lands in the outfolder. It’s also what the /remotion-render skill does when you simply ask the agent to “run the final render.”

A few command options are useful day to day: --props to inject the month’s values, --width and --height to force a format, --concurrency to limit the number of CPU cores used if the machine needs to stay responsive during the render.

Windows gotcha

The documentation flags it: passing props as JSON directly on the command line (--props='{...}') doesn’t work in Windows terminals, which strip the quotes. Write the values to a file, for example props/october.json, and pass its path: --props=./props/october.json. It’s cleaner anyway, since each month becomes an archived file.

Step 7: turn the video into a recurring format

This is where Remotion pays back the setup. If the props were planned from the brief, November’s “number of the month” no longer needs the agent: you copy October’s file, change three values and run the render. For format variants, ask the agent to add one composition per aspect ratio (16:9 for YouTube and the website, 9:16 for stories, 1:1 or 4:5 for LinkedIn) sharing the same component: one animation to maintain, three output files.

Beyond a few dozen automatically generated videos, for example one per product page, the project changes in nature: server-side or cloud rendering, integration into an application, and the Automators license plan. It’s no longer a tutorial, it’s a full-fledged automation project, which deserves to be scoped as such.

The most common mistakes

Symptom Likely cause Fix
The agent uses functions that don’t exist Skills not installed, it’s writing from memory npx remotion skills add, then ask it to consult /remotion-docs
The preview stopped updating The terminal running npm run dev was closed Restart the preview in a dedicated window
Text cut off in portrait format Layout designed for 16:9 A “still” loop on each composition
Each variant needs the agent Text hard-coded into the animation Have the text extracted into props with default values
Different font in the render Font not explicitly loaded Ask for the font to be loaded via the skill /remotion-markup

Finally, only give the agent what you could publish: an internal figure not yet announced is still company data. The confidentiality rules are those described in our article on Claude for business and data security. And the rights to fonts, music and images are still yours to check.

Frequently asked questions

How do I install Remotion with Claude Code?

The Remotion documentation gives four steps: create a blank project with npx create-video --yes --blank --no-tailwind my-video, install the Agent Skills with npx remotion skills add in that folder, launch the preview with npm run dev, then start claude in the same folder from a second terminal.

Do I need to know how to code to use Remotion with Claude Code?

Not to produce a first video: the agent writes the React code. You do need to be able to run commands in a terminal, know three concepts (composition, frame, props) and review the preview to request precise corrections.

Can Claude Code see the video it creates?

Not the animation itself, but it can check still frames: the npx remotion still command renders a specific frame as a PNG, which the agent reads and compares with the brief. Judging rhythm and smoothness remains a human job, in Remotion Studio.

How do I render the final video as an MP4?

Either with the Render button in Remotion Studio, or on the command line with npx remotion render followed by the composition ID. Without an output path, the file is saved in the project’s out folder.

Is the tutorial free for a business?

Remotion is free for individuals and companies of up to 3 people. From 4 people, a Company License is required: $25 per month per seat for the Creators plan, which covers creating videos with AI agents (as of November 2026). Claude Code itself is paid (subscription or API).

In short

Four commands install Remotion and its skills; the rest is a matter of method. A structured brief that plans for props, a loop where the agent checks still frames itself, precise corrections one at a time, a command-line render with value files: that’s what turns a demo into a format you can reproduce every month in a few minutes. The next article in the series puts Remotion up against HyperFrames, HeyGen’s open-source alternative. To frame these uses within your company, explore our AI strategy services or contact us.

Nathan Ibgui, IT & AI consultant

Written by

Nathan Ibgui

Independent consultant and fractional CIO, I help small and mid-sized businesses with IT strategy, artificial intelligence, automation and cybersecurity — from assessment to execution.

Ready to transform your business?

Describe your needs in a few lines: I reply within 24 hours with an initial analysis and concrete recommendations.