Why Your WAV Files Are So Huge: Sample Rate, Bit Depth and File Size

A three-and-a-half-minute song at 48kHz/24-bit stereo is about 60 MB uncompressed. Bump that to 96kHz and it’s 120 MB. Track a full band at 192kHz/32-bit float across 24 inputs for a two-hour session and you’re suddenly staring at a number that makes your SSD nervous. None of this is a bug or bloated software — it’s arithmetic. Uncompressed audio size is a straight multiplication of four numbers, and once you see the formula, every “why is this session so big” moment stops being a mystery.

The formula behind every WAV file

Uncompressed PCM audio (WAV, AIFF) stores every single sample as raw numbers, with no compression removing any of it. The size in bytes is:

bytes = sample rate × bit depth × channels × duration (seconds) / 8

Each term does exactly what it says. Sample rate is how many snapshots of the waveform are captured per second — 44,100 for CD audio, 48,000 for video and most modern production, up through 96,000 and 192,000 for high-resolution capture. Bit depth is how many bits describe the amplitude of each snapshot — 16-bit for CD, 24-bit for professional recording, 32-bit float for mixing headroom that never clips. Channels just multiplies everything by however many discrete audio streams you’re storing — 1 for mono, 2 for stereo, 6 for 5.1 surround, 8 for 7.1. Divide by 8 at the end because the other three terms are in bits, and a byte is 8 bits.

Run the numbers for a 3:30 stereo track at CD quality: 44,100 × 16 × 2 × 210 / 8 ≈ 37 MB. The same track at 48kHz/24-bit — the de facto standard in most DAWs today — comes out to roughly 60 MB, because both the sample rate and the bit depth went up. Every one of those four inputs is a linear multiplier, so doubling any single one roughly doubles the file, and stacking increases compounds fast: a jump from 44.1kHz/16-bit stereo to 96kHz/24-bit surround (6 channels) is nearly an 8x size increase for the same duration.

Bitrate is the same math, just per second

The other number worth knowing is bitrate — how many bits of data flow per second of audio, independent of duration:

bitrate (bits/sec) = sample rate × bit depth × channels

A 48kHz/24-bit stereo file runs at 2,304,000 bits/sec, or 2,304 kbps. Compare that to a 320kbps MP3 and the gap is obvious: uncompressed audio carries roughly seven times the data of even the highest-quality lossy MP3, which is exactly what that data is spent on — no psychoacoustic modeling has thrown anything away.

Why FLAC isn’t a fixed fraction of WAV

FLAC and ALAC are lossless — every bit of the original signal is recoverable — but they’re also compressed, using the same idea as ZIP: find redundancy in the data and encode it more efficiently. That means FLAC’s compression ratio depends on the material itself. Simple, sparse audio (an acoustic guitar, spoken word, a quiet passage) compresses well, sometimes down to 40% of the original PCM size. Dense, noisy, or highly processed audio (distorted guitars, white noise, aggressively limited masters) compresses poorly, sometimes barely below 70%. There’s no single conversion factor — “FLAC is about half the size of WAV” is a reasonable rule of thumb for typical music, not a guarantee. Lossy formats like MP3 and AAC don’t have this variability, because they encode at a fixed target bitrate regardless of content, which is why their file sizes are so easy to predict: bitrate × duration / 8, full stop.

Where this actually bites you

Three situations turn this formula from a curiosity into a planning problem:

Multitrack session storage. A 24-track session at 48kHz/24-bit for a 4-minute song is 24 individual WAV files, each around 60 MB — roughly 1.4 GB before you’ve bounced a single mix, printed a stem, or saved an alternate take. Studios doing 10+ songs a month need to budget storage in the hundreds of gigabytes, not tens.

Sample rate decisions for recording. 192kHz sounds like “more quality,” and technically it captures frequency content up to 96kHz — far beyond the ~20kHz limit of human hearing. For most music production, 48kHz or 96kHz captures everything audible with comfortable headroom for pitch-shifting and time-stretching, while 192kHz mainly earns you 4x the file size of 48kHz for content nobody can hear. It has real uses — ultrasonic research, some high-end mastering workflows, machine-learning training sets — but it’s rarely the right default for a mix session.

Delivery and streaming. If you’re sending stems to a client or uploading to a service with bandwidth or storage limits, the gap between a 24-bit WAV stem pack and a well-encoded FLAC or even 320kbps MP3 bounce can be the difference between a five-minute upload and a five-hour one — worth checking against a bandwidth and download time calculator before you commit to a delivery format for a large batch of files.

Running the numbers without doing the math by hand

Because the formula stacks four variables, mental math gets unreliable past the “48kHz/24-bit stereo” case everyone has memorized. The Sample Rate & Bit Depth File Size Calculator takes sample rate, bit depth, channel count and duration, and returns the uncompressed size instantly alongside estimated sizes for FLAC, ALAC, MP3 320, AAC 256 and Opus 128 — so you can compare “what will this session actually cost me in disk space” across every format you might deliver in, before you record a single track.

A practical checklist

Before you commit a session to a sample rate and bit depth, ask three questions. Does the delivery target require a specific rate — video work usually wants 48kHz, some mastering houses want 96kHz submissions? Will you be doing heavy time-stretching, pitch correction, or slow-motion sound design, where a higher sample rate genuinely helps the algorithm have more data to work with? And do you have the storage and backup budget for the multiplier that comes with going up a tier? For the overwhelming majority of music production, 48kHz/24-bit stereo is the sweet spot — professional headroom without the multitrack storage bill that 96kHz or 192kHz brings.

If you’re also chasing exact millisecond timing for delays and echoes synced to tempo, the BPM to Milliseconds Delay Calculator handles that half of the mixing-math problem — between the two tools you can plan both the timing and the storage footprint of a session before you hit record.