Remotion vs Editing Footage With Claude: Which One You Need

1Do you need Remotion or a video editor?

Use Remotion (or HyperFrames) when the video does not exist yet and will be designed: product demos, animated charts, explainers, title sequences. Use an editor when the video already exists as footage: a talking head, a podcast, a screen recording, an interview. Claude Code can drive both, but it is doing different work in each.

With Remotion, Claude writes a program. Every frame is computed from code, so a change means editing code and rendering again. With an editor, Claude makes decisions about material that already exists: which takes to keep, where to cut, how loud the voice should be. Our overview of editing video with Claude covers all three routes briefly; this guide goes deep on the choice between the first two, with numbers from our own renders.

The confusion is understandable. The best-known Claude video demo is a Remotion one: an r/ClaudeAI post titled “I delayed my product launch for months because I couldn't afford demo videos” had more than 1,000 upvotes and 133 comments when we re-opened it in October 2026. People arrive from posts like that wanting to cut a recorded video, which is where Remotion fits worst.

2How does Remotion work with Claude Code?

Remotion turns React components into video. Claude Code writes the components, Remotion's preview shows them in a browser, and the render command loads each frame in headless Chrome and encodes the frames to MP4. Remotion's coding agents guide names Claude Code, Codex, Kimi Code and OpenCode, lists Node.js as the other prerequisite, and notes that most coding agents require a paid subscription (checked October 2026). Its steps: create a blank project, run npx remotion skills add to install Remotion's agent skills, start the preview with npm run dev, and run claude in the project folder in a second terminal.

Our test render

We wanted real numbers rather than demo-reel impressions, so we built a small composition ourselves (without an agent, so the timings measure Remotion, not Claude). The project setup and first render:

npx create-video --yes --blank --no-tailwind my-video
cd my-video
npm i
npx remotion render MyComp out/first.mp4

The composition is a 5 second, 1920x1080, 30 fps “data video”: a title fades in and a number counts from 0 to 1,240. It is the kind of component Claude Code writes in this setup; ours, with styling trimmed:

export const MyComponent: React.FC = () => {
  const frame = useCurrentFrame();
  const opacity = interpolate(frame, [0, 20], [0, 1], { extrapolateRight: "clamp" });
  const signups = Math.round(
    interpolate(frame, [20, 110], [0, 1240], { extrapolateLeft: "clamp", extrapolateRight: "clamp" }),
  );
  return (
    <AbsoluteFill style={{ backgroundColor: "white", justifyContent: "center", alignItems: "center" }}>
      <div style={{ opacity, fontSize: 64 }}>Weekly signups</div>
      <div style={{ fontSize: 200, fontWeight: 700 }}>{signups.toLocaleString("en-US")}</div>
    </AbsoluteFill>
  );
};

What we measured on an Apple M1 Pro with Remotion 4.0.532 (our numbers, one machine, wall-clock time):

# Apple M1 Pro, Remotion 4.0.532, 1920x1080 at 30 fps
npm i                                   58.8 s
first render, 5 s counter card          10.1 s   (fetched a 193 MB headless Chrome once;
                                                  node_modules then held 504 MB)
next three renders                      4.2 s, 4.1 s, 4.0 s
30 s of footage + a lower third         31.5 s, 30.8 s
same 4 s lower third, opaque H.264      4.0 s
same 4 s lower third, transparent VP8   116.6 s, 114.5 s

The output was a 150 frame H.264 file of 5.000 seconds and 173 kB, and a frame at 4 seconds showed “1,240” as expected. Two things stand out. Designed graphics render quickly once the browser is installed: about 4 seconds for 5 seconds of video. Footage and transparency are slower, which matters in sections 6 and 8.

The preview is what makes this work with an agent: you watch each change in the browser as Claude makes it. But the project is a folder of React files, not a timeline.

3What is HyperFrames, and how is it different from Remotion?

HyperFrames, from HeyGen, does the same job with plain HTML instead of React: a composition is an index.html with data attributes for timing and tracks, rendered frame by frame in headless Chrome and encoded with FFmpeg. Its GitHub README (checked October 2026) lists Node.js 22+ and FFmpeg as requirements and gives this Claude Code plugin install:

claude plugin marketplace add heygen-com/hyperframes
claude plugin install hyperframes@hyperframes

The README describes the difference itself: HyperFrames is “inspired by Remotion”, both render with headless Chrome and FFmpeg, and “The main difference is the authoring model.” HyperFrames needs no build step and is Apache 2.0, “with no per-render fees or commercial-use thresholds”.

Two of its skills are telling for this comparison. /talking-head-recut packages an existing talking-head, interview or podcast video with designed overlays (lower thirds, callouts, kinetic titles), and /embedded-captions adds captions to an existing talking-head video, “footage untouched”. Our reading: even the code-first tools treat recorded footage as something you decorate, not something you cut. We did not run HyperFrames for this post; the facts above are from its README.

4Is Remotion free for commercial use?

Yes, if you are an individual, an organization of up to 3 people, a non-profit, or still evaluating it. Organizations of 4 or more need a paid Company License. That is from Remotion's licence FAQ and pricing page, both checked October 2026. The FAQ says there is no difference in features between the free and paid licences, and that a one-person company can use the free licence even when incorporated.

The paid options, as the pricing page and FAQ list them in US dollars:

