How to compress a video without uploading it

Most online converters are a web page in front of a server. When you press convert, the whole file is sent to that server, processed there and offered back as a download. For a holiday clip that is harmless. For a recording of a client meeting, footage from a clinic, an unreleased product demo, a legal deposition or a video of your children, it means a copy of something sensitive now exists on a computer you don’t control.

Reputable services delete uploads after a few hours and say so in their privacy policies, and most of them mean it. But a policy describes intent, not what physically happened: the file still crossed the internet, sat on a disk, and passed through whatever logging, backups and staff access that company has. If a contract, an employer or a data-protection rule says the footage must not be shared with third parties, an upload converter is a third party, however briefly it keeps the file.

There is a practical cost too. Uploading a 1 GB phone video on a typical home connection takes several minutes before any work starts, and downloading the result takes more. With large files, the upload is often the slowest part of the whole job.

Modern browsers can run serious software. WebAssembly lets a page run compiled programs such as FFmpeg at close to native speed, and WebCodecs gives the page direct access to the video encoder built into your phone or laptop, the same chip your camera app uses to record. A converter built on these has no reason to send the file anywhere: the page arrives with the code, and the code runs on your device.

That is how Compress Video works. When you add a file, the browser reads it from your disk into the tab’s memory. The encoder works through it frame by frame, and the finished MP4 is handed back to you as a download created inside the page. There is no upload step to wait for, which is also why a large video starts straight away instead of after a long progress bar.

The same is true of every tool on FixMyFiles. The only things the browser downloads are the page, its code and, for some tools, an engine or a model the first time that tool is used. Downloads come in; your files never go out.

You shouldn’t have to take a privacy claim on trust, and with a local converter you don’t. Two tests settle it.

Watch the network. On a computer, open the browser’s developer tools (F12, or Cmd+Option+I on a Mac), choose the Network tab, then compress a video. You will see the page’s own files and, the first time, the engine being downloaded. You will not see a request carrying your video out: no request whose size is anywhere near your file’s.

Pull the plug. Load the tool and run it once so its engine is saved, then turn on airplane mode or switch off Wi‑Fi and compress another video. If it finishes with no connection at all, nothing could have been uploaded. The no-upload page walks through both checks in more detail.

FixMyFiles also counts it for you: the bytes-uploaded counter at the top of every page measures every request the page sends out, and it stays at 0 B while you work. The site does run anonymous usage analytics (Microsoft Clarity). It is paused while a tool is working, and the tool area is masked from it, so it never sees a file name or a frame.

1. Trim first. Cutting is free and exact: half the length is half the size, with no change to what remains. Trim Video works on your device too.

2. Add the video to Compress Video. Tap a size limit under the size box (WhatsApp, Discord or Gmail), type your own, or switch to Quality if there is no limit to meet.

3. Lower the resolution if it will be watched on a phone. A 4K recording squeezed into 25 MB looks worse than the same video at 1080p or 720p, because the same bits are spread across four or nine times as many pixels. Set Max resolution to match where it will be watched.

4. Save the result. The file goes to your downloads folder. Closing the tab clears everything the page held in memory; nothing is kept for next time.

Need a different format rather than a smaller file? The same approach applies to MOV to MP4, MKV to MP4 and every other conversion: the file is rewrapped or re-encoded in the tab, not on a server.

Your device does the work, so its speed is your speed. A recent laptop or phone with a hardware encoder compresses a 1080p clip faster than it plays; an older machine working through a long 4K file will take a while, and the tab has to stay open until it is done. A rack of servers is faster on very large jobs, and that speed is what the upload buys you.

Memory is the other limit. Browsers cap how much a single tab may use, and phones cap it lower than computers. Very long, high-resolution files are the ones that reach it; trimming first or lowering the resolution keeps the job within bounds.

Finally, local processing protects the file from the converter, not from wherever you send it next. A video emailed or posted after compressing is subject to that service’s rules, and a phone video can carry the place it was filmed in its metadata. For sensitive material, share it through a channel you trust.