The podcast voicemail WAV myth

By Jeff Sarris · 2026-08-04

Some podcast voicemail tools advertise WAV downloads as a quality feature, and it sounds convincing: WAV is what studios use, so WAV must be better. For listener voicemails recorded in a browser, it isn't. Here's what's actually happening.

How a browser records your listener

Every tool in this category, mine included, records through the browser's MediaRecorder API. The moment your listener stops talking, their browser has already compressed the audio: Chrome and Firefox capture Opus, Safari captures AAC. That compressed capture is the master. There is no uncompressed original sitting anywhere.

So what is a WAV export, then?

It's the same compressed capture, decoded and rewrapped in a container about ten times the size. Nothing lost, nothing gained. It's the audio equivalent of photocopying a photocopy onto heavier paper.

What actually limits quality

• The microphone: a phone held at arm's length, laptop mic in a kitchen. This is 90% of what you hear.
• The room: echo and background noise survive every format equally.
• The connection: some tools reduce capture quality on slow networks.

And here's the kicker: your finished episode ships as compressed audio anyway. Every podcast app your listeners use plays AAC or MP3. A voicemail that stayed compressed from capture to episode loses nothing a listener could ever hear.

What to look for instead

Judge a voicemail tool on the things that change your week: does the download drop straight into your editor (Call.Show gives you an .m4a, which every editor opens), does every message arrive transcribed so you can pick messages by reading, and did the listener consent to being played on air. If a workflow of yours strictly requires a .wav container, any editor converts the file in seconds with nothing lost from the source.