Free tool
Video Bitrate Calculator for a Target File Size
Give the duration and the size limit you have to hit, and get the video bitrate that fits — audio comes out of the same budget, not on top of it.
AhaNow tools · Updated 2026-11-03 · No sign-up, nothing leaves the page
Summary
This calculator turns a target file size and a duration into a bitrate budget, then subtracts the audio track so what is left is what the video stream can use. It is the calculation you need when a platform or a client gives you an upload limit rather than a quality target. The result is a bitrate, not a quality promise: the same bitrate looks different on different material.
Work out the bitrate for a size limit
1 MB is 1,000,000 bytes here, which is what upload limits mean. The audio track is subtracted from the same budget.
From the timeline, not the length of the source footage.
The ceiling for the whole file, as the destination states it.
The setting for the track you will actually mux.
Video bitrate you can afford
1,205 kbps
This is a ceiling for a variable-bitrate encode, not a quality setting, and container overhead is not included. Leave headroom and confirm with one test encode of the real footage.
This is the size calculation, not a quality setting. It answers “what bitrate fits in this file”, never “what bitrate looks good” — those are different questions with different answers.
What the calculator works out
A file size is bytes and a bitrate is bits per second, so the arithmetic is a unit conversion plus a division. One megabyte is eight million bits; divide the target size in bits by the duration in seconds and you have the total bitrate the file can afford. Subtracting the audio bitrate leaves the video stream's share, which is the number an encoder actually wants.
Keeping the audio in the same calculation is the part most quick estimates get wrong. A two-hour cut with a 192 kbps stereo track spends 192 kilobits every second for 7,200 seconds — 1,382,400 kilobits, or 172.8 MB — on audio alone, before a single frame of video is encoded. If the target was a 20 MB upload limit, the video budget is not small, it is negative, and the calculator says so instead of printing a negative bitrate.
How to fill in the three fields
- Enter the duration of the cut you are delivering, in seconds. Use the final runtime from the timeline rather than the length of the source footage — a two-hour recording that will be cut to forty minutes has a forty-minute budget.
- Enter the size limit in megabytes exactly as the destination states it. If a platform says 500 MB, that is the ceiling for the whole uploaded file, including audio and container overhead.
- Enter the audio bitrate you will actually mux: the number in the encoder settings for the track that ships, not the bitrate of the microphone recording or of a source file you are going to re-encode.
- Read the video bitrate as a ceiling for a variable-bitrate encode, not as a constant. A constant-bitrate encode at that number will hit the target and waste bits on static scenes.
Two-pass, one pass, and hitting the number
A single-pass variable-bitrate encode spreads bits by what the encoder sees as it goes and lands somewhere near its average, not on it. A two-pass encode looks at the whole clip first, then distributes the budget, which is why it gets closer to a hard ceiling. If the size limit is advisory, one pass with a quality target is simpler and usually looks better at the same size; if the limit is enforced by a platform, measure the first output before rendering the rest of the series in the same preset.
The headroom you leave is a property of your encoder, container and track layout, not a universal percentage. Encode thirty seconds of representative footage, look at the actual file size, and use the difference to set the target you feed this calculator. That measurement takes a few minutes and replaces every rule of thumb about overhead.
When the result will not match the file you get
Everything outside the two media streams is missing from the budget: container index, metadata, subtitle and chapter tracks, thumbnails, and any second audio track.
- Container overhead is not in the number. It is usually small, but it is not zero, and it grows with the number of tracks and the length of the index.
- A variable-bitrate encode only hits its average over the whole file. Short clips, or clips with one very static section, can land noticeably above or below the target.
- Platforms re-encode on ingest. A file that fits the limit before upload may be replaced by a different encode afterwards, and the size you calibrated against no longer describes what viewers receive.
- A second audio track, a commentary mix or burned-in subtitles all consume budget that this form does not ask about. If you need them, lower the video bitrate or raise the ceiling — the arithmetic does not have a third answer.
- Frame rate and resolution change what a bitrate buys. The same number produces a clean image at one resolution and visible blocking at another, so a bitrate copied from a different deliverable is not a starting point, it is a coincidence.
Reading the result
If the video bitrate comes out in the low hundreds of kilobits per second, the size limit is asking for something the footage will not survive: at that budget, motion turns to mush and gradients band. That is information, not a failure — it means the constraint has to move, either the duration down or the size limit up. If the audio row is flagged as exceeding the budget, the video bitrate is not the problem and lowering it further cannot help.
Questions
Why is my finished file larger than the target size?
The budget here covers the media streams. The container adds an index, headers and any extra tracks, and a variable-bitrate encode does not land on its average exactly. Both effects push the file above the calculation, so aim below the limit and confirm with one test encode of the real material before committing to a long render.
Should I use two-pass encoding?
Use it when the size ceiling is hard. Two-pass encoding spends the budget where the picture needs it and gets closer to the target than a single pass, at the cost of encoding twice. When there is no ceiling, a single pass with a quality setting is the better trade.
Does the audio bitrate really come out of the same budget?
Yes. The limit applies to the whole file, so every bit the audio uses is a bit the video cannot. At small budgets the audio can take a large share — the calculator flags the case where it takes all of it, which means the fix is a shorter clip or a lower audio bitrate, not a lower video bitrate.
What video bitrate gives good quality?
This page cannot answer that, and any page that answers it with a single number is guessing. Quality at a given bitrate depends on resolution, frame rate, how much motion and grain the footage has, and the encoder. The calculator answers the size side of the question; the quality side needs a test encode of the actual material.
Is the MB here the same MB my file manager shows?
Not always. This calculator uses 1 MB = 1,000,000 bytes, which is what upload limits and platform quotas mean by MB. Some file managers show mebibytes — 1,048,576 bytes — while still calling them MB, which makes the same file look about 4.86% larger there. Read the number in the same unit the limit uses.
Can I use this for a podcast or an audio-only file?
Not directly — it assumes a video stream and an audio stream sharing one budget. For audio-only files there is nothing to subtract, so the total bitrate is the answer, and the audio duration calculator runs the same arithmetic in the other direction.
