Premation

An open-source motion editor for the desktop. Compositions, layers, keyframes, a graph editor, 3D space with cameras and lights, effects, masks and mattes, per-glyph text animators, mesh rigging, particles, and a deterministic export pipeline — built on a GPU render engine that runs on WebGPU or WebGL2.

It is modelled on After Effects' Classic 3D workflow: if you know AE, the tools, the panel layout and most of the keyboard shortcuts are already where you expect them.

Electron + React + TypeScript. Everything renders through one engine, the same engine that exports, so what you see in the viewport is what lands in the file.

License: GNU AGPL v3.0 · Status: pre-1.0, in active development

We're live on Product Hunt — an upvote helps more people find the project:

---

Contents

• Two editions
• Quick start
• Requirements
• What's in the box
• Export
• Projects on disk
• The AI assistant
• Repository layout
• Plugins
• Testing
• Packaging a release
• Contributing
• Documentation
• License

---

Two editions

The same source tree builds two editions, chosen at build time with VITE_EDITION. This exists because the editor is open source while the hosted backend service is not.

	local (VITE_EDITION=local)	server (default)
Accounts / sign-in	none — opens straight into the editor	required
Projects	on disk, .motion bundle	cloud, with autosave
Assets	on disk, content-addressed	cloud library
Export	local ffmpeg	local ffmpeg
AI assistant	bring-your-own-key (OS keystore)	via the hosted gateway (BYOK keys stored server-side)
Billing / sync / plugin registry	absent	available

The local edition is the one to build from this repository. It does not talk to a Motion backend: the API layer refuses those calls, so an offline build cannot quietly phone home for accounts or cloud projects. The assistant, when you connect your own provider key, reaches OpenAI / Anthropic / Gemini from the desktop shell — that is intentional BYOK, not telemetry. The server edition targets a backend service that is not part of this repository, so its cloud features will not work without one.

Read the edition as a capability, never as a flag — see src/core/config/edition.ts.

Quick start

git clone https://github.com/isroil01/motion-editor.git

cd motion-editor && npm install

Run the desktop app:

npm run electron:dev:local

That compiles the Electron main process, starts Vite, and opens the app. Edits to renderer code hot-reload.

To run just the renderer in a browser tab (faster, but no filesystem, native menus or ffmpeg export):

npm run dev:local

Both :local scripts set VITE_EDITION=local. Dropping the suffix (npm run electron:dev) builds the server edition, which will sit on a sign-in screen unless you point it at a backend.

Requirements

• Node.js 20 or newer and npm.

• A GPU that supports WebGPU or WebGL2. The engine picks WebGPU when available and falls back to WebGL2; there is no software rasteriser.

• ffmpeg, for .mp4 / .mov export only. Everything else — including the editor itself and webm/GIF/PNG/Lottie export — works without it. The app looks for ffmpeg in this order:

  1. $FFMPEG_PATH
  2. a binary bundled next to the packaged app
  3. ffmpeg on your PATH

  If it finds none, mp4 export fails with a message saying exactly that, and nothing else is affected.

Linux, macOS and Windows are all supported by the toolchain. CI currently exercises the render tests only.

What's in the box

Counts below were taken from the source, not from memory — if you change a registry, this section is expected to drift, so re-check before quoting it.

Compositing and layout

• Nested compositions and comp instances, with collapse-transformation
• 2D and 3D layers in one space, with cameras and lights (parenting included)
• Masks, track mattes, blend modes, layer styles
• Shape layers, paths, trim paths, repeaters, path operations
• 204 effects (src/core/effects/effects.ts)

Animation

• Keyframes with full easing control and one graph editor, shared by the timeline and the Motion panel — Animated/Selected modes, a frozen reference curve, rove, and a library of saved ease curves
• 84 presets — 15 animation, 18 text, 6 behaviour, 6 camera, 5 scenery, 34 film look — plus your own, saved from any layer and exported as a shareable file
• Per-glyph text animators with a real selector stack
• Expressions, with caret autocomplete
• Modifier stacks — ordered offset / wiggle / spring / loop / delay / audio rows per property, compiled to one expression and edited as sliders
• Parametric stagger across a selection, audio-reactive drivers, and bake-dynamics that turns a simulation into ordinary keyframes
• Bone and puppet mesh rigging (FK, linear-blend skinning, FABRIK IK, ARAP)
• Particles, motion blur, motion paths

Editing footage

• A source monitor — in/out in source seconds, JKL shuttle, insert / overwrite / add to end / new comp from range
• Razor, slip, slide and roll as visible timeline tools, with clip-edge snapping
• Per-cut transitions you can select, lengthen and remove — cross dissolve, dip to black or white, wipe
• Assemble from Footage: detect the cuts in a rush, drop the runts, sequence the rest with dissolves, one undo
• Scopes — waveform, RGB parade, vectorscope, histogram
• A transcript panel with text-based editing: select words, delete the time range from every layer at once
• Silence removal and ducking, both as editable keyframes

3D

• Cameras, five light types, extrusion and bevels, per-face materials
• Imported glTF/GLB models as ordinary layers, with skinning, morph targets, baked clips and 3D IK (docs/3d-layer-model.md)
• Curved primitives — sphere, cylinder, cone, torus, capsule, box
• An environment light fed by any image or EXR, giving both irradiance and split-sum reflections, plus the glTF PBR map set

Import

• Video, audio and images
• SVG — static files import as one intact layer; animated SVG (CSS or SMIL) converts to keyframes
• Lottie / Bodymovin
• Captions — .srt / .vtt in and out, or generated from the composition's own audio (docs/CAPTIONS.md)

Delivery

