WAV: Uncompressed Audio for Professionals

WAV is the simplest audio format to understand: it's raw sound, written directly to disk. No compression algorithm, no psychoacoustic tricks, no quality trade-offs. Every sample of the original waveform is stored as a number, and when you play it back, those numbers become sound again — identical to the original.

This simplicity comes at a cost: size. A single minute of CD-quality audio in WAV is 10.1 MB. A full album runs 600-700 MB. An hour-long podcast session at production quality (48 kHz / 24-bit) hits 500 MB. For distribution, this is impractical. For production, it's exactly right.

WAV has been the professional audio standard since Microsoft and IBM introduced it in 1991. Despite FLAC offering the same quality at half the size, and despite the 4 GB file-size limitation, WAV persists in studios because it removes every possible variable between the audio data and the tools that process it.

PCM: How WAV Stores Sound

WAV files contain PCM (Pulse Code Modulation) data — the most direct digital representation of analog sound. The process works like this:

1. Sampling: The analog waveform is measured at regular intervals. CD audio measures 44,100 times per second (44.1 kHz). Each measurement captures the amplitude of the wave at that instant.
2. Quantization: Each sample's amplitude is mapped to the nearest value on a fixed scale. 16-bit quantization gives 65,536 possible values. 24-bit gives 16,777,216 values — far more precise.
3. Storage: Each quantized sample is written as a binary number. For stereo, left and right samples alternate: L1, R1, L2, R2, L3, R3...

That's it. No transform, no prediction, no entropy coding. The file is literally a sequence of numbers representing air pressure at each point in time. This directness is why DAWs (Digital Audio Workstations) work with PCM natively — it's the format that audio processing algorithms expect.

The RIFF Container Structure

WAV isn't just raw PCM data dumped into a file — it uses the RIFF (Resource Interchange File Format) container. A WAV file has this structure:

• RIFF header: File identifier and total size
• fmt chunk: Audio format (1 = PCM), number of channels, sample rate, byte rate, bits per sample
• data chunk: The actual PCM audio samples
• Optional chunks: LIST (metadata), cue (markers), smpl (loop points), bext (Broadcast Wave extension)

The fmt chunk is what tells a player how to interpret the data. Without it, the raw bytes are meaningless — you'd need to guess whether it's 16-bit or 24-bit, mono or stereo, 44.1 kHz or 48 kHz. The RIFF header makes WAV self-describing.

One limitation of RIFF: the size field is a 32-bit unsigned integer, capping files at 4 GB. At CD quality (10.1 MB/min), that's about 6.6 hours. At 24-bit/96 kHz stereo (34.6 MB/min), it's under 2 hours. This matters for live recording sessions and long-form audio work.

CD Quality: The Numbers Behind 44.1 kHz / 16-bit

CD audio specifications (Red Book, 1980) chose 44.1 kHz sample rate and 16-bit depth. Here's why those numbers, and exactly how big the files are:

44.1 kHz sample rate: The Nyquist-Shannon theorem requires sampling at 2x the highest frequency you want to capture. Human hearing tops out at ~20 kHz. 2 × 20 kHz = 40 kHz minimum, plus a guard band for the anti-aliasing filter = 44.1 kHz. (The .1 kHz comes from historical video tape storage constraints during early digital recording.)

16-bit depth: Each sample uses 16 bits, giving a dynamic range of 96 dB (calculated as 6.02 × number of bits). The quietest room you've ever been in is about 30 dB. The threshold of pain is ~130 dB. 96 dB of dynamic range covers everything useful for music playback with room to spare.

File size calculation: 44,100 samples/sec × 16 bits × 2 channels = 1,411,200 bits/sec = 176,400 bytes/sec = 10.1 MB per minute. A 45-minute album: ~454 MB. A 3-minute song: ~30 MB.

Why Producers Use WAV Despite the Size

Every audio professional knows FLAC exists. They still use WAV. Three reasons:

Zero Decode Overhead

A music production session might have 40-80 audio tracks playing simultaneously. Each track in FLAC requires real-time decompression. Each track in WAV is direct memory read — no CPU cycles for decoding. On a modern workstation the difference per track is trivial, but multiplied across dozens of tracks with plugins and effects running simultaneously, it adds up. WAV eliminates one variable from the performance equation.

Perfect Edit Transparency

Cutting, copying, pasting, and crossfading WAV audio involves manipulating PCM samples directly. There's no encode/decode cycle at any point. You can bounce (export) a mix of 50 WAV tracks into a new WAV file, re-import it, process it further, and export again — zero quality change at every step. With lossy formats, each bounce re-encodes and further degrades.

Universal Tool Support

Every DAW, audio editor, plugin, and hardware recorder supports WAV. Not most — every single one. Pro Tools, Logic, Ableton, Audacity, Reaper, FL Studio, Cubase, Studio One — all handle WAV natively. Some have FLAC support, but WAV is guaranteed. When you're collaborating with other studios or sending stems to a mixing engineer, WAV is the format that never needs a "can you open this?" conversation.

The 4 GB Limit and RF64

Standard WAV files hit a hard ceiling at 4 GB because the RIFF header stores file size as a 32-bit integer (max value: 4,294,967,295 bytes). At CD quality, 4 GB holds about 6.6 hours. At 24-bit/96 kHz stereo, it's about 1 hour 57 minutes.

For long recording sessions — live concerts, film scoring, podcast recordings — this can be a real problem. Solutions:

• RF64: A backward-compatible extension that uses 64-bit size fields. Supports files up to 16 exabytes (effectively unlimited). Most modern DAWs and recorders auto-switch to RF64 when approaching the 4 GB boundary.
• BWF (Broadcast Wave Format): An extension of WAV used in broadcast and film. Adds timestamp metadata, loudness information, and originator data. BWF files use the .wav extension and are backward-compatible with standard WAV players, which simply ignore the extra metadata chunks.
• Split files: Some recorders automatically split into multiple WAV files at the boundary. This works but creates editing headaches.

If your recording workflow involves sessions longer than 2 hours at high resolution, make sure your recorder supports RF64 or BWF64. Most professional recorders released after 2010 do.

WAV vs FLAC vs AIFF: When Size Matters

The practical comparison for lossless audio:

For a 500-track music library: WAV = ~25 GB, FLAC = ~13 GB. Same audio, half the disk space. For archiving, FLAC is the rational choice. For active production work, WAV's decode-free playback and universal tool support justify the extra storage. Use FLAC for storage, WAV for work, and convert between them as needed — it's lossless in both directions.

Converting WAV Files

WAV is the ideal source for any conversion because it contains the complete, uncompressed audio. Converting WAV to a lossy format (MP3, AAC, OGG) is a one-way trip — data is permanently discarded. Always keep the WAV as your master.

Converting WAV to FLAC is lossless and reversible — the audio data is identical, just stored more efficiently. Converting back (FLAC to WAV) reconstructs the exact original file.

Common conversions: WAV to MP3 | WAV to FLAC | WAV to AAC | WAV to OGG | WAV to Opus | WAV to M4A | MP3 to WAV | FLAC to WAV

WAV is brute-force simplicity: every sample, every bit, no tricks. It's too large for distribution and too basic for metadata, but it's the format audio professionals trust because it introduces zero variables between the source audio and the tools that process it.

For archiving, convert to FLAC — same quality, half the size. For sharing, convert to MP3 or AAC. For production, keep everything in WAV until the final delivery step. Convert WAV to MP3, WAV to FLAC, or MP3 to WAV — free at ChangeThisFile.