Sending video on Discord: the 10MB cap and inline playback
Discord’s 10 MB is the harshest cap among mainstream platforms, yet it is the home turf of gaming communities and project collaboration. Fitting under 10 MB has a clear parameter path; inline playback has a clear encoding precondition.
The hard cap and content shape
Free accounts allow 10 MB per file; Nitro relaxes it to 500 MB. The cap dictates content shape: short clips (highlight plays, meme videos, feature demos) are Discord’s native format — a 30-to-60-second cut fits under the cap, while anything past a minute wants splitting or an external link.
Discord’s community nature sets the rhythm: videos posted in a server play inline, and inline plays beat external links on click-through by a wide margin. Inline when possible; links are the fallback, not the default.
The encoding precondition for inline playback
Only H.264 + AAC in MP4 gets the inline player: Discord’s clients handle VP9 and HEVC unstably, and some endpoints show a bare file card. Verify the codec pair before sending so recipients never have to download first.
Quality reality inside 10 MB: a minute of 1080p lands near 1.2 Mbps — tight. Dropping to 720p doubles the bits per pixel at the same size and usually looks better. The size-targeted compress tool’s Discord preset maps directly onto the cap, and the two-pass switch buys noticeably more quality per byte.
A sending strategy for gaming communities
Compress locally before posting: Discord has no friendly "auto-shrink to 10 MB" path, and a botched re-upload costs more time than a proper pre-compress. 720p two-pass at roughly 9 MB leaves margin for the thumbnail.
Footage delivery (gameplay for teammates, assets referenced by an edit) should not be squeezed under 10 MB: use documents or links and keep quality first. The inline cap serves community sharing, not asset transfer — two scenarios, two paths.