Skip to content
Back to Blog
informational

What Is PCM Audio? The Format Behind WAV and AIFF

2026-05-17 9 min read

PCM Is Not a File Format — It's a Method

Let's clear up a common misconception. When you see a WAV or AIFF file, you're not looking at a 'PCM file'. PCM isn't a file format at all. It stands for Pulse-Code Modulation, the fundamental process of turning analog sound into digital data. WAV and AIFF are just the containers, the wrappers holding that PCM-encoded audio. The process is straightforward. An analog waveform is sampled thousands of times per second. Then, each sample's amplitude is measured and assigned a number. This creates a long stream of numbers that can reconstruct the original sound with high fidelity. This is the opposite of formats like MP3 or AAC. Those formats use clever math to throw away audio data they think you won't hear, making files smaller. PCM is brutally honest: it keeps everything. No shortcuts. A 10-second stereo recording at CD quality (44,100 Hz sample rate, 16-bit depth, stereo) will always be 10 × 44,100 × 2 bytes × 2 channels, which works out to about 1.76 MB of raw data. This distinction isn't just academic; it's the language of professional audio. When a video editor asks for 'uncompressed audio,' they mean PCM. When a mastering engineer demands 'lossless source files,' they mean PCM. It's the bedrock of pro audio, even if the term itself stays behind the scenes, rarely appearing on file icons or export menus.

Sample Rate and Bit Depth: The Two Numbers That Define PCM Quality

Two numbers define the quality of any PCM audio file: sample rate and bit depth. You see them everywhere in audio software, and understanding what they mean is the key to avoiding expensive mistakes in your projects. Sample rate, measured in Hertz (Hz), tells you how many snapshots of the audio signal are taken per second. According to the Nyquist theorem, you need a sample rate at least double the highest frequency you want to record. Since human hearing maxes out around 20,000 Hz, the 44,100 Hz CD standard was born, giving a safe margin over the 40,000 Hz minimum. You'll see other common rates: 44,100 Hz (CD, streaming), 48,000 Hz (video production), 88,200 Hz and 96,000 Hz (high-res audio), and even 192,000 Hz for archival work. Using 48,000 Hz for a podcast isn't a mistake, but you'll have to resample it later if you want to burn it to a CD alongside other 44,100 Hz tracks. Bit depth is all about precision. It determines how many possible volume levels each sample can have. A 16-bit file offers 65,536 steps. A 24-bit file offers a staggering 16,777,216 steps. This translates directly to dynamic range—the difference between the quietest and loudest possible sounds. 16-bit gives you about 96 dB of range; 24-bit provides 144 dB. That extra headroom is why pros record at 24-bit: you can capture quiet sounds without cranking the gain and risking noise, then deliver the final product at 16-bit. Don't make the common mistake of carelessly converting a 48,000 Hz / 24-bit file down to 44,100 Hz / 16-bit. The quality of the sample rate conversion (SRC) algorithm is everything. A bad algorithm will litter your audio with nasty aliasing artifacts. Anyone who has wrestled with a grainy, phasey downsample knows this pain. Professional tools like iZotope RX or Adobe Audition use high-quality SRC by default. CocoConvert applies standard algorithms that are perfectly fine for web and podcasting, but I'll be blunt: if you're prepping a commercial music master, you need to use dedicated mastering software. No exceptions.

WAV vs. AIFF: Two Containers, One Codec

The two main containers for PCM are WAV and AIFF. WAV, a Microsoft and IBM creation, came along with Windows 3.1 in 1991. Apple's AIFF is even older, created in 1988 and based on an earlier Electronic Arts format. Both were built to hold uncompressed PCM audio. For all practical purposes, a 44,100 Hz / 16-bit stereo WAV and its AIFF equivalent are identical in sound because the raw PCM data inside is the same. So what's the difference? It's mostly historical and structural. WAV uses little-endian byte ordering, while AIFF uses big-endian. This mattered back in the days of PowerPC Macs and x86 PCs, but today's software couldn't care less and handles both without issue. The more relevant difference is metadata. WAV has the BWF (Broadcast Wave Format) extension, a powerhouse for film and TV work that embeds critical timecode and scene data. AIFF has its own metadata chunks, and a variant called AIFF-C can technically hold compressed audio, though you'll almost never see that in the wild. Here's the practical breakdown: Windows apps lean towards WAV. Apple's Logic Pro defaults to AIFF. Pro video tools like Premiere Pro and DaVinci Resolve happily accept both. My advice? If you're sending audio to a client and you're not sure what they use, send a WAV. It's the closest thing to a universal standard. Just remember, one isn't 'better' than the other in terms of sound quality when they're both holding the same linear PCM data.

Where PCM Audio Actually Lives in Your Workflow

You might be surprised how often you're already working with PCM audio. It's the invisible workhorse of most media workflows. Knowing where it lives helps you decide when to convert and, just as importantly, when to leave things alone. In video production, the audio inside professional video files like MXF, ProRes, and DNxHD is almost always 48,000 Hz / 24-bit PCM. That final export from Premiere Pro (File > Export > Media) is a critical moment: the editor chooses whether to keep the pristine PCM or compress it to something like AAC. For major broadcasters like the BBC (under R/68) or streamers like Netflix, there's no choice—their delivery specs demand PCM. In the music studio, everything is PCM. DAWs like Ableton Live, Logic Pro, and Pro Tools live and breathe it. Ableton Live 11, for instance, defaults to recording in 32-bit float WAV format at your project's sample rate (set in Preferences > Audio). This special PCM variant uses floating-point numbers, which gives engineers massive headroom during mixing and prevents clipping. Once the mix is done, those files are converted down to standard 16-bit or 24-bit integer PCM for the final release. For long-term storage, PCM is king. Archives, libraries, and broadcasters choose PCM WAV or AIFF because it's future-proof. There's no proprietary codec that can become obsolete. An MP3 made in 2001 might sound different from one made with a 2024 encoder, but a PCM file from 1991 is bit-for-bit identical today. That's why the Library of Congress puts its trust in PCM WAV for audio preservation. Even on the consumer side, it's there. If you rip a CD using the 'AIFF Encoder' in Apple's Music.app, you get PCM AIFF files. If you use Windows Media Player to rip to WAV, you get PCM WAV. In both cases, you've created a perfect, lossless copy of the disc.

