Video Editors
Editing tools that work on the file rather than a copy of it on someone else’s server. The clip is read straight from your disk into the page, cut there, and handed back, so nothing is uploaded and no stored copy exists to be deleted later.
Showing 2 tools
Video Trimmer
Cut a video down to the part you want, in your browser. Set a start and end, preview the cut, and export without uploading the file anywhere.
Video Editor
Join several clips into one video, trim each of them, reorder them, and set the resolution, speed and audio. Everything runs in your browser, so nothing is uploaded.
Editing video in a browser has usually meant uploading the file, waiting in a queue and trusting a retention policy you did not read. Neither tool in this category works that way. The video trimmer cuts one clip down to the stretch you want. The video editor takes up to eight clips, trims each of them, puts them in order and writes a single file. Both read the footage from your disk into the page, edit it there, and hand it back as a download.
The work is done by ffmpeg compiled to WebAssembly, which is the same engine most desktop editors use underneath, running in the tab instead of on a machine you do not control. That decides both what these tools are good at and where they stop. One cut on one clip is close to instant. A timeline of eight clips at 1080p is a real encode and takes real time. A two-hour recording belongs in a desktop editor, and a single export here is capped at thirty minutes for exactly that reason. Changing the format rather than the content, or lifting the audio out of a clip, is converters, and sizing the result for one platform in particular is social media tools.
Which of the two to open, and what each job costs you in time
| What you want to do | Tool | What to know |
|---|---|---|
| Cut the start or the end off one clip | Video trimmer | Fast mode repackages the streams without decoding them and finishes almost immediately |
| Pull one exact section out of a recording | Video trimmer | Accurate mode lands on the frame you picked, re-encodes, and takes considerably longer |
| Join clips that came off one camera | Video editor | They join top to bottom, in the order you set |
| Join a phone clip to a screen recording | Video editor | Mismatched frame rates and pixel formats are rebuilt in a filter graph so the result does not freeze after clip one |
| Trim several clips and keep them as one video | Video editor | Every clip holds its own in and out points, and one export writes the lot |
| Drop a video to 720p, or run it at 2x | Video editor | 1080p, 720p or 480p, 0.5x to 4x, with the audio pitch-corrected rather than left to drift |
| Remove the sound | Video editor | Audio on or off is a setting on the export |
| Transitions, titles, colour grading, layered tracks | Neither | Those need a timeline UI and a render pipeline a browser tab is the wrong place for |
Fast or frame-accurate: which cut to ask for?
A trim can be done two ways and the difference decides how long you wait. Copying the streams is the default: the existing video and audio are repackaged into a new container without being decoded, so nothing is re-compressed, no quality is lost, and a long clip finishes in about the time it takes to write the file. The catch is that a stream copy can only cut cleanly on a keyframe, and keyframes are typically one or two seconds apart, so the real start can land slightly earlier than the timecode you typed.
Frame-accurate mode decodes the section, lands on the frame you chose, and encodes it again. It is the right choice when the first word of a sentence matters or you are cutting to a beat, and the wrong choice when you are lopping dead air off the end of a screen recording. The video trimmer offers both on the same screen; pick fast first and only switch when the cut lands in the wrong place.
Why joining clips takes longer than cutting one
Two files can both be MP4 and still disagree about resolution, frame rate, pixel format, audio sample rate and timebase. Putting them end to end without touching them works only when all of that already matches, which is true for clips shot in one session on one camera and false the moment a phone clip meets a screen recording. Tools that skip the check are the reason you have seen a joined video play the first clip and then freeze.
The browser video editor builds a filter graph instead: each clip is trimmed, its timestamps are rebased to zero, the streams are concatenated inside the graph, and one encode writes the output. Mixed sources join correctly, and the price is that joining can never be a stream copy. A short timeline at 480p is quick; several clips at 1080p is where you go and make coffee.
What leaves your machine
Nothing. Each file is read from your disk into the page and edited inside the tab. No server receives the footage, nothing is queued, and there is no stored copy to delete afterwards because none is ever made. You do not have to take that on trust: open devtools, switch to the network tab, and run an export. No request carries the file.
That matters more for video than for most file types. A clip is usually the largest and most personal thing anyone edits, and the standard arrangement for a free online editor is that you hand a stranger your footage in exchange for a download link. The only thing fetched here is the WebAssembly build of ffmpeg itself, a few megabytes on first use, which the browser then caches. After that the editing needs no network at all.
What a browser tab can hold
A tab has a memory budget, and every clip on a timeline costs a decode pass inside it. The limits follow from that rather than from a paid tier: eight clips on one timeline, thirty minutes on a finished video. Within those numbers both tools are comfortable on a laptop. A phone runs them, but with a tighter memory budget and a much slower encode, so two short clips at 480p or 720p is a realistic ask and a long 1080p timeline is not.
MP4, WebM, MOV and MKV all open. A trim keeps the format it came in as. A joined export is MP4 with H.264 and AAC, or WebM with VP9 and Opus: MP4 is the safer file to send someone, WebM usually lands smaller at the same visible quality and encodes more slowly in a browser. Neither output carries a watermark, and neither tool has an account, a trial or a feature held back behind one.
Frequently asked questions
Should I use the trimmer or the editor?
One clip and one cut, use the video trimmer: it can copy the streams untouched and finish in seconds. More than one clip, or one clip that needs its resolution, speed or audio changed, use the video editor. The editor trims too, so there is no need to trim first and join afterwards.
Is any of my footage uploaded?
No. Both tools read the file from your disk into the browser tab and do the work there with ffmpeg compiled to WebAssembly. Nothing is sent to a server, so there is no queue, no retention policy and no copy to delete. Watching the network tab in devtools during an export is the quickest way to confirm it.
Why did my cut start a second before the timecode I typed?
Because it was a stream copy, and a stream copy can only cut on a keyframe. Keyframes sit one or two seconds apart in most footage, so the cut lands on the nearest one at or before your mark. Switch the trimmer to frame-accurate mode and it will decode, land on the exact frame, and take longer doing it.
Does the quality drop?
A fast trim loses nothing at all, because the video is never decoded. A frame-accurate trim and any joined export re-encode, which is lossy by definition, though at the default settings the difference is hard to see on normal footage. Dropping the resolution to 720p or 480p is a deliberate quality change, and that one you will notice on a big screen.
How long a video can I edit here?
Thirty minutes on a finished export, and eight clips on one timeline. Both numbers come from the memory a browser tab is given rather than from a pricing page. For a two-hour recording, a desktop editor is the right tool and will be faster as well.
Can I add transitions, titles or background music?
Not in these tools. A layered timeline and a render pipeline are a different job, and something that half-supports transitions is worse than something that joins and cuts properly. What is here covers the edit most videos need: order the clips, trim each one, set the output.
Is there a watermark on the result?
No, on either tool. The export is your footage and nothing else, with no overlay, no corner logo and no bumper. There is no account to create, no emailed download link and no trial that expires.
Will it work on a phone?
It runs, with caveats. Phones have less memory to spare and encode a good deal more slowly, so a couple of short clips at 480p or 720p is realistic and a long 1080p timeline is not. On a desktop browser neither limit bites.