Your Discord video is too large. The free limit is 20 MB now.
A lot of Discord compressor pages still talk about 8 MB or 10 MB. Discord changed the free upload limit to 20 MB in August 2026. If your gameplay clip or meme is still too large, make a smaller sharing copy locally instead of uploading the raw video to another conversion service.
Why so many Discord guides still say 8 MB or 10 MB
Those numbers were real at different points in Discord's history. They are simply stale now. This matters because a target-size compressor is only useful when the target matches the platform you are actually sending to.
As of August 2026, Discord says the free limit is 20 MB. It also changed mobile behavior so file size is checked before compression, matching desktop. In practice, that means the source file has to be under the applicable attachment limit before Discord accepts it; you cannot assume the mobile app will rescue an oversized video for you.
For a free account, aim a little below 20 MB
If the only goal is to get a clip through Discord, I would not target exactly 20.00 MB. Give yourself some margin. An 18–19 MB sharing copy is usually a more comfortable target than trying to land on the boundary byte-for-byte.
The file-size math is straightforward: duration determines how much bitrate you can afford. A 15-second gameplay clip has much more bitrate available per second than a three-minute clip if both must fit under the same cap. That is why there is no honest “best Discord quality” setting that works for every video.
| Destination | Official attachment cap checked Sep. 17, 2026 | Practical compression target |
|---|---|---|
| Discord Free | 20 MB | About 18–19 MB if you want margin |
| Nitro Basic | 50 MB | About 47–49 MB if the source needs shrinking |
| Nitro | Up to 500 MB | Only compress if size, transfer speed or convenience matters |
Gameplay clips: cut duration before destroying quality
For game footage, the fastest route to a better-looking small file is often trimming dead time. A 90-second clip with 30 seconds of menus and waiting is asking the encoder to spend bits on frames nobody cares about.
Fast camera movement, particles, grass, rain, film grain and HUD text are all expensive to compress. If a long 1080p60 clip has to fit under 20 MB, something has to give. My order is usually: remove dead time, then lower bitrate, then consider 720p, and only then reduce frame rate if motion still looks acceptable.
Memes and screen recordings need different treatment
A meme clip with a mostly static frame can survive a much lower bitrate than a competitive shooter highlight. Screen recordings with small text are the opposite: dropping resolution too aggressively can make UI labels unreadable even when the overall image looks “fine.”
- Fast gameplay: preserve motion first; try shorter duration and sensible bitrate before cutting frame rate.
- UI-heavy screen recording: protect text readability; 1080p at a lower bitrate can beat 720p if tiny text matters.
- Short meme/reaction clip: usually easy to push below 20 MB without dramatic damage.
- Long cinematic clip: consider whether a link or a higher Discord tier makes more sense than crushing several minutes into 20 MB.
No-upload compression changes one important tradeoff
A lot of online video tools start with an upload. That is convenient when you want server-side codecs or editing, but it also means the original gameplay recording, private call capture, unreleased trailer, moderation evidence or client clip leaves your device before it gets smaller.
CreatorPrivacyKit's Video Compressor uses a local browser processing path for supported inputs. The source video can stay on your device while the browser creates the smaller copy. There is no hidden “upload it anyway if local encoding fails” path; unsupported situations should fail clearly rather than silently changing the privacy model.
A simple Discord workflow
- Keep the original recording untouched.
- Open the local Video Compressor and load the clip.
- For a free Discord account, set a target below 20 MB rather than exactly on the cap.
- Preview the result around fast motion, text overlays and audio sync.
- Send the compressed sharing copy to Discord; archive the master separately.
What if the clip is still ugly at 20 MB?
That is not necessarily a compressor problem. A fixed 20 MB budget can be genuinely too small for a long, complex video at the quality you want. Trim the clip, lower resolution, or share it another way. Compression cannot create bitrate that the file-size limit does not allow.
Also remember that Discord may change its limits again. The useful part of this workflow is not memorizing “20 MB forever”; it is having a local target-size workflow that can adapt when the platform changes.
Make a Discord-sized copy without uploading the source
Choose a smaller target, compress in the browser, inspect the result, and keep the original master untouched.
Open Video Compressor →