Video editorComing soon
A video editor for the devices you already own. Still being built.
This one is not released. There is nothing to download yet and we are not naming a date. What follows is what it is being built to do, and the changelog is where the work actually shows up.
Edit on the machine you have
The plan is one editor on your Mac and your phone, cutting footage where it already sits, rather than an upload queue and a wait.
One project, either device
The edit decision list is the project. Open it on the phone and it is the same cut as on the Mac, because nothing important is hidden in a per-device file.
Undo and sync you can rely on
Every edit is an explicit, named operation: move a clip, trim it, set the playhead. Reliable undo, redo and sync fall out of that instead of being bolted on.
Where it actually stands
In development, not released. We would rather say that plainly than run a countdown we then move. When there is something to install it will appear on the download page, the changelog will say so, and this page will stop writing in the future tense.
- Nothing to download today
- No release date announced, because we do not have one to keep
- Changelog first: that is where a build gets mentioned before anywhere else
The edit decision list is the single source of truth
A project is a list, not a binary blob. It records which media, which in and out points, which effects, in order. Playback, export and sync all read the same list, so what you see on the timeline is what renders and what travels to the other device.
- Media stays where it is; the list points at it rather than swallowing it
- Opening a project on another device replays the list, not a screenshot of it
- A project that serialises and deserialises unchanged is the bar for every release
Every edit is an explicit operation
Drag a clip and what gets recorded is moveClip, not a mutated widget somewhere. Each operation is named and serialisable, which is what makes undo predictable and what lets two devices reconcile a sequence of edits instead of fighting over a file.
- Move, trim, split, set playhead, add effect: each one a discrete operation
- Undo and redo replay operations rather than guessing at the previous state
- Sync reconciles operations, so a conflict is a merge and not an overwrite
Rendering goes through a pluggable target
Export is designed against one interface with more than one implementation behind it. The device's own hardware encoder first, because it is free and fast; a server render as the fallback for the cases a phone cannot finish. The editor itself never talks to an encoder directly.
- Hardware H.264 on the device by default
- Server render as the fallback, not the standard path
- Only permissively licensed codec paths are built in, which is why encoding uses the hardware your device already ships with
Frequently asked questions
Can I use it today?
No. It is in development and there is no build to install. The changelog gets an entry the day that changes, and the download page follows.
When will it be released?
We are not giving a date. A date announced now would only be a date we moved later, so progress is posted as it lands rather than promised in advance.
Which plan will unlock it?
The Editor plan or the Bundle plan. Everything else keeps working without them: Tincograph AI and Nova are on every plan, and the local-only features stay free forever.
Why hardware encoding rather than a bundled encoder?
Licensing. We build only against permissively licensed codec paths, so H.264 goes through the encoder already in your Mac or phone. That keeps the licence position clean and is usually faster than software encoding anyway.
Start with the free plan
Local-only features are free forever, and the free plan includes a monthly credit allowance. No card to try it.