Your video never leaves your device
This is a fully client-side video compressor. The file you choose is read and compressed locally — there is no upload, no server, and no copy of your video anywhere but your own machine.
Drop a video here, or browse
MP4 · MOV · WebM — compressed right here, nothing uploaded
100% on-device · no signup · no watermark
Loading compressor…
Bigger files take longer — your CPU does the work, privately.
Don’t trust us — verify it
Privacy claims are cheap. Here are three ways to prove this one in under a minute.
- 1
Disconnect from the internet
Compress one clip first (that loads the engine once). Then turn off Wi-Fi and compress another — it still works, because your video never needs to be sent anywhere.
- 2
Watch the Network tab
Open your browser’s DevTools → Network tab before compressing. You’ll see the one-time download of the compression engine, and then no upload of your video at all.
- 3
Check the file size moving
There’s no progress bar for an “upload” because there is no upload. The only progress is your CPU encoding the video locally.
How it works under the hood
When you pick a video, the page loads a WebAssembly build of FFmpeg — the same open-source engine used across the industry — directly into your browser. Your video is handed to that engine in memory and re-encoded to a smaller H.264 MP4 on your own CPU. The result is offered back to you as a download. At no point is the video data sent over the network.
The trade-off of doing everything locally is speed: your device, not a server farm, does the encoding. That’s why a big 4K file takes longer — and why your footage stays completely private.
Frequently asked questions
What does “client-side” mean?
It means all the processing happens on your own device, in your browser, instead of on a remote server. Your video file is read locally and compressed locally — it’s never transmitted.
How can I be sure my video isn’t uploaded?
Compress once to load the engine, then disconnect from the internet and compress again — it still works. Or open DevTools → Network and watch: you’ll see the engine download once from a CDN, but no upload of your file.
What is actually downloaded, then?
A one-time copy of the open-source FFmpeg WebAssembly engine (cached after the first use). That’s code coming to you — your video never goes the other way.
Why is client-side better for privacy?
Your footage never touches a third-party server, so it can’t be stored, leaked, or scanned. That matters for personal clips, client work, and anything confidential.