Real answers, no marketing speak

Yes. Compression runs inside your browser tab on your own device. The file you drop in stays in the page's memory and never gets sent over the network. You can confirm by opening DevTools, going to the Network tab, and watching the bytes counter while compression runs. It doesn't move.

No. There isn't an upload step. The page itself is small (around 250 KB), and once the compression code is loaded, everything happens locally on your device. No video data crosses any network.

We don't have your videos. There's no server we could store them on, no dataset to feed them into. The architecture makes it physically impossible regardless of intent.

We log anonymized counts (success or failure, file size in MB, source format, country code) so we can spot bugs and improve the tool. We do NOT log file names, file content, or anything that identifies a specific person. If you'd rather not be counted, an ad blocker or any DNS-level blocker skips the small telemetry beacons cleanly.

Yes. No paid plan, no email gate, no "upgrade to remove watermark" upsell. Because the compression runs on your computer instead of ours, our running cost stays low enough that we don't need to charge.

Most online compressors run the encode on their own servers, which means hardware and bandwidth bills they need to recoup. We pushed the encode to your browser instead. Different architecture, different cost structure.

We set the upper bound at 2 GB. The real ceiling is your device's memory: desktops usually handle 2 GB cleanly, phones tend to struggle past 500 MB to 1 GB. The upload card shows what your specific device can comfortably manage.

No. Some hosted tools throttle free users to 3 to 5 conversions per day. We don't, because each compression costs us nothing.

No. The output is identical bytes to what a paid encoder would produce at the same settings. No logo overlay, no audio jingle, no metadata branding.

No account, no email. Drop the video, pick a target size, click compress, download. The whole flow is anonymous.

Pick the WhatsApp preset on the homepage. We target around 15 MB to leave headroom, since WhatsApp rejects right at 16 MB on some clients. If your source is shorter than a couple of minutes, you can use the Custom slider and aim lower for visibly better quality at the same final size.

Pick the Discord preset, set target to 10 MB. Works for clips up to about 90 seconds at watchable quality. Past that, drop resolution to 720p or below in Advanced Settings.

Same Discord preset, but raise the target to 500 MB. Most full-quality 1080p clips up to six or ten minutes fit without visible loss.

The Email preset targets the lower number (20 MB) so the file works regardless of which provider the recipient uses.

All three preserve original quality at upload, so we target a generous size (200 to 500 MB depending on platform) and let the platform do its own re-encode. Your input quality matters more than your output size for these.

Some loss is unavoidable when you're shrinking the file five to ten times. It's almost always invisible to the eye at the targets we pick. The encoder allocates bits smartly: easy scenes (talking head, slow pan) cost less, action scenes get more. Bigger visible drops happen below 720p or under about 500 kbps.

Modern encoders allocate fewer bits when the source is easy to compress (low motion, static scenes). If you asked for 100 MB and got 45 MB, the output is the same visual quality a 100 MB version would have been, just more efficient. We show a confirmation banner when this happens so it doesn't look like a bug.

Your source was probably already compressed efficiently (low bitrate clip from a phone, for example). Re-encoding it at a generous target adds bits back. The fix is to either lower the target, or accept the source unchanged. We offer both options on the result screen.

MP4 with H.264 video and AAC audio. It plays everywhere: phones, browsers, smart TVs, Discord, every messaging app. We default to this for that reason. MOV is the same family, useful if you specifically want a QuickTime file.

Yes, on Safari and Chrome running iOS 16.4 or later. iOS 26.4 and newer adds hardware video encoding for noticeably faster runs. The practical file size limit on iPhone is around 1 GB before Safari starts releasing memory.

Yes, in Chrome, Edge, or any Chromium-based browser on Android 12 or later. Hardware encoding is available on most modern Android devices, so a 100 MB clip typically takes 10 to 30 seconds. There's also a native Android app with a more powerful engine that works fully offline — see /android.

Yes. The Android app uses a more powerful native compression engine and works fully offline — your phone literally cannot send your videos anywhere because the app declares no internet permission. Faster than browser-based compression, especially on bigger files. Same privacy as the web tool, with native speed.

Chrome, Edge, Brave, Opera, Vivaldi (any recent Chromium-based browser) get the full hardware-accelerated path. Safari 17 and later runs the same path, slightly slower. Firefox 150 and later works but takes around 10 times as long because Firefox hasn't shipped hardware H.264 encoding yet (tracked in Mozilla bug 1918769). We detect Firefox automatically and warn before you start.

Mozilla hasn't enabled hardware H.264 encoding in Firefox yet. We fall back to a pure-software path, which works but runs at roughly 10% the speed of Chrome's hardware path. For a 500 MB clip the difference is around 30 minutes versus 3 minutes. Switch to Chrome or Edge if speed matters.

HandBrake runs natively, so on huge files (multi-GB sources, multi-hour videos) it's still two to four times faster than any browser. For one-off compressions, normal phone-clip sizes under 2 GB, and zero-install convenience, this tool is competitive. Different tools, different sweet spots.

Your original file on disk is untouched. We never modify the source: we read it, build a new file, and try to hand you the new file. If something breaks, the result screen tells you why (low memory, unsupported codec, etc.) and the original is still where it was.

Yes. The review screen has a trim tool, just drag the handles to set start and end. Trimming runs alongside compression so it doesn't add to wall-clock time.

Open multiple browser tabs. Each tab runs an independent compression on your own hardware. We don't gate concurrent jobs because each one costs us nothing.