vawe vs Revideo.
Revideo is an MIT-licensed rendering engine that makes video from TypeScript scenes. vawe makes video from one HTML page. This page compares them on authoring, rendering, preview, agent support and project status, and says where Revideo is stronger.
Facts read from Revideo’s own pages on 2026-11-03. Sources are listed at the end. vawe runs on your machine, needs no account and has no per-render fee.
Choose Revideo when
- Your team writes TypeScript and wants animation as generator functions.
- You need to split renders across workers or run them on Cloud Run.
- You want a React Player in your own app.
- You want an MIT licence.
Choose vawe when
- You want an agent to write the film in plain HTML, CSS and Web Animations, with no scene API to learn.
- You want one page to give the same frames every time, with the clock, timers and Math.random controlled for you.
- You want built-in motion blur and a library of 130 video components with After Effects eases.
- You want a critique of the film by a session that did not write it.
What Revideo is.
Revideo describes itself as a rendering engine for creating videos in code. You write a scene as a TypeScript generator function, render it with renderVideo() or a render endpoint, and preview it with a React Player. Its README calls it the engine behind Midrender.
Side by side.
| feature | Revideo | vawe |
|---|---|---|
| What it is | Rendering engine to create videos in code | Framework to make films from one HTML page |
| Licence | MIT | Apache-2.0 |
| Authoring model | TypeScript generator functions (makeScene2D) that add components and animate them with yield* | One HTML page: CSS, Web Animations, SVG, canvas, three.js |
| Rendering | renderVideo() or a render endpoint from the CLI; runs where Node and a headless browser run | Headless Chrome seeks and screenshots each frame; renders on your machine |
| Distributed rendering | Yes: split across workers; Google Cloud Run named as a target | No |
| Preview | A React Player that previews the project in the browser | bin/vawe studio: a scrubbable preview that edits the page’s literals |
| Agent support | Its GitHub page says Claude or Codex can generate a scene from a prompt; no skills named on the pages read | bin/vawe CLI and skills for writing, critiquing and judging a film |
| Project status | Not archived. Latest tag v0.11.0; last commit on main 2026-07-15. docs.re.video redirects to midrender.com/revideo/docs | Source install from GitHub |
Where Revideo is stronger.
- A TypeScript scene model. Scenes are generator functions, so duration and order come from yield* calls and not from keyframes.
- Parallel rendering. The README says renders can be split across workers and run on serverless platforms such as Google Cloud Run. vawe renders on one machine.
- An embeddable Player. A React Player previews the same project that renders the final video and accepts dynamic inputs.
- A headless render API with a render endpoint you can expose from its CLI.
Questions.
- Is Revideo open source?
- Yes, under the MIT licence. vawe is Apache-2.0.
- Is Revideo still maintained?
- On 2026-11-03 the GitHub repository was not archived. The last commit on main was dated 2026-07-15, and the latest tag was v0.11.0. The old docs address, docs.re.video, now redirects to midrender.com/revideo/docs. Check the repository for recent activity before you depend on it.
- What is the relation between Revideo and Midrender?
- The Revideo README says Revideo is the engine behind Midrender. The Revideo docs now sit on the Midrender site. This page found no pricing for Midrender and gives none.
- Can an AI agent use Revideo?
- The Revideo GitHub page says Claude or Codex can generate a scene from a prompt. This page found no agent skills named in the Revideo docs or README.
- Does vawe need TypeScript?
- No. A vawe film is one HTML page. You write HTML, CSS and Web Animations, or SVG, canvas or three.js.