Video Editor

A video editor takes several pieces of footage and turns them into one finished video. You put the clips in an order, cut each one down to the part that earns its place, decide how the result should look and sound, and export a single file. That is the whole job, and for most videos it is genuinely all that is needed: three clips from a phone joined in the right order, the dead air trimmed off each one, the whole thing dropped to 720p so it uploads before you lose patience.

This one runs entirely in your browser. Each file is read from your disk into the page, edited there, and handed back as a download. Nothing is uploaded, there is no render queue, and no copy sits on a server to be deleted later, because none was ever made. For video that matters more than it does for most file types. A clip is usually the largest and most personal thing anyone edits, and the normal arrangement for a free online editor is that you hand a stranger your footage and trust a retention policy you did not read. The work here is done by ffmpeg compiled to WebAssembly, the same engine most desktop editors use underneath, running in the tab instead of on a machine you do not control.

Joining clips is harder than it looks, and it is worth knowing why the export re-encodes. Two files can both be MP4 and still differ in resolution, frame rate, pixel format, audio sample rate and timebase. Putting them end to end only works when all of that already matches, which is true when the clips came off one camera in one session and false the moment a phone clip meets a screen recording. Rather than refuse the mixed case or produce a file that plays the first clip and then freezes, this builds a filter graph: every clip is trimmed, its timestamps are rebased to zero, and the streams are concatenated inside the graph before a single encode writes the result. That costs time and it is the reason an export is not instant, but it means footage from two different sources joins correctly instead of failing in a way that is hard to diagnose.

The settings are deliberately few. Resolution, speed, audio on or off, and the container. Each one is a decision that changes the output meaningfully, and leaving out transitions, titles, colour grading and layered tracks is a choice rather than an omission: those need a timeline UI and a render pipeline that a browser tab is the wrong place for. If you want them, a desktop editor is the right tool and we would rather say so.

The limits come from the browser, not from a paywall. A tab has a memory budget, so the timeline takes up to eight clips and the finished video is capped at thirty minutes. Within that it is comfortable. Past it, a desktop editor will be faster and will not run out of memory halfway through. MP4, WebM, MOV and MKV all open. The export is MP4 or WebM, with no watermark on it and no account to create.