Work on the timeline.
Arrange footage, tune pacing, and make exact changes without losing sight of the film.
A video editor and motion design studio built around your direction. Bring footage, build the scene, and work with the AI assistant you already use.
Editing and motion design belong in the same creative conversation. The rough cut, the graphic idea, and the finishing pass happen in one workspace.
Arrange footage, tune pacing, and make exact changes without losing sight of the film.
Create type, overlays, scenes, and transitions that are part of the edit.
Give an agent a task, inspect the result, then refine it by hand.
Describe the cut you want. Your assistant proposes a plan and makes scoped changes. You decide what stays.
Footage, audio, a script, or a reference.
Ask for pacing, cuts, graphics, or a visual system.
Review every change in the editor and export.
Null Motion is planned to expose editing and motion tools through MCP and CLI. Connect your preferred assistant and keep the project in your hands.
These are captures from the existing Null Motion prototype: a finished reference film playing above the simple drafts it grew from.
One playhead keeps the reference and its rough motion beats together.
Simple drafts make the pacing and visual structure easy to inspect.
Reference footage is by other creators and appears as a study in the prototype. It is not commissioned Null Motion work. The MCP and CLI connection shown elsewhere on this page is still planned.
The local motion engine and launch studio prototype exist today. The unified editor and open agent workflow are the next product steps.
Local generation, rendering, and working browser prototypes.
Footage, timeline, motion, and review in a single workspace.
MCP and CLI tools for assistants you choose.
Creator, Studio, and Team tiers are being defined. Pricing and exact features will be published before paid access opens.
Get launch updates ↗There are working local prototypes for motion generation and a public launch editor concept. The unified product described here is in development.
Those connections are planned through MCP and CLI. This website does not connect accounts or collect provider credentials.
That is the goal. AI should help make changes you can inspect and refine on the timeline and in the composition.
Pricing is not set. We will publish the tiers and their features before paid access opens.
Follow the build, ask about early access, or explore the current public prototype.
Join the waitlist Explore the prototype ↗