Skip to calculator
Veomark

Free · Instant · No signup

Bandwidth / Bitrate to File Size Estimator

File size from video or audio bitrate and duration, in MB and GiB.

Page updated 2026-09-04.

Bandwidth / Bitrate to File Size Estimator visual
Sponsored

Calculator

Default 8000 kbps (about 8 Mbps video).

Default 12.

Default 3%.

Calculated Results

Size MB

--

Size GiB

--

Payload bits

--

Sponsored

From bitrate and duration to an actual file size

An 8,000 kbps (8 Mbps) bitrate over a 12-minute (720-second) duration, with 3% container overhead, produces a payload of 5,932,800,000 bits, which converts to 741.60 MB or 0.6907 GiB.

The core formula is straightforward -- bitrate x duration in seconds / 8 gives bytes -- but getting from raw payload bits to a final file size correctly requires two separate conversions: bits to bytes (divide by 8), and then accounting for container overhead (the extra bytes added by the file format's own structure: headers, index tables, metadata) on top of the raw encoded payload.

MB (megabytes, decimal, 1,000-based) and GiB (gibibytes, binary, 1,024-based) are genuinely different units shown side by side here -- 741.60 MB and 0.6907 GiB describe the same actual amount of data, but using different unit conventions, which is exactly the kind of mismatch that makes a file manager's reported size differ from what you might expect from a bitrate calculation.

Why container overhead isn't just a rounding factor

bitrate x seconds / 8. Container overhead is a percent you can add. Different container formats (MP4, MKV, WebM) each have their own overhead characteristics for storing metadata, chapter markers, and multiple audio/subtitle tracks -- 3% is a reasonable planning estimate, but a file with many additional tracks or extensive metadata could carry meaningfully higher overhead than a simple single-track file.

This calculates payload size from a target bitrate -- it's the planning-forward direction (deciding what bitrate to encode at to hit a target file size, or predicting size from a chosen bitrate), the reverse of measuring an existing file's actual bitrate after the fact.

Bitrate here represents a constant, average rate -- real video encoding often uses variable bitrate (VBR), where actual bit usage fluctuates scene by scene (more bits for complex/fast-motion scenes, fewer for static ones), which can make an actual VBR-encoded file's size differ somewhat from a pure constant-bitrate calculation like this one.

Related file-size and transfer-time tools

Once you know the resulting file size, the Data Transfer & Download Time Calculator estimates how long it would take to move that file over a given connection speed.

For converting the resulting size into other storage units, the General Data Storage Unit Converter is the broader reference.

Frequently Asked Questions (FAQ)

How is the 741.60 MB file size calculated?

Payload bits = bitrate x duration in seconds = 8,000,000 bits/sec x 720 sec = 5,760,000,000 bits, then adjusted for 3% container overhead. Converting to bytes (divide by 8) and then to MB gives 741.60 MB.

Why are MB and GiB both shown, and why do they look like different numbers?

MB (megabyte) uses a decimal, 1,000-based convention, while GiB (gibibyte) uses a binary, 1,024-based convention. 741.60 MB and 0.6907 GiB represent the exact same amount of data expressed in these two different unit systems -- neither figure is wrong, they're just different conventions.

What does container overhead actually account for?

bitrate x seconds / 8. Container overhead is a percent you can add. It represents the extra bytes a file format (MP4, MKV, WebM, etc.) adds beyond the raw encoded audio/video payload -- things like headers, index tables, chapter markers, and metadata. Files with more tracks or richer metadata typically carry more overhead than a simple, minimal file.

Does this work for variable bitrate (VBR) encoded content?

It models a constant average bitrate. Real VBR encoding varies bit usage scene by scene, so an actual VBR file's size could differ somewhat from this calculation, even when using the same average bitrate as an input.

Can I use this to figure out what bitrate to encode at for a target file size?

Yes -- rearranging the same formula (target bytes x 8 / duration in seconds, adjusted for expected overhead) works backward from a target size to a required bitrate, which is a common practical use for this same relationship.