The Discord upload cap changed in April 2024, and every "how to compress video for Discord 8mb" tutorial written before then is technically wrong. The free-tier limit went from 8 MB to 25 MB - a 3x jump that changes what a normal screen recording can look like at Discord-ready quality. The tier ladder is worth memorising because the compression targets are wildly different at each rung.
#The current limits (as of April 2024)
- Free tier: 25 MB per file. Applies everywhere unless a server-boost or Nitro tier raises it.
- Server boost Level 2 (7 boosts): 50 MB per file for members of that server. Doesn't apply to your DMs.
- Server boost Level 3 (14 boosts): 100 MB per file for members of that server. Doesn't apply to DMs.
- Nitro Basic ($2.99/mo): 50 MB per file for you, everywhere.
- Nitro Full ($9.99/mo): 500 MB per file for you, everywhere.
The single most-searched limit is still "8mb" because that was the free-tier cap for years and the muscle memory hasn't updated. If a tutorial or Discord bot references 8 MB, it's pre-April-2024. Nothing on Discord in 2026 caps at 8 MB.
#What a 25 MB video actually looks like
The recipe is: total file size ≈ (video bitrate + audio bitrate) × duration ÷ 8. For a 25 MB target with 128 kbps AAC audio, the video bitrate budget lands at roughly:
- 30-second clip: ~6.5 Mbps - fine for 1080p H.264 (comparable to Instagram Reels quality).
- 60-second clip: ~3.2 Mbps - fine for 720p H.264, marginal for 1080p (visible compression on motion).
- 2-minute clip: ~1.5 Mbps - 720p at low motion, or 480p at any motion.
- 5-minute clip: ~500 kbps - marginal at any resolution; suitable for talking-head content or slow screen recordings.
- 10-minute clip: ~250 kbps - only viable for slideshows or heavily-static content.
The practical takeaway: 25 MB is comfortable for a 30-60 second 1080p clip, workable for a 2-minute 720p clip, and starts falling apart above 3 minutes. Long clips that need Discord-shareable quality are a Nitro-tier problem or a link-to-external-host problem, not a compression problem.
#What a 50 MB video looks like (Nitro Basic or boosted server)
Same math, doubled budget. A 60-second 1080p clip at 50 MB has ~6.5 Mbps to work with - broadly indistinguishable from source quality on typical content. A 5-minute clip at 50 MB has ~1.3 Mbps - fine for 720p, thin for 1080p. The 50 MB tier is where casual screen recordings and gameplay clips stop looking degraded.
#What a 500 MB video looks like (Nitro Full)
Effectively unconstrained for anything up to 5-10 minutes. A 10-minute 1080p60 clip at 500 MB has ~6.5 Mbps to work with - equivalent to YouTube 1080p60 quality. The only case where 500 MB matters is when you're sharing raw camera or screen-recording footage without a compression pass, which iPhone HEVC recordings at 4K60 will hit inside 3-4 minutes.
#Bitrate targets by tier and length
If you're compressing manually (with HandBrake, ffmpeg, or a re-encode inside your recording tool), these are the practical starting bitrates:
Video bitrate for a given size × length (H.264, AAC 128 kbps)
| Length | 25 MB (free) | 50 MB (Nitro Basic) | 500 MB (Nitro Full) |
|---|---|---|---|
| 30 s | 6.5 Mbps | 13 Mbps | 130 Mbps (source-limited) |
| 1 min | 3.2 Mbps | 6.5 Mbps | 65 Mbps (source-limited) |
| 2 min | 1.5 Mbps | 3.2 Mbps | 32 Mbps |
| 5 min | 500 kbps | 1.3 Mbps | 13 Mbps |
| 10 min | 250 kbps | 650 kbps | 6.5 Mbps |
#What to do when the clip is longer than the tier can hold
- Trim first, compress second. Most screen recordings have 30 seconds of setup dead-air at the head and 30 seconds of tail. Trimming those saves you the compression pain.
- Split into multiple messages. Discord doesn't care if a 6-minute clip is three separate 2-minute uploads. Viewers slightly do, but it's the difference between watchable and unwatchable at low bitrates.
- Upload to a temporary host and drop the link. Litterbox (72-hour retention), catbox.moe (permanent), or a personal Google Drive share. Discord auto-embeds recent Google Drive video links inline, and it looks the same as a native upload for the viewer.
- Nitro Basic pays for itself at $2.99/mo if you're hitting the 25 MB limit more than a few times a month. The jump to 50 MB is significant for casual sharing.
#Why not just upload the source file?
Because iPhone screen recordings, phone camera clips, and OBS recordings are wildly bigger than Discord accepts. An iPhone 15 recording 4K60 HEVC hits about 400 MB per minute - a 30-second recording is already over the 25 MB free-tier cap. An OBS 1080p60 recording at reasonable bitrates hits about 100 MB per minute. Even a two-minute clip needs compression before Discord will accept it.
#Container and codec matter, not just size
Discord's embedded player is picky. MOV files (iPhone screen recordings, Mac screen recordings) sometimes fail to display an inline thumbnail even after they upload, forcing viewers into a download-and-open workflow that most abandon. WebM files from browser MediaRecorder work in Discord's web client but sometimes fail in the mobile apps. MKV files upload but never preview inline. The reliable target is MP4 with H.264 video and AAC audio - Wave's default output.
If your recording is a .mov (iPhone or Mac screen recording), convert it to MP4 first with Wave's iPhone screen recording page or Mac screen recording page. That's a container swap, not a compression - the file size stays the same. Then decide whether the resulting MP4 fits in Discord's cap, or whether it needs compression.
#The takeaway
Discord's free tier holds 25 MB - enough for a 30-60 second 1080p clip at watchable quality. 50 MB (Nitro Basic or a boosted server) holds a 2-minute 1080p clip comfortably. 500 MB (Nitro Full) is effectively unconstrained for casual clips. Match the target bitrate to the length using the table above. And if the source is .mov from iPhone or Mac, convert the container first before you decide about compression - the .mov to MP4 step alone doesn't save any bytes, but a lot of Discord upload failures are container issues masquerading as size issues.