Question 1

Why did Discord reject my video even though Handbrake said 24.8 MB?

Accepted Answer

Container muxing overhead and Discord re-inspection. Video and audio streams live inside an MP4/MKV container that requires header data (such as the moov atom, chunk offset tables, and sync packets). In Handbrake, estimating only the raw video/audio payload leaves out this metadata. Furthermore, Discord's ingest servers re-check the exact byte count and reject uploads even 1 byte over 25,000,000 bytes. BitrateCalc's built-in -5% safety margin guarantees you never get rejected.

Question 2

Why shouldn't I use CRF (Constant Quality) in Handbrake to hit a target file size?

Accepted Answer

CRF (Constant Rate Factor) targets visual fidelity, NOT file size. A 60-second video of low-motion talking heads with CRF 22 might be 10 MB, but high-action gameplay with grass, water, or confetti with the exact same CRF 22 will explode past 60 MB. When you have a strict limit like Discord 25MB or 500MB, 2-Pass Average Bitrate is mathematically required.

Question 3

Why does 2-Pass VBR take twice as long to encode?

Accepted Answer

In pass 1, the encoder analyzes every frame across your entire timeline to identify which shots are static and which have fast motion. In pass 2, it applies your exact target bitrate, stealing bits from still scenes and giving them to action sequences. While it takes longer, it delivers pristine visuals while staying strictly under your file size limit.

Question 4

What audio bitrate gives the best balance between quality and file size?

Accepted Answer

For short videos under strict limits, 128 kbps AAC stereo is the perceptual sweet spot—it frees up maximum megabytes for your video frames without sounding muffled. For music videos or cinematic sound, use 192 kbps. Going above 192 kbps on a compressed 25 MB clip wastes precious bitrate that your video stream desperately needs.

Video Bitrate Calculator for Discord & Web

Target Parameters

Discord & Video Bitrate FAQ