Programmatic video, the MIT way
Revideo is a framework for building videos in code, derived from Motion Canvas and aimed at developers who want to generate video programmatically and render it through an API. Where Remotion uses React, Revideo uses a Motion Canvas-style TypeScript API, and its draw is being fully MIT licensed, with a focus on headless rendering for building your own video pipeline. At 3,854 stars as of 2026-06 it is a small, niche project (the repository moved to the midrender organization from its earlier redotvideo home, keeping the @revideo/* npm scope).
It is the kind of tool you reach for when you want to build a render service, not edit a one-off clip.
What it does
You write scenes as TypeScript using Motion Canvas concepts, preview them live in the browser, and render to video. The emphasis is on programmatic and headless rendering, with parallelization for generating video at scale, which makes it suited to backend services that produce video from data. Audio support and shader hooks exist, though both have rough edges in practice.
Install
npm init @revideo@latestThat scaffolds a project; npm run dev gives a live browser preview and npm run render exports to a video file. The workflow is write TypeScript scenes, iterate in the browser, then render.
The maintenance question
Before you build on Revideo, look at the activity. As of 2026-06 the last meaningful pushes were around mid-2025, and there is a community issue literally titled “Still maintained?” that went without a clear official answer. The project is not archived and had four contributors active in its last busy stretch, so this reads as a slowdown and a communication gap rather than a confirmed abandonment. Still, the practical advice is the same: it is fine for experiments and internal tools, but do not put a critical production pipeline on a small project whose release cadence has gone quiet without checking current activity yourself.
Where it fits, and where it doesn’t
Revideo makes sense when MIT licensing is a hard requirement, when you are building a self-hosted render pipeline and want a code-first, headless-friendly framework, or when you specifically prefer the Motion Canvas style. For an internal video-generation tool it can do the job.
The cautions are real: it is much smaller than Remotion with a far smaller community, maintenance has slowed, headless rendering has reported instability on Windows and serverless, audio handling has bugs, and some Motion Canvas features are not fully ported. If you want a mature, actively maintained programmatic-video tool and can accept Remotion’s license, Remotion is the lower-risk choice.
revideo versus Remotion
| Revideo | Remotion | |
|---|---|---|
| Stars | 3,854 | 50,261 |
| Paradigm | Motion Canvas-style TypeScript | React components |
| License | MIT | free for individuals and small companies, paid for larger |
| Maintenance | slowed, last push mid-2025 | very active |
| Best for | MIT self-hosted render pipeline | mature data-driven video in React |
Counts are from GitHub as of June 2026. Remotion is the mature, actively maintained leader, at the cost of a paid company license above a small size threshold. Revideo’s appeal is the MIT license and the Motion Canvas style, but the small community and slowing maintenance are the trade-off. Pick by which risk you can live with: licensing cost, or maintenance uncertainty.
The star curve
The star curve shows early interest that has flattened, consistent with a niche project that drew attention as a Motion Canvas-based, MIT alternative to Remotion, then slowed. The shape mirrors the maintenance story rather than continued momentum.
What the issue tracker warns you about
The tracker points at the rough edges. The clearest signal is the open question about whether it is still maintained, which matters for any production decision. Beyond that: audio across multiple scenes and local audio files have bugs, headless rendering with ffmpeg fails on some Windows setups, serverless deployment lacks first-class support and documentation, and shaders and some Motion Canvas features (camera, certain media seek) are incomplete or undocumented. Test your exact use case before committing.
Related
For the mature, actively maintained alternative, see Remotion. For AI-driven short-form video rather than code-defined video, see MoneyPrinterTurbo. For what is trending, see the daily digest and the weekly report.
FAQ
Is Revideo still maintained? It is not archived, but its last meaningful activity was around mid-2025 and a community “Still maintained?” issue went without a clear answer. Treat it as slowed rather than confirmed dead, and check current commit activity before building anything critical on it.
Revideo vs Remotion, which should I use? Revideo is MIT and Motion Canvas-style but small and slowing. Remotion is mature and very active but needs a paid license for larger companies. Choose Revideo if MIT licensing is essential and you accept the maintenance risk, Remotion for a production-grade, well-supported tool.
Why did Revideo move from redotvideo to midrender? The repository moved to the midrender organization, which is an org rename rather than a sign of abandonment. The @revideo/* npm packages kept their names, so imports are unaffected.
Can I use Revideo commercially? Yes. It is MIT licensed, so commercial use, modification, and private deployment are all permitted without a separate license.
Can Revideo render on Windows or serverless? Sometimes, with caveats. The tracker has reports of ffmpeg failures on Windows and a lack of first-class serverless support, with Google Cloud Run the documented path. Test your target environment before relying on it.