Discord
Upload clips without Nitro: fit your video to 8, 10, or 25 MB depending on your server's limit.
Compress your video or GIF to the exact size you need
Choose how big you want the final file to be — 5, 8, 10, 25, 50, 100 MB, or any size you like — and the tool adjusts bitrate, resolution, fps, and audio to get as close as possible without going over.
Works with files up to ~500 MB and ~15 minutes long (depends on your device's memory).
Final size
MB
Output format
Audio
Clip trim (for GIF)
GIFs are heavy: we recommend clips under 10s.
The video is encoded in two passes to hit the exact size — this can take longer than a normal compression.
Processing…
0%
Something went wrong
🔒 100% private — your video is processed locally in your browser. Nothing is uploaded or stored on any server.
How it works
Upload your file
Drag in a video (MP4, MOV, WebM, AVI) or a GIF. Everything is processed in your browser, never uploaded to a server.
Choose the exact size
Pick 5, 8, 10, 25, 50, or 100 MB, or enter your own. You can also remove the audio for extra margin.
Download the result
The tool calculates the bitrate and, if needed, adjusts resolution and fps to stay under your chosen size.
What it's for
Any situation where a file has to stay under a specific size limit:
Heavy videos get auto-compressed or fail to send. Set the size beforehand and it arrives intact.
Many providers cap attachments at 25 MB. Prep your video to fit without relying on an external link.
Web forms
Job portals, applications, and paperwork often cap attachment size. Get the size right the first time.
Social media
Shrink files before uploading to platforms with size limits or slow mobile load times.
Support tickets
Attach a video capture of a bug without the ticketing system rejecting the file for being too large.
Compressing video without losing quality: how to get it right
When you shrink a video's file size, what you're really reducing is its bitrate: the amount of data used to describe each second of footage. A smaller file needs a lower bitrate, and a lower bitrate means less detail. The key to a good-looking result isn't blindly "lowering the quality" — it's spending that bitrate intelligently.
That's why this tool first calculates the exact bitrate needed to hit your target size based on the video's actual duration, and only lowers resolution or frame rate automatically if that bitrate falls below a reasonable minimum for decent playback — because a lower-resolution video needs less bitrate to look sharp than the same video at full resolution. It's the same reason a 480p YouTube video looks better on a slow connection than that same video forced into 1080p with too little bitrate.
Removing the audio is another useful lever: the sound track can take up 96 to 192 kbps, which is noticeable in short clips. If the content doesn't depend on sound (a screen capture, a silent demo, a meme), removing it frees up that margin for the image.
With GIF the logic is different: there's no such thing as a "bitrate," so the file size depends on the color palette, resolution, frame rate, and duration. That's why, for GIF, the tool iteratively tries different combinations of fps and resolution to get as close as possible to your target size — and if it still can't get there without looking bad, it tells you and suggests converting it to a short video instead, which for the same content is almost always a fraction of the size of the equivalent GIF.
Frequently asked questions
How does the tool hit the exact target size?
For video, it calculates the bitrate needed from the file's actual duration and encodes in two passes (2-pass) with libx264: the first pass analyzes the video, and the second encodes precisely against that bitrate. It's slower than a single pass, but it's the reliable way to get close to the exact size without going over. GIF has no real equivalent to "bitrate," so it's handled by iteratively trying different combinations of fps and resolution until it gets close to the target.
Does compressing lose quality?
Reducing a video's file size always costs some quality — that's physics, not a trick. The tool prioritizes keeping the bitrate above a reasonable minimum and, if that's not possible at the original resolution, automatically lowers resolution and/or fps rather than forcing too low a bitrate that would look blocky or blurry.
Can I remove the audio to save space?
Yes. Removing the audio frees up all the bitrate the sound track was using, redirecting it to the image. The tool shows you how much extra size you'd gain before you decide.
What happens if the size I want is impossible to hit at good quality?
We tell you clearly instead of pretending the target was hit. We verify the actual size of the generated file, and if the requested limit couldn't be reached (or only at the cost of looking very bad), we show you that and suggest alternatives: raising the limit, removing the audio, trimming the duration, or, for GIF, converting to a short video.
What input and output formats are supported?
As input it accepts MP4, MOV, WebM, AVI, and GIF. As output it generates MP4 (H.264, the most widely compatible option) or GIF — including converting a short video to GIF or a GIF to video, which usually weighs much less.
Are my files uploaded to a server?
No. The whole process happens in your own browser through a compression engine that runs locally (ffmpeg compiled to WebAssembly). Your video never leaves your device, isn't stored anywhere, and requires no sign-up.
Why does video compression take so long?
Two-pass encoding is slower than a single pass because the video is analyzed twice, but it's the only reliable way to hit the actual target file size. Also, all the work is done by your own device (not a server), so the time depends on how powerful your computer or phone is.
Is there a limit on the file size or duration I can upload?
Yes, due to the memory available in the browser: up to about 500 MB of input file and about 15 minutes of duration. If your file exceeds these limits, we let you know before starting, so the tab doesn't lock up.