To compress a video for Discord, get it under the free tier’s 10 MB per-file limit: trim the clip to the moment that matters, drop the resolution to 720p, and re-encode with H.264 — either at a bitrate you calculate from the clip length (size in MB × 8 ÷ seconds = total Mbps budget) or with CRF 26–30.
That workflow gets almost any short clip under the limit with watchable quality. The rest of this guide is the numbers behind it, plus the fastest tooling for each situation — including free in-browser converters that compress the file without uploading it anywhere.
What Are Discord’s Upload Limits?
As of July 2026, Discord’s per-file upload caps are:
| Plan | Price | Max file size |
|---|---|---|
| Free | $0 | 10 MB |
| Nitro Basic | $2.99/mo | 50 MB |
| Nitro | $9.99/mo | 500 MB |
The free limit dropped from 25 MB to 10 MB in 2024, which is why so many older “under 25 MB” guides now produce files Discord rejects. The caps are per file and tied to your account, and Discord doesn’t compress video for you — an oversized clip is simply refused. Pasted links embed regardless of size, though, which is the escape hatch for anything long: a video URL from a host plays inline no matter what tier you’re on. Current limits are documented in Discord’s own File Attachments FAQ.
The Bitrate Math: What Fits in 10 MB?
File size is just bitrate × duration, so 10 MB is a fixed budget you spend across the clip’s length: 10 MB × 8 = 80 megabits, divided by the clip’s seconds, minus ~0.1 Mbps for audio. In practice:
| Clip length | Total bitrate budget | Realistic quality at that budget |
|---|---|---|
| 15 s | ~5.3 Mbps | 1080p30 looks genuinely good |
| 30 s | ~2.6 Mbps | Solid 720p30 |
| 60 s | ~1.3 Mbps | Watchable 720p, visible artifacts in motion |
| 2 min | ~0.65 Mbps | 480p territory — trim instead |
| 5 min | ~0.26 Mbps | Not viable — link it instead of uploading |
Read the table bottom-up and the first rule of Discord compression falls out: trimming is worth more than any encoder setting. Cutting a 60-second clip to the 20 seconds people actually need quadruples the bitrate every remaining second gets. Past the two-minute mark, stop compressing and upload to a host built for it, then paste the link.
The Three-Step Workflow
- Trim first. Cut to the moment. Every second you delete is bitrate handed to the seconds you keep.
- Drop the resolution. Discord’s inline player is small — 720p is indistinguishable from 1080p in an embed, and it halves the pixels the encoder has to feed. For clips over a minute, 480p is a legitimate choice.
- Re-encode as H.264 MP4. H.264 embeds and autoplays across Discord on every platform. Set the bitrate from the table above, or use CRF and let the encoder pick (next section).
One lever people forget: audio. A screen recording carrying 320 kbps stereo audio spends 2.4 MB of a 10 MB budget per minute on sound. Re-encode audio at 96 kbps AAC for gameplay and voice clips — nobody can tell in a Discord embed — or strip the track entirely (-an in FFmpeg) for silent clips, and hand every reclaimed bit to the video.
Avoid the Problem: Record Smaller
If your clips routinely start life at 300 MB, the cheapest compression happens before the recording exists. In OBS or any game-capture tool, record clips-for-chat at 720p30 with a bitrate around 4–6 Mbps instead of archiving-quality settings — a 20-second clip lands near 12 MB before you’ve touched an encoder, and one light CRF pass finishes the job. Keep a separate high-quality profile for footage you’ll actually edit; the mistake is using the archival profile for everything.
Compressing with FFmpeg CRF
If you’re comfortable with a terminal, CRF (constant rate factor) mode is the quality-first way to compress — you pick a quality level and FFmpeg spends whatever bitrate that requires:
ffmpeg -i input.mp4 -vf scale=1280:-2 -c:v libx264 -crf 28 -preset slow -c:a aac -b:a 96k output.mp4CRF 23 is near-transparent, 26–28 is the Discord sweet spot, and 30+ shows blocking in motion. The loop is simple: encode at CRF 26, check the size, and step the CRF up by 2 until the file slips under 10 MB — each +6 roughly halves the bitrate, so a +2 step cuts around 20% without an obvious quality cliff. If even CRF 30 at 720p won’t fit, the clip is too long: go back to step one and trim.
The In-Browser Route (No Upload, No Watermark)
Not every clip starts life as an MP4 — and format conversion and compression can be one step. The free converters at /tools run entirely in your browser via ffmpeg.wasm: the file never leaves your device, there’s no watermark, and every video converter includes trim, resize, and quality controls — exactly the three levers above.
- iPhone clips (MOV): the MOV to MP4 converter re-encodes HEVC footage as H.264, which also fixes the “iPhone video won’t play inline in Discord” problem in the same pass.
- OBS recordings (MKV): the MKV to MP4 converter turns crash-safe recordings into small, shareable MP4s — drop the quality slider to 70 and gameplay clips shrink dramatically.
- Giant GIFs: the GIF to MP4 converter routinely cuts 90%+ of the file size, since H.264 stores frame differences instead of full frames.
For an MP4 that’s already an MP4 and just too big, FFmpeg (above) or any desktop encoder with a CRF setting does the re-encode; the general-purpose treatment of the topic — codecs, resolution, and when each lever matters — is in How to Reduce Video File Size.
FAQ
What is Discord’s file size limit right now?
10 MB per file on the free tier, 50 MB with Nitro Basic, and 500 MB with Nitro, as of July 2026. Oversized files are rejected outright — Discord doesn’t compress video on upload.
What’s the fastest way to get a video under 10 MB?
Trim to under 30 seconds, resize to 720p, and re-encode as H.264 MP4 at CRF 26–28 (or quality ~70 in a slider-based tool). That combination fits the 10 MB budget for the overwhelming majority of gameplay and screen-recorded clips.
Why won’t my iPhone video play inline on Discord?
Recent iPhones record HEVC (H.265) in a MOV container, which some Discord clients won’t decode inline. Converting to H.264 MP4 fixes playback everywhere and usually shrinks the file at the same time.
Does compressing for Discord ruin the quality?
Under 30 seconds, barely — 2.6 Mbps at 720p30 looks clean in Discord’s small embed player. Quality falls apart when people try to squeeze multi-minute videos under the cap; past two minutes, upload elsewhere and share the link.
Are in-browser compressors safe for private clips?
Client-side ones are — the conversion runs in your browser’s own memory via WebAssembly, so the file is never uploaded to a server. Check for an explicit “files never leave your device” statement; tools that show an upload progress bar are sending your clip somewhere.
