Shrink a video to the size you need — encoded in your browser, never uploaded.
Your files never leave your browser — all processing is local.
The browser's encoder makes a single pass, so the size can land a few percent off the target; if it goes over, the page says so and lets you try again. Smaller always means softer, and a very small target for a long video won't look good. HDR video comes out as SDR. Speed and quality depend on your computer's encoder. Output is H.264 MP4. Without a save dialog (browsers other than desktop Chrome or Edge) the result is limited to about 1 GB. Files are not uploaded.
Drop a video, choose how small it has to be, and get an MP4 back. The video is decoded and re-encoded inside this tab with the browser's own H.264 encoder, so nothing is uploaded and there is no queue, no watermark and no file-size cap on what you open. On desktop Chrome and Edge the result streams straight into a file you choose; other browsers build it in memory, up to about 1 GB.
Most people arrive with a number in mind: a chat app that refuses anything over 10 MB, an email attachment limit around 25 MB, or an upload form with its own cap. Choose 10, 25, 50 or 100 MB, or type any size from 1 to 4000 MB. Here 1 MB means 1,000,000 bytes, the smaller of the two ways sites count, so the file fits either way. Upload limits change, so check the current one where you are sending. If you just want the file smaller and don't care about an exact number, switch to quality mode and pick high, medium or low instead.
A size target is really a bitrate budget: the same 10 MB that holds a sharp minute holds a blurry ten. The page works out the picture bitrate for your target and length, then lowers the resolution step by step (original, 1080p, 720p, 480p, 360p) until each pixel gets enough data. When even the smallest step would look like mush, it says so and won't start: cut a shorter range on the timeline or raise the target. You can also pin the resolution yourself. The sound is copied untouched when the budget allows; when it doesn't, or when your range starts after 0:00, it is re-encoded at 128 or 96 kbps.
Browser encoders make a single pass, so the output can land a few percent above or below the target. If it goes over, the page retries once on its own at a lower bitrate, then tells you and offers one more try. Smaller always means softer; there is no trick that keeps a long video sharp at 10 MB. Hardware encoders differ, so the same video can come out a little different in size and quality on another computer, and a computer without a hardware H.264 encoder is much slower. HDR video from recent phones comes out as SDR, so colors can look paler. Output is H.264 in MP4; if your browser has no AAC encoder, the sound is saved as Opus and the page tells you.
Drop the video, keep the 10 MB preset, and press Compress. The page plans the bitrate so the file comes in at or just under 10,000,000 bytes, and lowers the resolution if it has to. Discord's free upload limit has changed over the years, so check the current one; if it is different, type that number in the custom box. A long video may be too much for 10 MB, in which case the page asks you to cut a shorter range.
Browser video encoders run once over the video and adjust the bitrate as they go; they can't do a second pass to correct the total. So the size usually lands within a few percent of the target. If it comes out over, the page compresses again automatically at a lower bitrate, and if it is still over, it shows how far off it is and offers one more try. Under the target is fine and is left alone.
Because the picture would be unwatchable. Every second of video needs a minimum amount of data per pixel; a long video squeezed into a small size gets so little that it turns into blocks, even at 360p. Cut a shorter range on the timeline, raise the target, or both. When the result will fit but look soft, the page warns you and still lets you go ahead.
When the budget has room for it, the original audio is copied exactly as it is. When the target is tight, it is re-encoded at 128 or 96 kbps so more of the size goes to the picture, and the page says so before you start. A range that starts after 0:00 always re-encodes the sound. Some browsers, such as Chrome on Linux, have no AAC encoder; then the sound is saved as Opus inside the MP4, which a few older players can't play.
Recent iPhones and many Android phones record HDR video by default. This page outputs standard SDR video and does not tone-map HDR, so bright, saturated scenes can look flatter. The page warns you when it detects an HDR source. If colors matter, switch the phone's camera to SDR before recording, or compress on a desktop tool that tone-maps.
It depends on your computer's video encoder and the video's length and resolution. While it runs, the page shows how many times faster than real time it is going and an estimate of the time left. A computer with a hardware H.264 encoder is much faster than one without. Keeping the screen on (the option is on by default) stops the tab from being slowed down when the display sleeps.
No. The file is read from your disk and decoded and encoded inside your browser; the compressed MP4 is written back to your disk. There is no server in between, which is also why there is no queue, no watermark and no sign-up.