Video Compressor
Make videos smaller for email, chat or upload — entirely in your browser. Your file is never uploaded to a server; the whole process runs on your device. Free, private and watermark-free.
- No login required
- Files never stored
- Free forever
Your video is processed in your browser and never uploaded.
Video compressor
Compress video without uploading it
Sending a big video over email or chat is a pain, and most compressors upload your file to their servers first. This tool runs entirely in your browser using WebAssembly, so your video never leaves your device. Pick a clip and we re-encode it to a much smaller MP4 while keeping it sharp.
Choose the video you want to shrink
Click Choose a video and pick a file up to 200 MB. Nothing is transmitted — the browser reads the file locally, so even a large clip is available to the tool immediately.
Press Convert and let your device work
The engine loads on first use (about 31 MB, cached afterwards), then re-encodes the video with a progress percentage. You can watch the counter, but leave the tab open — the work is happening in it.
Check the before and after size
When it finishes, the tool shows the original size next to the new size, and the percentage saved when the result is genuinely smaller. Preview the video to confirm it still looks right, then download the MP4.
What the compressor changes, and what it leaves alone
The video is re-encoded to H.264 at a constant-quality setting of CRF 30, with AAC audio, into an MP4 container. Constant quality is the important part: rather than forcing your video to hit a fixed bitrate, the encoder spends only as many bits as each scene needs to hold a set quality level, so a static talking-head shot compresses enormously while a handheld shot of moving leaves compresses much less. CRF 30 sits toward the aggressive end of the usable range — you are trading visible fidelity for size on purpose. Your resolution and frame rate are not touched. A 1080p60 video comes out 1080p60, just with far less data behind each frame, which is why the result still fills a screen properly instead of looking like a thumbnail.
How much smaller your file will actually get
There is no honest single number here, and any compressor promising one is quoting its best case. The saving depends almost entirely on how much bitrate the original was carrying. Screen recordings, drone footage, exports from editing software and anything straight off a DSLR are usually stored at bitrates far higher than the picture needs, and those files often drop by most of their size. Video that has already been squeezed once — a clip downloaded from a social app, a file a messenger already re-encoded, or an efficiently encoded HEVC phone recording — has little slack left, and re-encoding it can produce a file the same size or even slightly larger. That is why the tool reports the real before and after figures for your specific file rather than advertising a percentage: if the output comes out bigger, it shows you both numbers and claims no saving, and you can simply keep your original.
Getting under a specific size limit
Common targets are 25 MB for email attachments, 8 MB for a standard Discord upload and 16 MB for WhatsApp. One pass at CRF 30 clears those limits for most short clips. If it doesn't, length is usually the problem rather than quality — file size scales roughly linearly with duration, so a 90-second clip trimmed to 30 seconds ends up around a third of the size with no further quality loss. Trim first, then compress the shorter file. Compressing an already-compressed output a second time will shave a little more off but degrades the picture quickly, so it is worth trying the trim route first.
How long compression takes
Compression is the heaviest thing this toolkit does, because every frame is decoded and then re-encoded. The engine is single-threaded, which keeps the tool compatible with every browser but means it is slower than desktop software. Expect a one-minute 1080p clip to take a few minutes on a modern laptop, longer on a phone, and considerably longer again for 4K source footage. The tab needs to stay open and in the foreground on mobile, since background tabs get throttled. If you are compressing something long, trimming it first speeds up the encode as well as shrinking the result.
If something goes wrong
A failed conversion usually means the browser ran out of memory for the tab, which happens most often with long 4K files; trimming first is the reliable fix. Files above 200 MB are rejected before the encode starts. If the output looks soft or blocky in fast motion, that is CRF 30 doing what it was asked to do — high-motion footage needs more bits to stay clean, and this setting deliberately does not give them. If the output is larger than the input, your source was already efficiently encoded and there is nothing to gain; keep the original.
Private by design
Because compression happens on your device, your video is never sent anywhere and nothing is stored. This is the one thing a server-based compressor structurally cannot offer: uploading to shrink a file means handing a copy to someone else's infrastructure, which is a genuine problem for screen recordings of internal tools, client work under NDA, medical or legal footage, and anything involving family. Here the file stays in the tab. It works on desktop and modern mobile browsers — the first run downloads the engine once, then later runs are instant.
Frequently asked questions
Answers to the most common questions about using these free video & audio tools.
No. The entire compression runs in your browser with WebAssembly, so your video never leaves your device and nothing is stored on any server.