Video Bitrate, File Size and Duration: How the Three Numbers Lock Together

Every time you export a clip, three numbers are fighting each other: the bitrate you set in the encoder, the length of the footage, and the size of the file that lands on disk. Most people only find out the third number after a twenty-minute render, then discover it is too big for the upload and start over. The fix is to understand that these three values are not independent. They are tied together by one short equation, and once you know it you can predict any one of them before you press export.

The formula that ties bitrate, size and duration

Here is the whole relationship in one line:

file size (MB) = bitrate (Mbps) × duration (seconds) ÷ 8

The divide-by-8 is the part people forget. Bitrate is measured in megabits per second, but file size is measured in megabytes, and there are 8 bits in a byte. Skip the division and your answer is eight times too large.

What makes this useful is that it works in any direction. Give it bitrate and duration and it returns size. Give it size and duration and it returns the bitrate you need to set. Give it size and bitrate and it returns how long you can record. Same equation, rearranged:

bitrate (Mbps) = file size (MB) × 8 ÷ duration (seconds)
duration (s)   = file size (MB) × 8 ÷ bitrate (Mbps)

That is exactly what the Video Bitrate Calculator does: you fill in any two fields and it solves the third, so you never have to remember which way the 8 goes.

A worked example you can check by hand

Take a 10-minute clip exported at 8 Mbps. Ten minutes is 600 seconds, so:

8 × 600 ÷ 8 = 600 MB

The two 8s cancel cleanly here, which is a handy sanity check: at 8 Mbps every second is exactly 1 MB. A 10-minute 8 Mbps video is about 600 MB. Drop the bitrate to 4 Mbps and the size halves to 300 MB. Push it to 16 Mbps and it doubles to 1.2 GB. Size scales linearly with bitrate, so cutting the bitrate is the most direct lever you have on file size.

Now flip the question. Suppose a client share has a 250 MB limit and your clip runs 600 seconds. What bitrate fits?

250 × 8 ÷ 600 ≈ 3.33 Mbps

So set the encoder to roughly 3.3 Mbps and the export lands under the cap on the first try.

Don't forget the audio track

The video stream is not the only thing in the file. Audio rides alongside it, and on longer clips it is not negligible. Audio bitrate is quoted in kbps (kilobits per second), so a typical AAC track at 192 kbps is 0.192 Mbps. You add it to the video bitrate before applying the formula, because the container stores both streams.

Over a 30-minute recording, that 192 kbps of audio works out to:

0.192 × 1800 ÷ 8 ≈ 43 MB

Forty-three megabytes of audio alone is enough to push a borderline file over an upload cap. The calculator keeps a separate audio field and sums it for you, so when you read the predicted size it already accounts for both streams. If you are exporting a silent or video-only file, set audio to 0.

Picking a bitrate for resolution and platform

A higher bitrate does mean more detail at a fixed resolution and codec, because more bits per second describe motion, gradients and fine texture. But beyond a certain point the encoder is already near transparent and the extra bits are wasted weight. The goal is the lowest bitrate that still looks clean for your content.

Rough starting points, which you can refine while watching the predicted size:

• 1080p30 for YouTube: about 8 Mbps. A talking head survives at 6 Mbps; fast game capture or sports wants 12 Mbps or more.
• 1080p60: closer to 12 Mbps, because there are twice as many frames to describe.
• 4K30: around 45 Mbps for upload. This is why a 4K export balloons so fast.
• Local editing or archive masters: 20 to 50 Mbps, deliberately high so the footage survives re-encoding.
• A tight Discord-style 25 MB cap: solve for bitrate from the size and length instead of guessing.

Codec choice changes the whole table. H.265 and AV1 reach the same look at roughly half the bitrate of H.264, so the same visual quality can mean half the file. When you change resolution you are also reshaping the frame, and an aspect ratio calculator keeps your width and height proportional so you are not encoding letterboxed black bars.

Balancing quality against size

I spent years over-exporting out of fear. I would set 20 Mbps on a simple screen recording "to be safe," then wonder why a five-minute tutorial was three quarters of a gigabyte. The habit that fixed it was watching the predicted size react as I dragged the bitrate down. At some point the preview stops looking worse but the number keeps falling — that crossover is the bitrate I actually want. For a screencast it usually sits far lower than my nervous default. Seeing the size update in real time turned a guess into a decision.

The practical loop is simple. Start from the preset for your platform, set your real clip length, read the predicted size, and only then trade quality for size if the file is too large. Because size moves linearly with bitrate, a 10% bitrate cut is a 10% smaller file — easy to reason about once the units are straight.

Storage planning is the same equation read sideways. A camera writing a 50 Mbps codec to a 64 GB card holds about 170 minutes, which you can confirm by solving for duration. When you are juggling gigabytes, megabytes and minutes, a data storage converter helps you keep MB, GB and the card's real capacity aligned before you commit to a shoot.

Keep the units straight

The single most common mistake is mixing rates and amounts. Mbps is a rate that flows over time; MB is a fixed quantity sitting on disk. A 10 Mbps stream is not a 10 MB file — at 10 Mbps you accumulate 1.25 MB every second, so a 10-second clip is 12.5 MB. The other classic slip is typing 8000 into an Mbps field that wanted 8, or putting an audio number meant for kbps into the Mbps box, which throws the result off by a factor of a thousand. Label-check every field before you trust the output.

Once the three numbers click into place, exporting stops being a gamble. You decide the size you can afford, the calculator hands you the bitrate, and the render comes out the size you planned the first time.

---

Made by Toolora · Updated 2026-06-13