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

Have you ever encountered one of the following errors when dragging and dropping a file into Discord?

• "Your files are too powerful"
• 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. We'll explain which limit you've reached and how to resolve 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.

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 a Discord-Native Sharing Workflow

This approach is ideal when:

• Managing a community server: A server admin needs to share files repeatedly with members.

• Prioritizing privacy: The shared content must remain strictly limited to server members.

• Requiring permanent links: The files must not expire (unlike Discord CDN links, which disappear after 24 hours).

The standard pattern involves a sharing service that authenticates users via Discord OAuth, verifies their server membership, and delivers files from R2 or S3 using secure, temporary links.

DisCoRibute serves as a prime example of this workflow. A file is uploaded just once, and active server members instantly get access while everyone else is kept out. Best of all, because the files never pass through Discord's infrastructure, the standard file size caps no longer apply.

Conclusion: Solve the Cap Once and For All

The "file too large" error is a simple sign that Discord isn't meant to be a heavy cloud storage system. When dealing with this limit, the best approach depends on your long-term needs:

• For one-off files: Compressing files or playing within the free limits works perfectly fine for occasional sharing.

• For recurring files: If you are constantly struggling with the cap every week for community assets or team files, moving the upload path outside of Discord entirely is the only sustainable way to scale.

Ultimately, the choice comes down to whether you want to fight the file size limit every single time, or set up the right infrastructure to solve it once and for all.