Your video is too large for Discord because its camera or screen recorder chose a bitrate, not a sharing destination. A phone may record 4K at 40–100 Mbps; Discord's free account limit is 20 MB per file. At 60 Mbps, the camera creates 20 MB in about 2.7 seconds. Nothing is broken—the source was made for editing and local storage, while the upload cap was made for quick delivery.
The fix is to compress for the limit you actually have: target 19 MB for a free account, 48 MB for Nitro Basic's 50 MB cap, or about 490 MB for Nitro's 500 MB cap. The margin matters because a target-size encoder can land slightly above the number requested.
First, check which Discord limit applies
Discord's current per-file limits are:
| Account | Limit | Safe target |
|---|---|---|
| Free | 20 MB | 19 MB |
| Nitro Basic | 50 MB | 48 MB |
| Nitro | 500 MB | 490 MB |
The limit follows the uploader's account. Posting inside a boosted server does not give a free account Nitro's file allowance. Older search results often say 8 MB, 10 MB or 25 MB because all three were real free-tier limits at different times. The dated history and sources are on the Discord video compressor page.
Why a short phone clip can be hundreds of megabytes
File size is mostly this multiplication:
bitrate × duration = data
Resolution and frame rate matter because they push the recorder toward a higher bitrate. They do not directly set the file size. Two one-minute 1080p clips can be 20 MB and 300 MB if one was exported for messaging and the other was recorded as a high-quality master.
Consider a one-minute clip:
- At 50 Mbps, it is about 375 MB.
- At 10 Mbps, it is about 75 MB.
- At 2.5 Mbps, it is about 19 MB after leaving room for audio and the MP4 container.
That last bitrate is a reasonable 720p delivery budget for ordinary camera footage. Trying to keep the same minute at 4K does not preserve quality; it spreads too few bits across too many pixels and produces a large frame full of blocks and smearing.
Use the video compression calculator if you want to see the bitrate implied by your exact duration before uploading.
The fastest reliable fix
- Trim dead time. Ten seconds removed from a 60-second clip gives every remaining second 20% more of the fixed budget.
- Choose an exact target of 19 MB. A percentage slider cannot know Discord's ceiling; a final-size target can.
- Use H.264 MP4. It is not the smallest possible codec, but it is the safest choice when you do not control the recipient's device.
- Let resolution fall when the clip is long. Under roughly 30 seconds, 1080p is realistic. Around a minute, 720p is safer. At several minutes, 480p or a link may be the honest answer.
- Check the result before posting. Watch motion, faces, small text and dark gradients—not only the first still frame.
You can do those steps directly with the Discord preset, which starts below the cap instead of aiming at its edge.
Why Discord says “file too large” even when it looks under 20 MB
There are four common explanations.
The app is checking the original phone file
Discord changed mobile behavior so the size is checked before the app performs its own compression, matching desktop. A clip that once slipped through after mobile compression can now be rejected immediately. Compressing before you pick the file solves that mismatch.
Your client still behaves like the older 10 MB limit
Discord raised the free cap to 20 MB in August 2026, but documentation and client rollouts do not always move together. If a 19 MB file is refused and the account is definitely free rather than restricted by another policy, try a 9.5 MB output once. That is a diagnostic fallback, not the current published target.
You checked the wrong file
Phone galleries often show a preview, edited copy or cloud placeholder while the share sheet sends the original. Confirm the size of the exact file selected for upload. On desktop, check the exported file rather than the editing project or source clip.
The file has a playback problem, not a size problem
An unusual codec can fail after upload or appear unplayable even when its bytes fit. H.265, AV1, variable frame-rate captures and uncommon audio tracks are more likely to expose client differences. H.264 video with AAC audio in MP4 is the boring format—and boring is useful when the audience is unknown.
What quality fits inside 20 MB?
A 19 MB target leaves approximately these video budgets after 128 kbps audio and container overhead:
| Duration | Approximate video bitrate | Practical starting point |
|---|---|---|
| 30 seconds | 5.1 Mbps | 1080p |
| 1 minute | 2.5 Mbps | 720p |
| 2 minutes | 1.2 Mbps | 480p–720p, depending on motion |
| 5 minutes | 0.4 Mbps | 360p or a cloud link |
Screen recordings can do much better because most pixels remain unchanged from frame to frame. Handheld camera footage, foliage, games with particles and film grain are harder. This is why a promise such as “20 MB equals two minutes of 1080p” cannot be universally true.
For the full limit history, evidence and longer duration table, read Discord File Size Limit: 20 MB Free, 500 MB Nitro.
FAQ
Can I send a video larger than 20 MB without Nitro?
Yes, by compressing it below 20 MB or sharing a cloud link. Discord will not accept a larger direct attachment from a free account merely because the server is boosted.
Why is a ten-second video 100 MB?
It was probably recorded at a high bitrate, often 4K, high frame rate, HDR or a quality-first camera mode. Ten seconds at 80 Mbps is about 100 MB.
Should I ZIP the video?
Usually no. H.264 and H.265 video is already compressed; ZIP often saves almost nothing, and the archive still has to fit the same upload cap.
Is lowering resolution better than lowering quality?
Once bitrate per pixel becomes too low, yes. A healthy 720p encode generally looks better than starved 1080p at the same 19 MB final size.
Does Discord compress the uploaded video?
Do not rely on it to make an oversized file fit. Prepare the delivery file before upload so the bytes Discord checks are already below your account's limit.