Remotion: Turn Video Into Code, Batch-Render It, and Version-Control It
Video as Code: What Remotion Can and Cannot Do
Author: Independent Developer Aping
Recently I came across a tool for writing videos in code—Remotion. I went through the whole remotion.dev site. My motivation was specific: to see whether one set of templates could be fed different data to produce videos in batch, and also be version-controlled like code.
1. Where the Two Existing Tool Types Get Stuck
The Manual Ledger of Editing Software
Premiere Pro / After Effects rely on manual dragging: you drag clips onto the timeline, one project per video, and to revise a version you have to go back and find the layer. 5,000 videos means 5,000 projects and 5,000 exports. There's no shortcut in the UI for these actions. Throwing project files into Git is useless—a diff shows a pile of binary data and layer IDs.
The Black-Box Ledger of AI Video Tools
AI video tools lower the barrier: a sentence in, a video out. What you can adjust stops at templates and parameters. If you want to swap the intro to match your company's current-season motion guidelines, or produce videos SKU by SKU from an order database, the interfaces and data structures don't line up.
Both tool types get stuck at the same point: the video-production process is not treated as code. Batch generation, version management, and integration with business systems all have mature answers in code, but not in editing software.
Why must videos be made one at a time?
2. What Remotion Is and How Frames Are Rendered
Its answer is the most direct: the picture is a React component, and time is determined by the frame number.
A One-Sentence Definition
Remotion is an open-source, React-based video framework. The official name for it is "video as code."
The Render Chain Has Only Three Steps
You write React components; a component describes what a given frame looks like. React renders each frame into the DOM, headless Chromium screenshots it into an image, and FFmpeg encodes the frames into an MP4 at the chosen frames-per-second. The timeline is derived from frame numbers; the playhead in the UI is just a number here.
Screenshotting frame by frame—how fast can that be? This post gives no numbers, and I haven't run it on my own machine.
Three Entry Points, Side by Side on the Homepage
- programmatically: everything controlled by code—data in, video out. Can go into Git and CI. Entry point is the API Docs.
- interactively: drag the timeline and adjust keyframes in Remotion Studio, then save changes back to code. Entry point is Studio.
- agentically: an Agent reads the official docs and writes components; a human only reviews the code. Entry point is Agent Skills.
The third column on the homepage, "agentically," refers to that last path—letting an Agent write components for you.
It Doesn't Replace PR/AE
For post-production and fine visual-effects editing, AE is the better fit. Remotion runs on the automation and programmability track; what it sells is batch processing, maintainability, and the ability to grow together with business systems.
3. Capability Inventory: What Can It Do
With the source of frames clear, let's see what those frames can be assembled into.
Parameterization and Design Systems
Intros, caption bars, and data cards can all be wrapped into components, letting the whole company share one set of motion and layout. Change one place, and every video produced from then on follows. The official term for this approach is a "motion design system."
Batch Rendering
One template plus one data source: 1,000 data records in, 1,000 videos out. Editing software can't do this, and that's not what it's good at anyway.
Built-In Assets
Six categories are included: elements, animations, transitions, sound effects, captions, and color grading. The official homepage also lists effect presets and transition presets—enough to assemble a short video.
Where Rendering Happens
The official docs list six rendering entry points. The difference is who is running the browser.
- Studio: manual export—a colleague who doesn't write code can still produce videos.
- CLI:
npx remotion render—most direct for local and CI scripts. - SSR: call the rendering API in a Node service, render on request.
- AWS Lambda: hundreds of concurrent renders per run; this is for large batches.
- GitHub Actions: triggered on commit, videos output as build artifacts.
- Browser-side rendering: render directly in the browser; assets don't need uploading.
Ecosystem Companions
Remotion Player embeds videos in web pages for playback. Editor Starter is a paid template that lets you build an online editor. The Agent SDK hasn't shipped yet—the official site marks it "Soon." remotion.dev/convert is a local transcoding tool, and remotion.media provides test assets.
The official site carries a few numbers. Copied from the homepage on November 14, 2026: 72K stars, 6M+ monthly installs, 1,200 pages of docs, 12K+ Discord members, 300+ contributors, 800 customers. These only indicate it won't disappear tomorrow.
Can the same set of components produce both landscape and portrait? Yes. Width and height are written into the composition's parameters; change one spot and you get a different aspect ratio.
4. Scenarios and People: Who Should Use It, Who Shouldn't
When these capabilities land on concrete jobs, the fork becomes clear.
What It's Good For
- Data-visualization shorts and technical-demo animations: data changes, videos re-render.
- Batch personalized videos: annual reports, certificates, marketing assets generated per user.
- Building your own video tools or online editing platforms—Player and Editor Starter are built for exactly that.
- Video templates that need to be maintainable and rollback-able, and that need to hook into a backend for automatic video creation.
Jobs It Can't Take
- Complex post-production and fine effects editing—AE is better.
- If you just want to drag and drop to cut long videos and have no intention of touching JS or React, editing software is far simpler.
Batch video fits it; long-form post-production doesn't. That line is drawn clearly. The difference between the two paths is quantity: one side is many videos, each different and required to be re-renderable; the other side is a single video that needs to be fine-tuned.
5. Minimal Setup: Running in Five Minutes
Only after the work matches does it make sense to talk about getting it running.
Prerequisites
Node 16 and above will run it—check the official system requirements for the exact version. The install page has an easy-to-miss note: Linux needs glibc 2.35+, macOS needs version 15 or later, and Alpine and NixOS are officially unsupported.
Two Commands
npx create-video@latest
Pick a template, install dependencies, then start Studio:
npm run dev
Edit Code, See the Screen Refresh in Real Time
In Studio you can drag the timeline and keyframes, and saving takes effect immediately. How a video is organized becomes clear from this composition snippet:
import { Composition } from "remotion";
import { MyVideo } from "./MyVideo";
export const Root = () => (
<Composition id="MyVideo" component={MyVideo} durationInFrames={150} fps={30} width={1080} height={1920} />
);
6. License and Commercial Use
Once it runs, money comes next. I checked this section twice because it's the easiest to misremember.
Free Scope
Remotion uses its own Remotion License; permissive open-source licenses like MIT don't apply here. It's free for individual use, and free for companies with up to three people. Commercial use doesn't cost extra.
7. Strengths, Limitations, and What Comes Next
With costs settled, let me lay out the good and the bad on each side.
What's Worth Using
I value two things most: First, you reuse the frontend stack—React, CSS, SVG, Canvas, WebGL can all go straight into the picture; you don't need to learn a separate motion system. Second, video-as-code: videos go into Git like a web page, you can diff a revision, and rollback doesn't require redoing the work.
- Data-driven batch rendering: template plus data source, output volume follows data volume.
- Integration into business systems: Player sits in a web page, the rendering API hangs off a backend, and producing a video is just an API call.
Where It Gets Stuck
- You need a React foundation. If you don't know components and hooks, the learning cost is no lower than learning editing.
- Rendering consumes resources: one local render saturates the CPU; large volumes require the cloud, and cloud costs are metered.
- Long videos are slow: a finished piece of tens of minutes takes hours. Short videos and dynamic graphics are where it's comfortable.
Reference Docs
- GitHub repository: https://github.com/remotion-dev/remotion — source code and examples live there.
- Official docs: https://www.remotion.dev/docs — look up APIs and rendering entry points here.