---
title: When to use Remotion vs invideo
description: Remotion renders React video code at volume. invideo lets you or your agent move one reveal on a timeline without a code change.
---
Use Remotion when your video is React code and you render many versions of it. Use invideo when a person or an agent changes the cut by hand, like moving one reveal two seconds later, and you want footage, voice and music in the same place.

## The same brief in both tools

The brief: a 15 second product reveal for a launch. The product slides in, a price card appears, and the logo closes. After the first review, the marketer asks to move the price card reveal a little later.

In Remotion, your agent writes the video as a React component. Each frame is a function of the frame number, so the reveal time is a value in the code. To move the reveal, someone changes that value and renders again. The render runs on your machine, on a server, or on AWS Lambda.

In invideo, your agent builds the same video as clips, text and keyframes on a timeline, on a branch from `timeline_history`. The price card is a clip. To move the reveal, the marketer drags the clip in the editor, or the agent sends one `move_clip` operation with `edit_timeline`. The rest of the cut stays as it was, and the agent checks it with `capture` before it runs `export`.

## At a glance

The rows below are the ones that change the choice for this job.

| | Remotion | invideo |
| --- | --- | --- |
| How you make the video | React components | Edit operations on a real timeline |
| Editable timeline after the cut | Change the code and render again | Your agent rebuilds the composition's elements on the timeline from the source; then move, trim and retime them by hand or by agent |
| Generation | Not part of the framework | Video, image and audio models through `generate` |
| Captions | A captions how-to with code | `audio.transcript`, then an editable caption track |
| Agent access | Agent skills; no hosted MCP server | CLI and skills for terminal agents; MCP server for clients without a shell |
| Project files out | Rendered media | MP4, or a Premiere Pro, Final Cut Pro or DaVinci Resolve project |
| Where it renders | Your machine, a server, or AWS Lambda | In the cloud |
| Batch | Render at volume with Lambda or a server | One timeline per row, run in parts |
| License | Its own license, with free and Company License terms | invideo's terms |

Checked on 29 October 2026 against the <a href="https://www.remotion.dev/llms.txt" target="_blank">Remotion docs index</a>, the <a href="https://www.remotion.dev/docs/lambda" target="_blank">Lambda page</a>, the <a href="https://www.remotion.dev/docs/ai/mcp" target="_blank">MCP page</a> and the <a href="https://github.com/remotion-dev/remotion/blob/main/LICENSE.md" target="_blank">Remotion license</a>.

## Use Remotion when

Remotion fits video that is software.

- Your team writes React and wants video in the same code and design system.
- You render the same template many times with different data.
- You want to own the render, on your own machine, a server, or Lambda.
- The video is motion graphics and data, not footage that needs a person's eye.

## Use invideo when

invideo fits video that people review and change.

- The person who asks for changes does not write code. They drag the clip in the editor.
- The video needs stock footage, generated shots, a voice or licensed music.
- A person and an agent work on the same cut, and you want branches to compare versions.
- An editor finishes the video in Premiere Pro, Final Cut Pro or DaVinci Resolve.
- You want one set of terms for the whole job. invideo's terms for stock, music and generated media are on [Licensing and commercial use](/account/commercial-use).

Edits and exports are free. Generation and transcripts cost credits. Paid stock costs a small credit charge, or one of your workspace's iStock licenses. Your agent runs a dry run first and tells you the price before it spends anything.

## Use both

Keep the motion in Remotion and the finish in invideo. The hand-off is an MP4, or a rebuild of the composition from its source.

1. Render the animated parts to MP4 in Remotion, or have your agent rebuild them on the timeline as clips, text and keyframes.
2. Upload each file to the invideo project with `start_upload` and `add_media`.
3. Place them on a timeline, then add footage, a voice and music.
4. Make late timing changes on the timeline, where a person can review them.

A change inside a rendered animation goes back to Remotion for a new render. Your agent then replaces the clip on the timeline. A rebuilt element changes on the timeline. [Rebuild a composition as an editable timeline](/how-to/developers/composition-to-timeline) gives the steps.

## What Remotion does better

Say it plainly: for code-first video at volume, Remotion is the stronger tool.

- It is a mature React framework. Even HeyGen's HyperFrames comparison calls it older and more established, with more templates and tutorials.
- Lambda renders one video in parallel parts, which its docs call the fastest and most scalable way to render.
- Each frame is a function of the frame number. The model is simple to hold in your head.
- You control where it renders and what it runs on.

Read its license before you ship. Remotion's license page says who can use it free and who needs a Company License.

## Related

- [Use Remotion with invideo](/integrations/remotion)
- [When to use HyperFrames vs invideo](/compare/hyperframes)
- [Make many videos from a CSV with a script](/how-to/developers/csv-to-videos)
- [Rebuild a composition as an editable timeline](/how-to/developers/composition-to-timeline)
- [AI video tools compared, including invideo](/compare/alternatives)
- [invideo for AI agents](/agents)