Media File Size Calculator

Estimate video and audio file sizes from bitrate and duration, with codec presets and upload time — the arithmetic behind every export dialog.

Estimated file size
Upload time
Per hour of content

Size = bitrate × duration ÷ 8. Real encoders use variable bitrate, so treat results as ±20%. Sizes use decimal units (1 GB = 1,000 MB) like drive makers and most upload limits; Windows displays binary GiB, which reads ~7% smaller for the same file.

The preset is the answer; the duration is just multiplication

Duration is the box people fuss over, and it is linear — an hour is exactly twice half an hour, at every preset, always. The dropdown is not. One hour of content, top to bottom:

PresetPer hourFits in a 25 MB emailFits on a DVD
4K30 H.264 18.00 GB 5.0s 15m 40s
4K30 H.265 9.00 GB 10s 31m 20s
1080p60 H.264 5.40 GB 17s 52m 13s
1080p30 H.264 3.60 GB 25s 1h 18m
720p30 H.264 2.25 GB 40s 2h 5m
1080p30 H.265 1.80 GB 50s 2h 37m
WAV / CD 635.0 MB 2m 22s 7h 24m
FLAC 450.0 MB 3m 20s 10h 27m
MP3 320 144.0 MB 10m 25s 32h 38m
MP3 192 86.4 MB 17m 22s 54h 24m
MP3 128 57.6 MB 26m 3s 81h 36m

Top to bottom is 312.5×: 4K30 H.264 against MP3 128, which is the ratio of their bitrates and nothing else. A 25 MB attachment limit holds 5 seconds of 4K, or 26 minutes of music. Same limit, same arithmetic. Every capacity in the table orders the presets identically, because only the bitrate is doing any work. Which means one wrong choice in the dropdown outweighs any plausible mistake about how long the recording is.

Resolution is a bigger lever than codec, by two and a half times

Starting from 4K30 H.264 and using this page's own presets, both choices have a price:

ChangeFromToDivides the file by
Codec only4K30 H.2644K30 H.265
Resolution only4K30 H.2641080p30 H.264
Both4K30 H.2641080p30 H.26510×

Switching codec halves it; dropping the resolution divides it by 5. The resolution change is worth 2.5× the codec change. And they multiply rather than adding, so doing both gives 10×. Re-encoding to a newer codec is the change people reach for first because it costs nothing visible. Dropping the resolution is the one they resist, and it is the one that does the work.

Whether you can upload faster than you record has nothing to do with length

Upload time divided by recording time is bitrate divided by upload speed — the duration cancels out completely. A ten-second clip and a ten-hour recording sit at the same ratio. So there is one clean threshold, and it does not move:

Upload speedShare of the runtimeTo send an hour at 8 Mbps
5 Mbps 160% 1h 36m
8 Mbps 100% 1h
10 Mbps 80% 48m 0s
20 Mbps 40% 24m 0s
50 Mbps 16% 9m 36s
100 Mbps 8% 4m 48s

Break-even is where the upload speed equals the bitrate — 8 Mbps for 8 Mbps video. Below it, sending takes longer than filming did; above it, less. Shortening the clip does not help, because it shortens both sides equally. Worth checking the upload number rather than the download one: consumer connections are asymmetric, and the figure advertised is almost always the download.

Lossless compression saves less than most people expect

FLAC at around 1,000 kbps is 71% the size of the CD-quality WAV it came from. A lossless codec can only exploit redundancy that is genuinely there, and music has less of it than text does — 29% off is a good result, not a disappointing one. MP3 at 320 kbps is 23% of the same WAV, and most listeners cannot tell it apart. That is 2.7× the saving, bought with information you were unlikely to use — which is the entire case for lossy compression in one comparison.

The 1,411 kbps figure is not a convention either: a CD stores 44,100 samples a second, 16 bits each, across 2 channels, which is 1,411,200 bits a second exactly. Everything above is derived from that one number.

How to use

  1. Enter the bitrate and duration.
  2. Or pick a codec preset for a starting figure.
  3. Read the file size and estimated upload time.
  4. Add a margin — real encodes vary.

Frequently asked questions

How is file size calculated?

Bitrate multiplied by duration, with the units reconciled. Bitrate is in bits per second and file size in bytes, so the product is divided by eight — which is the step people miss, giving an answer eight times too large.

What is the difference between constant and variable bitrate?

Constant bitrate holds the rate steady, giving a predictable file size and wasting data on simple scenes. Variable bitrate spends more on complex passages and less on simple ones, producing better quality for the same average size but a less predictable result.

Why is my exported file a different size from the estimate?

Because variable bitrate encoding targets an average rather than hitting it exactly, and because containers add overhead for audio, metadata and indexing. An estimate within ten per cent of the actual file is doing well.

What bitrate do I need?

It depends on resolution, frame rate and content. Fast motion and fine detail need considerably more than a static talking head at the same resolution, which is why a single number per resolution is only a starting point. Platforms publish recommended figures for their own encoders.

Does a newer codec really save that much?

Substantially. Modern codecs achieve comparable quality at roughly half the bitrate of older ones, at the cost of much slower encoding and narrower device support. Whether the trade is worth it depends entirely on where the file is going to be played.

Why does upload take longer than the estimate?

Because home connections are usually asymmetric, with upload speed a fraction of download, and because protocol overhead and the receiving server both take a share. Estimating from your download speed is the common mistake, and it can be out by a factor of ten.

🔒 This tool runs entirely in your browser. Nothing you enter is uploaded, logged, or stored.