# Remotion, HyperFrames and vos, compared

Three ways to make video with code. Two make a file; one keeps the video at a link with every version.

By [Hongbin Li](https://www.hongbinli.com/) · Updated October 2026

**Remotion** is the mature incumbent, built on React. **HyperFrames**, backed by HeyGen, is the fast-moving agent-first entrant, built on HTML. **vos** is the youngest of the three, built on a JSON config whose content is data, and it is the engine under vosso. Every row below was checked on the date above; each tool links to its own source.

## Side by side

*Remotion vs HyperFrames vs vos, October 2026*

|  | Remotion | HyperFrames | vos |
| --- | --- | --- | --- |
| Authoring | React components (JSX) | HTML, CSS and JavaScript with timing attributes | A JSON config; content in data, motion in the program |
| Where it renders | Server with a headless browser; the browser with @remotion/web-renderer | Headless Chrome capture, encoded with FFmpeg | One compiled artifact: browser preview, browser export, server render |
| Sharing a finished video | A file you host yourself | publish: an import page someone signs in to claim, no player | A watch page on vos.so that plays, unlisted or public |
| Changing it later | Change the code and render again | Edit the composition and publish again | Drag a control, or an agent pushes the next version |
| History | Your repository | Publishing again updates the page in place | Every version kept, with who pushed it |
| Editing by hand | Code, with a preview player | A desktop studio | A browser studio |
| License | Source-available; company license past 3 people | Apache 2.0 | MIT |
| Ecosystem | Mature: templates, docs, community | Fast-moving: block registry, skills, hosted MCP | Young; small community |

## When each one is the right choice

**Remotion** when your team lives in React and wants the safest, best-documented option. **HyperFrames** when you compose from HTML blocks and render in a pipeline, and want a desktop studio beside it. **vos** when the video has to stay current after it ships: a link that keeps playing the latest version, controls a person can drag, and a history of who changed what.

The pairwise pages go deeper: [vos vs Remotion](https://vos.so/engine/vs/remotion) and [vos vs HyperFrames](https://vos.so/engine/vs/hyperframes). Asking a coding agent to do the work? Each project’s skills are on [Claude Code video skills compared](https://vos.so/blog/claude-code-video-skills).

## Frequently asked questions

### Should I use Remotion or HyperFrames?

Use Remotion if your team works in React and wants the most mature ecosystem: components, templates, documentation and a long production record. Use HyperFrames if you or your agent think in HTML and CSS and want a registry of ready-made blocks and a desktop studio. Both leave you with a rendered file.

### Where does vos fit between Remotion and HyperFrames?

vos is the third option when the video has to live on after the render. Its content is data, so words and colours are controls, and vos.so hosts it at a link that plays and keeps every version. A Remotion or HyperFrames piece can be ported to vos by an agent and hosted there.

### Which of the three render in the browser?

Remotion exports in the browser with @remotion/web-renderer as well as on a server. vos runs one compiled artifact for the browser preview, the browser export and the server render. HyperFrames previews on a dev server and renders by capturing headless Chrome.

### Are they open source?

vos is MIT and HyperFrames is Apache 2.0. Remotion is source-available: free for up to three people, with a company license beyond that.

Something else? [hello@vos.so](mailto:hello@vos.so)

## Made one with Remotion or HyperFrames?

Paste one line to your agent and it lands on vos.so as a link that plays and keeps every version.

[Put your video on vos.so](https://vos.so/host)

---

Source: https://vos.so/engine/vs/remotion-vs-hyperframes
