How Do You Send a 30 Minute Video on Discord?

What a 30 minute video actually weighs

Doubling the length doubles the file, so a 30 minute clip lands at three times the weights you may have seen for 10 minutes. Thirty minutes of 1080p60 gameplay at a typical 12 Mbps recording bitrate is about 2.7GB. The same half hour at 720p30 runs about 1.1GB, and a 480p capture about 450MB. Discord's caps are 20MB free, 50MB Nitro Basic, and 1GB Nitro (the free cap was raised from 10MB in August 2026). Even the smallest of those weights is 22 times the free cap, and the largest is more than double Nitro's 1GB, which is why this length deserves its own guide instead of a one-line answer.

The quality floor: why 20MB only works for slideshows at 30 minutes

Here is the math that decides everything. Twenty megabytes across 1800 seconds works out to roughly 89 kbps of total bitrate. After setting aside 64 kbps for audio, the video stream gets about 25 kbps, which is below the bitrate early-2000s phone cameras produced. Real footage at that budget turns into a blur of blocks whenever anything moves. The 10 minute version of this question works because 600 seconds spreads the same 20MB into a usable 200 to 250 kbps; triple the seconds and the budget per second collapses. So the honest answer for 30 minutes is: do not chase one 20MB file. Pick one of the three routes below, each of which keeps quality at a level people can actually watch.

Way 1: split it into three parts (free, plays inline)

Cutting the video into three 10 minute segments is the best free route, because every segment gets the full 20MB budget and lands at usable 360p to 480p quality. Name the parts 01, 02 and 03 so they sort correctly in chat, then send them back to back; Discord plays each one inline and nobody has to click out. If your footage is a lecture, a stream VOD or a gameplay session with natural breaks, cut on the breaks and the parts feel intentional rather than chopped. The BitSized compressor reads the duration of each segment and encodes it to exactly 20MB on your own device, so even a 2.7GB source never uploads anywhere.

Way 2: Nitro's 1GB with a 950MB target (best quality)

If you have full Nitro, the play is to compress to a 950MB target rather than attaching the raw file. A 720p30 recording at 1.1GB is just over the 1GB cap, and a light target-size pass shaves it under with no visible change; a 1080p60 source at 2.7GB compresses to 950MB at a bitrate most viewers cannot distinguish from the original on a chat-sized player. Either way the result attaches as one file, plays inline, and keeps quality that splitting-to-20MB cannot match. Nitro Basic's 50MB does not solve this length; a 450MB minimum source is still nine times over. The Nitro limit comparison shows what each plan actually covers.

Way 3: cloud link (full quality, zero limits)

Upload the video to Google Drive, Dropbox or Streamable and paste the link in chat. This route has no size rules and delivers the original file bit for bit, which makes it the right choice for archival footage, anything viewers may download, and cases where the 2.7GB original matters. The trade is friction: viewers click out to watch, Drive links sometimes need sharing permissions fixed before they work for everyone, and Streamable's free tier caps video length. For a one-time watch, Way 1 or Way 2 is faster for everyone in the channel.

Why many online compressors refuse 30 minute videos

A pattern worth knowing before you pick a tool: upload-based compressors struggle at this length. They cap how long a video they accept, time out on gigabyte uploads, or hand back a corrupted 0-byte file, failure modes users document regularly on Reddit threads about long clips. The reason is structural: your file travels to their server, gets processed in a shared queue, and travels back, and 30 minutes of footage is a gigabytes-scale job that pipeline handles badly. BitSized was built the other way on purpose. The encoding runs in your browser through WebAssembly, there is no upload step to time out, no length cap, no watermark, and the exact target size you pick is the size you get, whether that is 20MB per part or 950MB for a Nitro attach.

Frequently asked questions

Related guides and tools