Guide
Discord’s video size limit, explained
Updated 2026-08-28 · 8 min read
If Discord refuses a clip, it is almost always the file size, not the format. This guide covers the real caps, why a phone recording blows past them, and how to shrink a video without a watermark or an upload to a random website.
What is Discord’s upload limit in 2026?
A standard Discord account can attach a file up to 25 MB. Discord Nitro raises that to 500 MB. Server Boost does not magically give every member the Nitro cap — only the person uploading with Nitro (or a boosted tier that your community actually has) gets the higher ceiling. If you are not sure which you have, assume 25 MB. That is the number most group chats still live with.
Length limits also exist (clips that are extremely long can fail even when they are under 25 MB), but size is the rejection you will see every day. Discord is not being picky about “quality.” It is protecting bandwidth. A two-minute 4K screen recording from a phone is often 150–400 MB. The client will not send it.
Why a 30-second clip is still 200 MB
Phones and game capture tools record high bitrates on purpose: lots of bits per second so fast motion stays sharp. File size is roughly bitrate × duration. Double the minutes, double the megabytes. 4K has four times the pixels of 1080p, so it eats the 25 MB budget in seconds.
That is why “just convert it to MP4” often fails. The file is already MP4. You have to throw bits away — that is compression. The useful question is not “is it MP4?” It is “how many kilobits per second can I spend and still land under 25 MB?”
How to pick a bitrate that fits 25 MB
A practical rule: leave a little headroom for audio and the MP4 container. For a 25 MB target, plan on about 23–24 MB of actual media. Divide that budget by the length of the clip (in seconds), and you get bits per second. A 60-second clip at 25 MB is roughly 3 Mbps of total bitrate. Subtract ~128 kbps for stereo AAC audio and the rest is video.
If the clip is three minutes, that same 25 MB budget is about 1 Mbps. At 1080p, 1 Mbps looks muddy. Dropping to 720p or 480p gives those bits fewer pixels to cover, so faces and UI stay readable. This is why “keep it 1080p no matter what” is bad advice for Discord.
A sane workflow that actually sends
Trim first. If the joke is in the last twelve seconds, do not encode the whole take. Then pick Discord (25MB) or Discord Nitro (500MB). Leave resolution on Auto unless you know you need 1080p and the clip is short. Strip audio only if the clip is silent B-roll — voice and game sound are usually the point.
Two-pass encoding (what Shrink Clip does in your browser) spends extra time measuring the clip, then puts more bits on the hard scenes. One-pass “fast” compressors often overshoot 25 MB or starve the action. Nothing is uploaded: the encoder runs in this tab. When it finishes, download the MP4 and attach it in Discord. If Discord still complains, you are a hair over — drop to 720p or trim two seconds.
Nitro, mobile data, and quality expectations
Nitro’s 500 MB cap is generous. You can keep 1080p on a five-minute clip and still look good. Do not use 500 MB as a default if the people you send to are on phones — they will thank you for a 25 MB file that plays immediately.
No compressor invents detail. If the original is a dark, shaky 480p stream, 25 MB will not make it cinematic. Compression only spends the budget you have. Short, well-lit clips at 25 MB look surprisingly close to the original. Long, busy 4K clips will look like a 480p YouTube video from 2014. That is physics, not a broken tool.
Ready to try it? Compress a video in your browser— nothing is uploaded.