Discord 'File Too Large' Error: What It Means and How to Fix It

You drag a file into Discord and get hit with one of these:

• "Your files are too powerful"
• "File too large"
• A red attachment box that won't send
• A silent fail where the upload progress just stops

It's the same problem in different costumes. Discord has a hard per-file upload cap, and your file is over it. Here's how to figure out which cap you hit and what to do about it.

What "file too large" actually means

Discord's caps as of 2026:

• Free: 10MB per file
• Nitro Basic: 50MB
• Nitro: 500MB

The cap isn't about your total storage. It's about a single upload. You can send a hundred 9MB files in a row on the free tier — you just can't send one 11MB file.

If you're confused about which tier you're on, check your Discord profile. The error is the same for all three; only the threshold changes.

A full breakdown of the Discord file size limit lists what each tier covers in practice.

Mobile is a special case

On iOS and Android, the error often shows up as "the file couldn't be uploaded" without specifying size. That's still a size error 90% of the time — the mobile clients are slightly worse at surfacing the real reason.

If a file uploads from your desktop but not from your phone, it's almost always size: phones tend to record at higher bitrates than people expect, and a 30-second 4K clip can land at 80MB easily.

Fix 1: Compress the file

Fastest answer. Works when the file is "almost" small enough.

• Video: re-encode at a lower bitrate. ffmpeg one-liner: ffmpeg -i input.mp4 -crf 28 output.mp4. CRF 23–28 is the usable range; higher = more compression = worse quality.
• Image: convert PNG to JPEG or WebP. For screenshots, resize to the display resolution you actually need.
• PDF: most PDF compressors handle this in one click.

If compression makes the file unviewable (small text in a screen recording becomes mush, color grading gets crushed), don't ship it. Skip to fix 2 or 3.

Fix 2: Upload to a host and paste a link

Public hosting works when the content is shareable with the open internet.

• Streamable: handles up to ~10GB on the free tier, plays inline in Discord.
• Google Drive / OneDrive: 15GB free; share link, paste in Discord.
• Imgur / Catbox: images and short clips.

These all work. They all share one weakness: there's no relationship between "who's in your Discord server" and "who can open the link." If the file is sensitive, this is the wrong layer.

Fix 3: Use Discord-native member-only storage

This is the right shape when:

• You're a community admin sharing files repeatedly with your server.
• The content needs to be private to your server members.
• You want links that don't expire (Discord CDN links die in 24 hours — see the link expiration breakdown).

The pattern: a sharing service authenticates users via Discord OAuth, checks they're in your server, and serves files from R2/S3 with signed URLs. DisCoRibute is the cleanest example I've seen of this. You upload once, your server members get access, nobody outside the server does, and the file size cap that triggered the original error stops applying because the file never goes through Discord.

When the error keeps coming back

If you keep hitting "file too large" on the same kind of file (screen recordings, design files, build artifacts), stop treating it as a one-off and set up a permanent destination. Compressing every week burns time. Pasting Drive links works until one leaks. A Discord-aware destination solves the upload-flow problem at the source.

The decision isn't "free vs. paid" — it's "do I want to fight the cap every time, or solve it once."

What this error is telling you

The "file too large" message is annoying, but it's an honest signal: you're using Discord as a file delivery system, and Discord doesn't want to be one. Either play within the cap (compress, send less), pay to extend the cap (Nitro), or move the file step out of Discord entirely. The first two are tactical. The third is what scales.