A five-minute training video may need to fit an upload limit even though its original recording is much larger. In HandBrake 1.10, choosing Constant Quality does not specify a final file size: different pictures can require different amounts of data at the same quality setting.

Start with the actual limit in bytes and the intended duration. Check whether the service means decimal megabytes or another unit, and whether the restriction applies to one file or an entire submission. Keep the original recording and prepare a separately named delivery copy.

Budget the whole file before setting video bitrate

For a decimal 50 MB limit and 300 seconds, 50,000,000 multiplied by eight and divided by 300 gives about 1,333,333 bits per second for everything in the file. That is roughly 1,333 kbps, not a video-only allowance.

As an illustrative starting budget, 1,100 kbps video plus one 128 kbps audio track works out to about 46.05 MB before container overhead. Additional audio tracks consume part of the same allowance. These figures demonstrate the calculation; they do not establish that a particular training video remains readable at that bitrate.

On the Video tab, select Average Bitrate and enter the video portion of the budget. If the chosen encoder offers a multipass option, consider it for this size-led encode. HandBrake's documentation recommends multipass for average-bitrate work where supported.

Review the selected audio tracks before starting. Retain the tracks the audience actually needs, accounting for each one instead of silently discarding a language or accessibility requirement.

Accept the result against both constraints

After encoding finishes, inspect the complete output's size in bytes. Average bitrate is a planning control, so leave margin and verify the actual file rather than promising an exact ceiling from the calculation alone.

Play the most demanding sections: moving detail, small labels and speech over background sound. If the file fits but the instructions cannot be followed, the delivery has failed. Reconsider duration, delivery method or an agreed quality compromise instead of repeatedly lowering the bitrate without a usability check.

Keep the accepted file, its actual byte count and the settings together. A short sample can reveal quality problems, but only the complete deliverable establishes compliance with the size limit.

Sources: HandBrake 1.10 documentation.