• premation render — render a project from a terminal, with no editor open (docs/CLI.md)
• Data-driven batches — one file per row of a CSV, filled through template fields
• Auto-reframe — retarget a composition to 9:16, 1:1, 4:5 or 16:9, following the subject and cutting where the edit cuts (docs/AUTO_REFRAME.md)

Engine

• One GPU render graph, WebGPU or WebGL2, used by the viewport and the exporter
• 3D transforms, extrusion, bevels, per-fragment shading, image-based lighting
• A render queue that pauses and resumes within a session, keeping staged frames
• Golden-image render tests to keep output stable across refactors

Export

mp4, mov, webm, GIF, PNG/JPG sequences, and Lottie/JSON.

Frames are rasterised by the same engine that draws the viewport, streamed to disk one at a time (so peak memory is one frame, not the whole render), and muxed by a local ffmpeg process. A long export leaves the app usable.

Projects on disk

A project is a .motion directory bundle, not a single opaque file:

MyProject.motion/
├── manifest.json          written last, so a crash can't corrupt the bundle
├── scene.json             ├─ separate chunks, content-hashed, so a save
├── animation.json         │  writes only what actually changed
├── timeline.json          │
├── meta.json              ┘
├── assets/                imported media, addressed by SHA-256
└── versions/              local version history, structurally shared

Saving is incremental and version history is local — snapshots share unchanged objects rather than storing full copies, so an animation-only change costs one new object.

The AI assistant

The editor contains a complete AI layer: 65 AI tools it can call, an agent loop, a deterministic "caster" pipeline that assembles motion from a hand-authored technique library, and a self-critique pass.

Both editions include it. Keys never enter the renderer:

• Local — you paste an OpenAI / Anthropic / Gemini key into Settings → AI. The desktop shell stores it in the OS keystore (safeStorage) and makes the provider call from the main process (electron/aiProxy.ts, including ai:image for generated imagery).
• Server — the same settings UI uploads the key to motion-back, which encrypts it at rest and proxies POST /ai/stream / POST /ai/image.

aiEnabled() in src/core/config/edition.ts is the surface gate (on in both editions). aiRunsThroughBackend() picks the transport. Everything else in the editor still works fully offline when you are not using the assistant.

Repository layout

src/
├── core/          document model, engine glue, commands, export, AI, plugins
│   └── config/    edition + feature flags
├── layout/        panels — timeline, inspector, workspace, effects
├── components/    reusable UI primitives
├── stores/        Zustand state
└── routes/        app shell and routing
packages/
├── scene/         scene graph, transforms, hit-testing
├── animation/     keyframes, easing, evaluation
├── timeline/      timeline model
├── renderer/      GPU render graph (WebGPU + WebGL2)
├── audio/         audio graph
├── workspace/     viewport interaction, gizmos
├── ai-tools/      the tool registry the assistant calls
├── caster/        deterministic generative pipeline
├── technique-library/ hand-authored motion techniques
├── design-system/ look packs and design tokens
├── product-motion/ UI-motion technique packs
└── render-tests/  golden-image harness
electron/          main process, IPC, native integration

Plugins

Plugins are packages — a plugin.json manifest plus an ES module — that run in a dedicated Worker sandbox. Permissions are shown and accepted before any plugin code is loaded anywhere, and packages are signed.

See docs/PLUGINS.md for the architecture and the authoring guide. Installing from a local file works in every edition; the hosted registry does not exist in the local edition.

Testing

npm test

Roughly 440 suites and 4,800 tests, and they are fast (under a minute). Also:

npm run typecheck

npm run lint

Golden-image render tests compare real GPU output against committed reference frames:

npm run render-tests

npm run render-tests:update

Only update goldens when you have looked at the diff and can say why the new pixels are correct.

Packaging a release

npm run dist:local

Produces an installer in release/ via electron-builder. npm run pack:local builds an unpacked directory instead, which is much faster for testing.

Contributing

Contributions are welcome — see CONTRIBUTING.md for how to set up, what the review bar is, and which areas need help. By participating you agree to the Code of Conduct.

Security issues should not be filed as public issues — see SECURITY.md.

Documentation

Start here: docs/EDITOR_REFERENCE.md — what the editor does, what it does not, and an honest gap analysis against After Effects. Its feature counts are derived from the registries by scripts/featureCounts.cjs and pinned by src/__tests__/docFeatureCounts.test.ts, so they cannot silently go stale.

Deep dives on individual subsystems:

• docs/3d-layer-model.md — the 3D model, and where it departs from After Effects
• docs/BONE_AND_PUPPET_RIGGING.md — mesh deformation, the math and the current gaps
• docs/ANIMATED_SVG_PIPELINE.md — SVG import, end to end
• docs/PLUGINS.md — plugin architecture and authoring
• docs/MOTION_FORMAT_FREEZE.md — what the .motion bundle is, the six migrations behind it, and what a 1.0 compatibility promise would actually require
• docs/CLI.md — headless rendering and data-driven batches
• docs/CAPTIONS.md — subtitles in, out, and from speech
• docs/AUTO_REFRAME.md — how the crop decides where to look, and why it jumps at cuts
• docs/PICK_WHIP.md — drag-to-link, and how a panel becomes a drop target

Prose drifts faster than code. Where a document and the source disagree, the source is right — and a PR fixing the document is very welcome.

License

Copyright © Premation contributors.

Licensed under the GNU Affero General Public License v3.0 only. The full text is in LICENSE.

In short: you may use, study, modify and redistribute this software, but derived works must also be licensed under the AGPL and must carry the same source-code offer. Section 13 matters in particular — if you run a modified version as a network service, you must offer its users the corresponding source.

The AGPL covers this repository. It does not cover the separate hosted backend service, which is not distributed here.