Free · private · in your browser
Choose a quality or file-size target, compare a short draft, and create the compressed video.
Video files grow fast: a minute of 4K phone footage can pass 400 MB, which is too big for most email, chat and upload limits. This compressor re-encodes the picture at a lower bitrate so the file shrinks while the framing, length and audio stay exactly as they were. You can aim at a quality level or at a hard megabyte number.
Two modes cover almost every reason to compress. A quality target keeps a constant visual quality and lets the file land wherever it lands — best when you just want something smaller and still good. An exact size target works backwards instead: you type 25 MB, the tool divides that budget across the video’s duration to derive a bitrate, and encodes to hit it. Use size targeting when a platform enforces a hard cap and quality targeting when it doesn’t.
Compression artifacts show up in specific places — gradients band, fast motion smears, fine text goes soft. Rather than encode the whole file to find out, render a short draft at your chosen settings and watch the part of the clip you care about most. If the draft looks acceptable, run the full export. If it doesn’t, raise the target and try again. A draft of a few seconds costs seconds, while a full 10-minute export costs minutes.
Bitrate dominates, but resolution and frame rate multiply it. A 1080p clip carries roughly four times the pixels of 540p, so downscaling is often a bigger win than pushing the bitrate down and living with blockiness. Long static shots compress far better than handheld footage or confetti, because modern codecs store differences between frames. If a clip refuses to shrink, it is usually because almost every pixel changes every frame.
There is no universal number — it depends on resolution, motion and content. As a rough guide, 1080p talking-head footage holds up around 2–3 Mbps, while 1080p sport or gameplay wants 6 Mbps or more. Render a short draft at your target and judge with your own eyes; that is faster than any rule of thumb.
Yes. Re-encoding is lossy, and the discarded detail cannot be recovered from the compressed copy. Your original file is never modified here, so keep it. If you later need a different size, compress the original again rather than compressing the compressed version, which stacks artifacts.
Yes — leave the dimensions alone and lower the quality or size target. The output keeps the same width and height. That said, if you need a very small file, reducing resolution usually looks better than holding 1080p at a starving bitrate.
Usually because the source was already efficiently encoded — for example an H.265 clip re-encoded to H.264, or a file that was already compressed hard. Re-encoding can only add loss, not undo it. Lower the target further, or accept that this file is already near its floor.
Everything runs inside your browser tab, so the practical ceiling is your device’s memory rather than an upload limit. Multi-gigabyte files can work on a desktop with plenty of RAM but may exhaust a phone. If a long file fails, trim it into parts first and compress each one.
