# Motion Canvas

> Motion Canvas is an MIT-licensed TypeScript library and editor for animation in code: its design, dormant core and the Canvas Commons and Revideo forks.

Source: https://metavert.io/motion-canvas  
Published: 2026-10-21  
Updated: 2026-10-21

**Motion Canvas** is an open-source TypeScript library and editor for making animations in code. Its documentation describes it as "a specialized tool designed to create informative vector animations and synchronize them with voice-overs", and adds that it's "not meant to be a replacement for traditional video editing software". The developer known as aarthificial started the project in 2022 and remains by far its largest contributor. It's MIT-licensed and has about 19,400 GitHub stars. It's one of the two best-known tools for [motion graphics as code](https://metavert.io/motion-graphics-as-code), alongside [Remotion](https://metavert.io/remotion), and a programmer's route into [automated animation](https://metavert.io/generative-animation). As of October 2026 its core is effectively dormant, and active development has moved to community forks.

### How It Works

Motion Canvas has two parts: a library that uses TypeScript generator functions to program animations, and an editor that previews them in real time. A scene is a generator that creates objects and then yields animation steps in sequence: move this, fade that, wait for the narrator. Animations are drawn with the browser's Canvas API. The editor shows those steps on a timeline, and time events can be placed against an audio track, which suits explainer videos where the animation follows a script. The model is procedural, unlike Remotion's, where each frame is a function of the frame number. That makes Motion Canvas a natural fit for narrated diagrams and a poorer fit for data-driven or templated video.

Rendering happens inside the editor. It plays the timeline and saves each frame as PNG, JPEG or WebP, and an FFmpeg-based exporter, which the docs call still relatively new, writes video with audio. There's no built-in headless or cloud rendering.

### Maintenance and Forks

The core repository's last release was 3.17.2 on December 14, 2024, followed by a 3.18.0 alpha on February 16, 2025. A community pull request opened in September 2026 proposes modernizing the build, test and documentation toolchain, but explicitly without new features. Two MIT-licensed forks carry the project forward:

- **Canvas Commons**, a community fork created in July 2025, released 0.4.0 on September 24, 2026 with text splitting, text on paths, justified wrapping, hand-drawn shapes, animated layouts and faster export. Migrating from Motion Canvas is mostly a package rename.
- **Revideo**, now maintained at `midrender/revideo`, released 0.11.0 on July 10, 2026. It adds headless rendering, a render endpoint and CLI, Cloud Run deployment, parallel rendering, a React player and audio and video export. It sends anonymous render telemetry by default unless that's turned off.

### How It Compares

Remotion is the default for programmatic video in 2026. It's actively developed, renders at scale on AWS Lambda or in the browser, embeds in React apps and ships official Agent Skills that teach coding agents such as [Claude Code](https://metavert.io/claude-code) to write it (see [SKILL.md](https://metavert.io/SKILL.md)). Its cost is a company license for organizations of four or more people. Motion Canvas and its forks are fully permissive and offer the more elegant model for hand-crafted, narrated vector animation. No official agent tooling for them was found as of October 2026, although language models can still write generator-based scenes (see [AI code generation](https://metavert.io/ai-code-generation)). Whichever tool a pipeline uses, AI-written animation code should run in a sandboxed renderer with restricted imports (see [agent sandboxes](https://metavert.io/agent-sandbox)). New projects that want Motion Canvas's approach should start on Canvas Commons for the editor workflow or Revideo for API rendering, rather than the dormant core. For the full comparison, see [Remotion vs Motion Canvas](https://metavert.io/compare/remotion-vs-motion-canvas); for the broader idea, [video as code](https://metavert.io/video-as-code).

## Related Topics

- [Remotion vs Motion Canvas](https://metavert.io/compare/remotion-vs-motion-canvas) — The two code-first animation tools compared
- [Motion Graphics as Code](https://metavert.io/motion-graphics-as-code) — Animation written as components and programs
- [Remotion](https://metavert.io/remotion) — The React-based alternative
- [Video as Code](https://metavert.io/video-as-code) — The broader spec-and-render approach
- [Generative Animation](https://metavert.io/generative-animation) — Other ways to automate animation
- [AI Code Generation](https://metavert.io/ai-code-generation) — Language models writing animation code
- [Agent Sandbox](https://metavert.io/agent-sandbox) — Running AI-written code safely
- [Open Source](https://metavert.io/open-source) — The development model behind Motion Canvas and its forks

## Further Reading

- [Motion Canvas documentation](https://motioncanvas.io/docs/) — generators, the editor and rendering
- [Motion Canvas on GitHub](https://github.com/motion-canvas/motion-canvas) — source, releases and the MIT license
- [Canvas Commons](https://github.com/canvas-commons/canvas-commons) — the community fork
- [Revideo](https://github.com/midrender/revideo) — the fork with headless rendering and a React player