Converting PCM Audio: What Changes and What Doesn't

Switching between PCM formats, like WAV to AIFF, is just changing the box the audio comes in. The audio data itself is untouched. It's a completely lossless operation, whether you use CocoConvert or any other tool. You can flip a file from WAV to AIFF and back a thousand times with zero quality loss. Going from PCM to a compressed format like MP3, AAC, or OGG Vorbis is a one-way street. It's a lossy process. The encoder uses psychoacoustic models to throw away data it assumes you won't miss. At high bitrates (like 320 kbps MP3 or 256 kbps AAC), most people won't hear a difference. But at lower bitrates, 128 kbps and under, you'll start to hear ugly artifacts, especially on sharp sounds like cymbals. That damage is permanent. You can't get it back. Converting that MP3 back to a WAV file just gives you a big file that contains the same damaged audio. Yes, CocoConvert can convert an MP3 back to a WAV. The operation is technically valid and the file will work. But let's be clear: this does not improve the quality. The audio quality is still limited by the original MP3. You're just putting 128 kbps quality audio into a much larger file. The only good reason to do this is for compatibility, if you're working with old software or hardware that demands WAV files. Don't ever do it thinking you're 'recovering' lost quality. When you're changing the sample rate or bit depth of a PCM file, the quality of the conversion software becomes critical. Going from 96,000 Hz down to 44,100 Hz, for example, requires a low-pass filter to prevent aliasing, and different tools do this with varying degrees of success. For anything that requires critical listening, you really should use dedicated audio software with a top-tier SRC algorithm.

PCM Variants You'll Encounter: Float, LPCM, and DPCM

Plain vanilla PCM isn't the only flavor out there. You'll run into a few variations, and it's good to know what they are and when they matter. The most important variant for modern producers is 32-bit float PCM (also called IEEE 754 float). Instead of integers, it stores sample values as floating-point numbers. This is a huge deal inside a DAW like Ableton Live, Pro Tools, or FL Studio because it allows audio levels to go 'over' the maximum without actually clipping, giving you incredible flexibility during a mix. These files are larger than 24-bit integer PCM (4 bytes per sample vs. 3 bytes), and while most modern software can play them, you'll almost always convert them down to a 24-bit or 16-bit integer file for final delivery. You might see the term LPCM, which stands for Linear PCM. Don't let it throw you; it's just a more specific name for the standard PCM we've been discussing, where the volume steps are all equal. The 'Linear' part is there to distinguish it from logarithmic PCM variants like A-law and μ-law (mu-law) encoding used in telephony. Those are clever compression schemes used to squeeze human speech into tiny 8-bit samples. If you ever get a strange .au file or a WAV from a phone system, it might be one of these. You'll need to convert it to standard linear PCM WAV before you can edit it, which is something CocoConvert can handle. Finally, there's DPCM and its cousin ADPCM. These are lightweight compression formats that store the *difference* between audio samples instead of the full value. You'll find ADPCM in some video game audio and older multimedia files. Even though it has 'PCM' in the name, it's not lossless. IMA ADPCM WAV files, for example, will sound noticeably less crisp than a true linear PCM file at the same sample rate and bit depth.

Choosing the Right PCM Settings for Common Use Cases

Bigger numbers aren't always better. Choosing the right PCM settings is about being smart: match your format to your final destination and maintain quality where it counts. For music distribution to streaming platforms (Spotify, Apple Music, Tidal): Stick to 44,100 Hz. Deliver a 16-bit stereo WAV for standard delivery, or a 44,100 Hz / 24-bit WAV if you're targeting a hi-res tier. Sending Spotify a 96,000 Hz file is pointless; their internal encoding pipeline accepts up to 44,100 Hz / 16-bit, so you gain nothing. Apple Music's Lossless tier is more flexible, accepting 24-bit files at either 44,100 Hz or 48,000 Hz. For video production and broadcast: This one's easy. Use 48,000 Hz / 24-bit PCM. Consistently. It's the global standard. By working in 48k from start to finish, you avoid any nasty sample rate conversions when your audio is finally synced with the video, which almost universally runs at 48,000 Hz. For podcasting and voice content: 44,100 Hz / 16-bit WAV is plenty. Your host is just going to re-encode it to MP3 or AAC anyway, so your job is to give their encoder the best possible source material to work with. Recording a podcast at 192,000 Hz is pure overkill and offers zero benefit to the listener. For archival and preservation: 96,000 Hz / 24-bit PCM WAV hits the sweet spot. It captures a huge amount of detail while remaining practical from a storage perspective. The Library of Congress and most national archives specify this range for a reason. For everyday conversions—swapping WAV to AIFF, adjusting sample rate, or creating compressed files for delivery—CocoConvert gets the job done right in your browser. No installs needed. But for highly specialized work, like mastering-grade SRC or batch processing broadcast files with BWF metadata preservation, you need to reach for the professional's toolkit: iZotope RX or Adobe Audition. Part of being a pro is knowing which tool to use for the job, and understanding the limits of any tool, including this one.