• Remotion for Creators: $25 a month per person who writes Remotion code “themselves or using agentic coding tools”. This is the tier for a team making its own videos with Claude Code. The pricing calculator shows 3 seats at $75.
• Remotion for Automators: $0.01 per render with a $100 monthly minimum, so the minimum covers 10,000 renders (our arithmetic: $100 / $0.01). It applies to organizations that own code calling Remotion's render APIs programmatically, such as video editors, prompt-to-video apps and pipelines; the FAQ lists renderMedia(), npx remotion render and the Player among them. Previews do not count as renders.
• Enterprise: from $500 a month, with custom terms, paperwork and a private support channel.

Two details matter for client work. If an agency delivers only the finished MP4, only the agency's headcount counts; if the client owns or works on the Remotion project, both headcounts are added together for the 4-person threshold. And Remotion is not open source: the FAQ calls it source-available, governed by a proprietary licence. That corrects a common belief; the automated summary on the launch thread above calls it “free/open-source”. “Free” holds for solo builders and teams of up to 3; “open source” does not hold for anyone.

5When does code-generated video win?

When the video is designed rather than shot, will be made more than once, or is driven by data. Product demos, launch reels, animated charts, explainers, title cards, and sets of variants (the same reel with a different headline, language or number) are where code beats a timeline: change a value and render again.

The launch thread is the clearest case. Its author describes quotes from motion designers of $300 to $1,000 per video with 6 to 10 week timelines, and writes:

Their stack was Remotion, Claude Code and agent skills for transitions and illustrations, and the time per reel fell quickly: “First reel took ~3 hours. Second took ~90 minutes. Now I'm under an hour per reel.” One reply drew the boundary well: for character animation or real motion design “youre cooked. but for product demos and explainer reels this workflow ships”.

The limit is polish. Another r/ClaudeAI poster had everything rendering correctly and still was not happy with the result:

A reply on the launch thread put it shorter: “It looks good but lacks that smooth magic of editors.” Our reading: code gets you clean, repeatable graphics fast; easing, timing and taste still have to come from you.

6When does editing recorded footage win?

Whenever the content already exists as footage: talking heads, podcasts, interviews, tutorials, vlogs. The work there is choosing and cutting, and an editor (or ffmpeg) does that directly, while a code framework pushes every frame back through a browser.

Three reasons, in our view:

• The decisions come from the transcript. Removing filler words, dropping a false start and keeping the best take are decisions about what was said. An agent reads a timestamped transcript and cuts. Remotion can trim a clip too, but you would be writing a cut list into React props.
• Speed. In our test, 30 seconds of 1080p test footage with a lower third took 31.5 and 30.8 seconds to render in Remotion, roughly real time. ffmpeg re-encoding the same clip with a drawn box took 4.2 seconds, about seven times faster (our test, not an equal comparison: ffmpeg drew a plain box, not a browser layout). At that rate, by our extrapolation, an hour-long podcast would take about an hour per render.
• Editing by hand afterwards. An editor keeps a timeline you can open and nudge. A code project can only be changed through code, which suits developers and frustrates everyone else.

The tell is in what people do after the code step. One reply on the launch thread: “I did the same with Remotion, Eleven Labs and then CapCut.” Remotion came first and an editor came last.

Our Claude Code editing guide walks through the ffmpeg route for footage step by step, and our comparison of video editing MCP servers covers editors Claude can drive directly.

7How do Remotion and editing footage compare?

Code wins on repeatable, designed output; editing wins on real footage and on anything you will keep adjusting by hand. Our summary of the sections above:

If the job sits in both columns, such as a podcast clip with animated captions and a branded intro, use both, as the next section shows.

8Can you use Remotion and a video editor together?

Yes, and for most real projects it is the best setup: cut the footage in an editor, generate graphics as code, and lay the graphics over the footage. Remotion's transparent video docs give two ways to keep the background see-through: WebM with VP8 or VP9 and the yuva420p pixel format, or ProRes 4444, which the docs recommend for Final Cut Pro, Adobe Premiere and DaVinci Resolve (checked October 2026). We rendered a sliding lower third the WebM way:

npx remotion render LowerThird out/lower-third.webm \
  --image-format=png --pixel-format=yuva420p --codec=vp8

ffprobe reported a 4.000 second VP8 file tagged alpha_mode=1, and overlaying it on our test footage with ffmpeg showed the white name box over the footage with the rest transparent. The cost was time: about 115 seconds, against 4 seconds for the same lower third rendered opaque, roughly 28 times slower on our machine (114.5 / 4.0, our arithmetic). The frames themselves rendered quickly; the progress output showed the VP8 encode as the slow step. Render overlays once, after the design is settled, not on every tweak.

Code clips inside an editor

Disclosure: we make Linkeddit Studio, a desktop video editor for Mac and Windows where Claude Code or Codex edits the timeline, so weigh this part accordingly. Studio's agent tools include one for code clips: the agent writes an HTML page, and Studio renders it frame by frame, with the network closed, into a video clip of up to 120 seconds that it can place on the timeline. A page with no background is kept transparent, so a lower third or title on a higher track shows the footage under it. The agent gets starter templates for a title card, lower third, word captions, progress bar and end card, and can look at rendered frames of the result before you do.

That puts both columns of the table in one project. The footage side is the editor's own work: cutting by editing the transcript, removing filler words, on-device Whisper captions burned in, and loudness normalized to a target, with every agent edit undoable. It is a one-time $99 purchase, and the AI is your own Claude or Codex subscription. The pages are plain HTML, like HyperFrames rather than Remotion, so a Remotion project does not drop in as it is; render it to a video file first.

Frequently asked questions