Audio Bitrate Math: One Formula, Three Questions

Audio files hide a suspiciously simple law: size is bitrate multiplied by time. Everything else — the megabytes your download page shows, the gigabytes your archive drive needs, the true rate your "320 kbps" file actually delivers — falls out of that one multiplication and its two inverses. Learn the law once and you can budget a podcast season, sanity-check a download, or plan a hard drive without a spreadsheet.

1. One formula, two inverses

Bitrate counts bits per second; a byte is eight bits. Chain the conversions and the file size follows directly:

bytes = kbps × 1000 ÷ 8 × seconds = kbps × 125 × seconds

The shortcut is worth memorising: kbps × 125 gives bytes per second. A 320 kbps file writes 40,000 bytes each second, so a 3:30 track (210 s) is 8,400,000 bytes — 8.4 MB. The same equation solves the other two questions: divide bytes by seconds to recover a bitrate, divide bytes by the byte-rate to learn how long a file can run. Three tools in one line.

2. The bits-versus-bytes trap

The most common error in audio math is forgetting the factor of eight. Network and connection speeds speak in bits (Mbps), file systems speak in bytes (MB). A "100 Mbps" connection does not download 100 MB each second — it downloads 12.5. The same confusion afflicts storage estimates: 128 kilobits per second is 16 kilobytes per second, and a recording planned as "128 KB per second" overestimates storage by 8×. Whenever a number looks too big or too small, check which unit the label actually meant.

3. MB versus MiB: the 4.9% disagreement

Even after the bits settle, two conventions label the bytes. SI megabytes count by thousands — 1 MB is exactly 1,000,000 bytes — and storage vendors, download pages and bitrates all use them. Binary mebibytes count by powers of two — 1 MiB is 1,048,576 bytes — and that is what most operating systems report. The same 8,400,000-byte file is 8.4 MB on a spec sheet and 8.01 MiB in your file manager. Nothing is missing; the labels disagree by 4.9% at every step. The habit that ends the confusion is showing both numbers side by side, which is exactly what a good calculator does.

4. Storage planning: per minute, per hour, per season

Single files matter less than fleets of them. The useful planning numbers are rates: bytes per minute and bytes per hour at your working bitrate. At 320 kbps that is 2.4 MB per minute or 144 MB per hour; at 128 kbps, 0.96 and 57.6; at CD-rate 1,411 kbps, about 10.6 MB per minute. Multiply by your real volume — 100 hour-long podcast episodes at 128 kbps is 5.76 GB, a stem archive of 50 two-hour sessions at 1,411 kbps is over a terabyte — and the "should I buy the bigger drive" question answers itself. A copies multiplier turns one file's size into an archive's size without touching a calculator twice.

320 kbps → 2.4 MB/min → 144 MB/hour → 5.18 GB per 36-hour album

5. Reading a file backwards

The inverse direction is the lie detector. Take any file's byte count and duration, and bytes × 8 ÷ seconds reveals the average bitrate it truly carries. A download advertised as 320 kbps that computes to 212 has been re-encoded, padded with silence, or mislabeled; lossless files that compute far above 1,411 kbps are genuinely carrying more than CD-rate audio. The third direction — given a size and a bitrate, how long does it play — answers capacity questions: a 700 MB disc at 1,411 kbps holds about 66 minutes, which is why CD burns always seemed to end just past the hour. One formula, three questions, no surprises left.

Try it yourself

Open the Audio Bitrate Calculator and reproduce the numbers above: 320 kbps for 210 seconds, then flip to the inverse mode with one of your own files to see its true bitrate. To plan where those files come from, work out clip lengths with the Sample Length Calculator and total a release's running time with the Set Time Calculator before you render a single export.