Browser-local editing
Video Editor With No Upload
The unusual thing about this editor is the part that does not happen. When you drop a video file onto the page, there is no POST request, no multipart upload, no chunked transfer. The browser reads the file off your disk into memory and runs the decode, compositing, and encode steps through WebCodecs, the hardware-backed video API built into the browser itself. Nothing is handed to a server.
Project picker
Multi-track editing with WebCodecs · Frame-accurate seek · Source monitor
New Project
About Video Editor With No Upload
You can verify this yourself. Open DevTools in this tab, switch to the Network panel, filter to XHR and fetch requests, then drop a file in and hit Export. You will see the page's own files and a few small anonymous usage events, none of which carry your media. You will not see your video going anywhere. That check takes 30 seconds and it is the only honest way to tell whether any editor is actually browser-local or just claims to be.
What you give up with this architecture is collaboration. Two people cannot work on the same project at the same time because there is no shared server to synchronise state through. What you gain is that no server operator, no cloud vendor, no foreign-adversary classification, no data-breach notification law applies to your footage, because no one but you ever has the bytes. That tradeoff fits a narrow set of use cases well and the broad general-purpose editing case poorly, which is why we lead with it instead of hiding it.
When to use this editor
Unreleased product demos
Marketing footage of a product under embargo cannot be uploaded to a cloud editor without breaking the NDA. Browser-local editing keeps the clip on your laptop.
Medical and educational recordings
Patient consent and student privacy rules are simpler to comply with when the video never leaves the device in the first place.
Slow or restricted networks
Once the page has loaded, editing and export do not depend on bandwidth. Useful on trains, in locked-down offices, or wherever uploading a large file is not an option.
Sensitive investigation footage
HR investigations, legal depositions, and compliance reviews all benefit from a workflow where the footage cannot be accidentally synced to someone else's server.
Quick utility edits
Trim a Teams recording, adjust a screen-capture, clip a highlight. No account setup, no upload wait, no sign-in loop.
How to Edit a Video Without Uploading
1 Open the editor in your browser
Load this page. The editor is part of the page; there is no separate engine to download.
2 Drop the file in
Drag a video onto the source bin, or use the file picker. The bytes go into browser memory, not over the network.
3 Edit and verify in DevTools
Trim and arrange clips on the timeline. Open the Network tab to confirm no outbound requests include your media.
4 Export locally
Click Export. WebCodecs encodes the timeline inside the tab and saves the MP4 back to your device.
Frequently asked questions
How does a video editor work without uploading?
The browser reads the file off your disk using a standard file input. The bytes stay in browser memory. WebCodecs decodes the frames, the editor composites your transforms and edits, and WebCodecs encodes the result. The final file is written back to your disk. No network request involves your media.
Is browser processing slower than cloud rendering?
For long edits it can be slower, yes, because a single laptop CPU competes with a rack of cloud servers. For short and medium edits the difference is negligible once you account for the upload and download time that the cloud flow adds. A 60 second clip is usually faster end-to-end in the browser than the equivalent cloud workflow.
Does this editor work offline?
Partly. There is no installable offline version, so loading the page needs a connection. After that, your media is decoded, edited, and encoded on your device, and losing the connection mid-export does not stop the export.
How do I verify that nothing is uploaded?
Open DevTools, switch to the Network tab, filter to fetch and XHR requests. Drop a video in and edit it, then export. Nothing in that list comes anywhere near the size of your file; the only requests are the page assets and small anonymous usage pings. This check works against any web app claiming to be browser-local.
Do I need a powerful computer for this to work?
Any modern laptop from the last five years handles 1080p editing without trouble. 4K needs more memory and a reasonably recent CPU, roughly an Intel 10th-gen or Apple M1 equivalent and above. Chrome and Edge tend to perform best because WebCodecs support is most complete there.
What video formats work without upload?
MP4, MOV, and WebM video, and common audio files like MP3, WAV, and FLAC. AVI and MKV are not supported; convert those first. Exports are H.264 and AAC in an MP4, with VP9 and Opus as the fallback on browsers without those encoders.
Your video never leaves your device
All processing happens locally in your browser, and your files never leave your device. The editor reads your video file through a standard browser file input, holds the bytes in memory, decodes and re-encodes them with WebCodecs inside the tab, and writes the final MP4 back to your disk. No upload, no cloud rendering, no external copy.
Related Tools and Resources
Private video editor
Privacy framing for teams that need more than the architectural story.
CapCut alternative
Specific alternative for users coming off CapCut.
Video editor, no signup
Zero-friction version that skips account creation too.
Free video editor, no watermark
Browser-local and watermark-free.