DiscordTextToolsDiscord Raised the Free Upload Limit to 20MB — So Why Do You Still Hit It?
In August 2026 Discord quietly did two things to file uploads at once. It raised the free limit from 10MB to 20MB — good news everyone noticed — and it changed how that limit is measured — a detail almost nobody noticed, but the one that explains why some people are hitting the wall more often than they used to.
If the number went up, why are your uploads failing more? This is the part the headline number hides.
What actually changed
Discord's File Attachments FAQ now documents a 20MB limit for non-Nitro accounts, up from the long-standing 10MB. It also carries a note at the very top:
We're currently experimenting with various file upload size limits. Select users may have the ability to upload larger file sizes.
So there are really two moving parts:
- The baseline went up to 20MB for free accounts.
- The check moved to before compression instead of after, and mobile was aligned with desktop so the number you see is the number that actually applies.
That second point is the interesting one, and it is worth unpacking.
Pre-compression vs post-compression: the hidden variable
Here is the mechanism. When you attach a file, Discord can measure its size at one of two moments:
- After compression — Discord shrinks the file first, then checks whether the result fits. This is more forgiving: a 28MB phone video that compresses down to 18MB would sneak through.
- Before compression — Discord checks the raw file you selected. If the original is over the limit, it is rejected outright, regardless of how small it might have become.
Historically, desktop checked before compression while mobile checked after. That inconsistency meant the "limit" you saw on your phone did not always match what actually applied. In 2026 Discord moved mobile onto the same pre-compression check desktop already used, so the stated number is now consistent across platforms.
Consistent, but not always more generous. The effect splits by platform:
| Platform | Typical effect of the change |
|---|---|
| Desktop | Roughly the same as before, now clearly 20MB |
| iOS | Generally easier — source files are already fairly compact |
| Android | Can be harder — camera files are large and now measured raw |
On Android, phone cameras and screen recorders produce big source files, and now those raw sizes are what count. A clip that used to slip under the old post-compression check can be rejected under the new pre-compression one, even though the stated limit went up. That is the whole paradox: a higher number that occasionally feels lower.
Why experiment instead of just picking a number?
Discord could set one limit and ship it to everyone at once. It does not, and the reason is worth understanding because it directly explains the inconsistency you are seeing. Every megabyte of free headroom is a recurring cost — attachments are served from Discord's CDN long after they are posted — so raising the limit is not a switch they flip lightly. (The full economics of why the cap exists at all is covered in the file size limit guide; this article is about the change itself.)
A/B testing lets Discord weigh that cost against the friction a tight limit creates, on real traffic, before committing globally. That is precisely why two accounts can see different numbers, why your laptop and your phone can disagree, and why 25MB shows up as BETA for some users and not others. The practical consequence: treat whatever limit you have today as current for your account, not permanent or universal.
What this means for you in practice
The upshot is simple, even if the mechanism is not:
- Aim for the raw file to fit, not the compressed result. Because the check is now pre-compression, the file you select has to be under your limit. Do the compression yourself first.
- Leave a small buffer. Discord counts in mebibytes (1MB = 1,048,576 bytes) and adds a little message overhead, so target ~19MB for a 20MB cap rather than exactly 20.
- Do not trust one platform's result on another. A file that uploaded fine from your laptop can still be rejected on Android, and vice-versa.
- Test your own limit. If a 20MB file is rejected, you may be on an older 10MB rollout. If a 24MB file goes through, you have the 25MB experiment. When in doubt, compress to a size you know works.
The reliable move is to compress before you upload, targeting the exact size your account accepts. The Discord File Compressor now lets you pick 20MB, 25MB, 10MB, or type an exact custom size — everything runs in your browser, so your file is never uploaded to a third-party server just to be shrunk. It also shows you the predicted quality before it encodes, so you are not guessing.
Length still decides quality more than anything
One thing the limit change does not alter: the quality you get out of compression depends on how long your clip is, not how big the source was. A 20MB budget is a fixed pool of bits — about 168 megabits — spread across every second of footage. A 30-second clip fits in 20MB at full 1080p and looks essentially untouched; a 10-minute recording squeezed into the same 20MB collapses to a soft 360p.
So if a clip is too long for the resolution you want, trim it before compressing. A crisp 40-second highlight beats a blurry four-minute upload every time. The full resolution-versus-length breakdown lives in the Discord file size limit guide, and the step-by-step settings per file type are in how to compress a video for Discord.
Frequently asked questions
Is the Discord free upload limit 20MB now?
Yes. As of 2026 Discord's FAQ documents 20MB for non-Nitro accounts, up from 10MB. Some accounts also get 25MB as an ongoing experiment, and a few may still be on the older 10MB tier.
Why did my upload fail if the limit went up to 20MB?
Most likely because Discord now checks your file size before compression. If the raw file you selected is over 20MB, it is rejected even if it would have compressed down to fit. This hits Android users hardest because their camera and screen-recording files are large. Compress the file yourself first so the original is already under the limit.
Does the pre-compression check affect desktop too?
Desktop has always used the pre-compression check, so nothing changed there — it just became consistent with mobile. The practical difference is felt mainly on Android, where files were previously measured after Discord's own compression.
How do I get a file under 20MB without Nitro?
Compress it. For gameplay clips, screen recordings, GIFs and screenshots, re-encoding cuts 80–95% off the size with no visible loss. The Discord File Compressor targets your exact limit in the browser without uploading anything.
Will Discord raise the limit again?
Possibly. The FAQ explicitly says it is experimenting with various upload sizes, so the free limit can move again and can differ between accounts. If you build a workflow around a specific number, expect to revisit it.
The short version
Discord raised the free upload limit to 20MB in 2026 and is testing 25MB for some users — but it also moved to checking file size before compression, which is why Android uploads can fail more often despite the higher number. The fix is unchanged: compress before you upload, leave a small buffer, and trim long clips first. Do it in your browser with the Discord File Compressor, and if you also keep bumping into the 2000-character message limit, that has its own set of workarounds.