Discordファイル共有 / 2026年5月12日

Discord File Size Limit: 10MB Free, 500MB Nitro — and the Workaround

Discord's file size limit is 10MB on free, 50MB on Nitro Basic, 500MB on full Nitro. Here's what the cap actually means and how to send larger files anyway.

You hit "Send" on a video, Discord shows a red bar, and you get told the file's too big. Annoying. Discord's file size cap has changed twice in two years, and the current numbers aren't obvious unless you go hunting in support docs.

Here's the actual cap, why it's that low, and what to do when you need to share something bigger.

The current Discord file size limits

As of 2026, the per-upload caps are:

  • Free tier: 10MB per file (lowered from 25MB in 2024)
  • Nitro Basic ($2.99/month): 50MB per file
  • Nitro ($9.99/month): 500MB per file

The cap is per-file, not per-message. You can't stack two 5MB attachments to make a "10MB allowance." Each file is independently checked.

Server boosts don't change file size caps for members — they used to, and they no longer do. The caps are tied to your personal Discord account tier, not the server you're in.

If your file is failing at the "too large" step specifically, the Discord file too large error breakdown covers the exact error states and where they come from.

Why Discord lowered the limit

In 2024 Discord cut the free upload cap from 25MB to 10MB. The reasoning, per their own announcements, was infrastructure cost — they were eating a lot of media bandwidth for non-paying users.

The change was unpopular. There's still an active feature request on Discord Support asking for it to be reverted. It hasn't been.

For everyday casual chat — screenshots, short clips, voice messages — 10MB is enough. For anything that wasn't built to fit in 10MB (a phone-recorded video, a class slide deck, a build artifact), it isn't.

How to send something bigger — without paying

1. Compress it

This is the only "free" fix that doesn't involve external storage.

  • Videos: HandBrake or ffmpeg can drop a 50MB clip to ~8MB if quality isn't critical.
  • Images: switch PNG to WebP/JPEG, resize to the actual display dimensions.
  • PDFs: PDF compressors strip embedded image bloat.

Compression destroys quality. For viewing-only content that's fine. For source files, masters, or anything someone will edit later, it isn't.

2. Use a file host

Imgur for images, Streamable for videos, Google Drive for everything else. Paste the link in Discord instead of the file.

The downside is access control: a Google Drive "anyone with the link" share is functionally public the moment one person reposts it. A Streamable link is fully public.

3. Use a Discord-aware sharing service

If the file needs to be visible to your server members and not the open internet, public file hosts don't fit. The pattern that works:

  • Auth via Discord OAuth.
  • Storage in object store (R2/S3) with no upload cap of its own.
  • Per-server access control, so members of your server see the file, others don't.

DisCoRibute is built around exactly this. Uploaded files live in private R2 buckets; only authenticated server members get signed-URL access; there's no per-file size cap from Discord at all because the file never touches Discord's servers.

What about Nitro?

If you're the only person in your server who regularly hits the cap, Nitro at $9.99/month is a clean fix. 500MB per file covers almost any practical upload.

If you're a server admin trying to make file sharing work for your whole community, Nitro doesn't scale — you can't require every member to subscribe. The Nitro vs alternatives breakdown goes deeper on when paying is worth it.

Special case: long videos

Long videos are their own headache. Even after compression, a 30-minute screen recording is going to land somewhere between "definitely over the cap" and "destroyed by compression." Sending long videos on Discord covers the video-specific tradeoffs.

What I'd actually do today

For a one-off file that nobody else needs to keep: compress, drop it in Discord.

For a recurring drop in a community server (lesson recordings, build artifacts, weekly assets): Discord OAuth + R2 setup. The cap stops being a daily annoyance the moment Discord isn't in the upload path.

The most expensive option is the one where every single member learns to compress their own files. That works for two weeks and then someone gives up and stops sharing.