DiscordTextTools
Back to Blog

Discord File Size Limit in 2026: Why You See 10MB, 25MB, or 500MB

By DiscordTextTools Editorial

You drag a clip into Discord, wait a second, and get hit with this:

Uh oh, this file exceeds the size limit. The max file size is 25MB. Upgrade to Discord Nitro to upload files up to 500MB.

It is one of the most annoying walls in Discord, partly because the number in that message is not the same for everybody. Some people see 10MB. Most now see 25MB with a BETA badge next to it. Nitro users see 500MB.

Here is what is actually going on, and what to do about it.

What is the Discord file size limit?

Account type Upload limit
Free (documented) 10 MB
Free (current rollout) 25 MB
Nitro Basic 50 MB
Nitro 500 MB

The confusing part is the first two rows, and they are both correct.

Discord's own File Attachments FAQ still states that "for non-Nitro subscribers, the maximum file upload is 10MB." But the same article opens with this note:

We're currently experimenting with various file upload size limits. Select users may have the ability to upload larger file sizes.

That is why the number in your client is tagged BETA. Discord has been rolling 25MB out to free accounts as an experiment rather than flipping it on globally and updating the docs. So the honest answer in 2026 is:

  • 10MB is the documented floor for free accounts.
  • 25MB is what most free accounts actually get right now.
  • Which one you have can change without warning, and can differ between your desktop and mobile clients.

If a 25MB upload gets rejected, you are on the 10MB tier. Aim lower and try again.

What happened to the old 8MB limit?

Discord's free limit used to be 8MB, which is why so many older guides and compression tools are built around that number. It is gone. If you find a tool that only offers "compress to 8MB," it is out of date — you are leaving roughly three times the headroom on the table.

Why the limit exists at all

Attachments are stored and served by Discord's CDN indefinitely, for free, to everyone in the channel. A 500MB upload in a busy server can be re-downloaded thousands of times. The cap is a bandwidth bill, not an arbitrary annoyance, and it is the single most effective lever Discord has for selling Nitro.

That also explains why the limit is per-file and per-message rather than per-account: it is about egress, not storage.

The four ways to get around it

1. Compress the file (free, keeps it in the channel)

For almost every real case — a gameplay clip, a screen recording, a meme GIF, a screenshot — compression just works. Modern video codecs are so much more efficient than what recording software outputs that you can usually cut 80–95% off a clip with no visible difference.

Recording tools like ShadowPlay, Medal, OBS and the Xbox Game Bar record at 30–70 Mbps because they are optimised for not dropping frames, not for file size. A 30-second clip at 50 Mbps is about 190MB. That same 30 seconds re-encoded at a sane bitrate is under 25MB and looks essentially identical.

You can do this in the browser with the Discord File Compressor — it targets your exact limit, runs entirely on your device, and never uploads anything.

2. Trim the clip

This is the option people skip, and it is often the right one. See the next section for why.

3. Upload elsewhere and paste a link

For anything long — a full match recording, a tutorial, a podcast — compression is the wrong tool. Put it on YouTube (unlisted), Google Drive, Streamable or Catbox and paste the link. Discord will unfurl a preview for most of these.

4. Pay for Nitro

50MB on Nitro Basic, 500MB on full Nitro. Worth it if you hit the limit daily; overkill if you hit it twice a month.

The thing nobody tells you: length matters, size does not

This is the single most useful thing to understand about compressing anything for Discord.

Your target is a fixed number of bits — 25MB is about 201 megabits. Those bits get spread evenly across every second of footage. So the quality you end up with depends on how long the clip is, not how big the original file was. Divide 201 megabits by the length of your clip in seconds and you have your bitrate budget.

Two examples that make the point:

  • A 300MB, 30-second clip → 25MB at full 1080p. Basically indistinguishable from the original.
  • A 300MB, 20-minute video → 25MB at roughly 240p. A blurry mess.

Same source file size. Wildly different outcomes. Here is roughly how long a clip can be before quality starts to suffer:

Output resolution Max length at 25MB Max length at 10MB
1080p ~36 seconds ~14 seconds
720p ~1m 15s ~30 seconds
480p ~2m 30s ~1 minute
360p ~4m 15s ~1m 40s
240p ~7m 30s ~3 minutes

(Assumes 30fps with stereo audio. 60fps roughly halves each figure.)

The practical takeaway: if your clip is longer than the row you want, trim it before you compress it. A sharp 40-second highlight is a better post than a blurry four-minute upload, every single time. Cutting 30 seconds of dead air at the start is worth more than any encoder setting.

Which formats compress well, and which do not

Compresses brilliantly:

  • Animated GIFs. GIF stores every frame almost independently with a 256-colour palette — it is a terrible video format. Converting a GIF to MP4 routinely cuts 90%+ off the size, and Discord autoplays and loops MP4 exactly like a GIF. If you have a 40MB GIF, this is a free win.
  • Screen recordings and gameplay clips. Huge bitrate, lots of redundancy between frames. Easy 90% reduction.
  • PNG screenshots. PNG is lossless. A 30MB screenshot becomes a 1MB WebP or JPEG that looks the same.
  • WAV and FLAC audio. Uncompressed or lossless audio converted to AAC or Opus is a 5–10x reduction with no audible difference at sensible bitrates.

Barely compresses at all:

  • ZIP, RAR and 7z archives. Already compressed. Re-compressing gains nothing — split them into parts instead.
  • Already-optimised MP4s. If a video is already at a low bitrate, there is little left to squeeze without visibly hurting it.
  • Small JPEGs. Re-encoding a JPEG that is already lossy just adds artifacts.

Cannot be handled in a browser:

  • AVI, WMV, FLV. Browsers cannot open these containers at all. Convert to MP4 on the desktop first.
  • HEIC and RAW photos. Not decodable in most browsers. Export to PNG or JPG first.
  • PDFs. They can technically be shrunk, but not safely in a browser — the usual trick is rasterising every page, which destroys selectable text and often makes the file bigger. Zip it or link it instead.

Common questions

Why does my 24MB file still get rejected?

Discord measures in mebibytes (1 MB = 1,048,576 bytes), and some clients count a little message overhead too. Leaving a small buffer — targeting about 24MB for a 25MB cap — avoids this entirely. Any decent compressor should already do that for you.

Does compressing remove the audio?

It should not. A good compressor reserves a slice of the budget for audio (usually 64–128 kbps) and spends the rest on video. If your audio disappeared, the tool either could not handle the source codec or dropped the track on purpose — check the output before you post it.

Can I send multiple files to get around the limit?

The limit is per file, not per message, so ten 20MB files in one message is fine. Splitting a single video into parts works too, but it makes for an awkward viewing experience. Trim instead.

Does the limit apply to profile pictures and emojis?

No, those have their own separate limits, which are much smaller. Server emoji are capped at 256KB, and avatars have their own constraints — see the avatar preview tool if you are working on a profile.

The short version

The Discord file size limit is 10MB on paper, 25MB in practice for most free accounts, 50MB on Nitro Basic and 500MB on Nitro — and the free number is still being A/B tested, so it can move.

For anything under a couple of minutes, compressing is free and near-lossless. For anything longer, trim it or host it elsewhere. If you want to do the compression without uploading your files to a stranger's server, the Discord File Compressor does it entirely inside your browser and shows you the predicted quality before it starts.

Hitting a different Discord limit? The 2000-character message cap has its own set of workarounds.