“We Cannot Play This Audio File Right Now” — What It Really Means

It’s a codec problem, not a temporary one

Despite the “right now,” this message has nothing to do with server load, your connection, or timing. Gmail displays it whenever the audio inside the attachment is encoded with a codec your browser cannot decode. The file is perfectly valid — Chrome simply doesn’t know how to turn it into sound.

This is almost always a voicemail or call recording. Phone systems and VoIP providers compress audio with telephony codecs that were never meant for web browsers. When that file lands in your inbox, Gmail recognises it as audio, shows a player, and then fails the moment you press play.

The formats that trigger it

You’ll usually see this error on files with one of these encodings — even when the file extension is an innocent-looking .wav:

The fix: decode it inside Gmail

Gmail Audio Player is a Chrome extension that adds the missing codec support directly inside Gmail. It detects the attachment, decodes it locally in your browser, and replaces the broken player with one that actually works — no download, no desktop app, no uploads.

Install it, reopen the email, and the same attachment that showed the error will play inline — with a scrubber, speed control, and optional AI transcription on paid plans.

What won’t fix it

Before you waste time: clearing your cache, using incognito, switching browsers, updating Chrome, or asking the sender to resend will not help. None of those change the codec inside the file. The only fixes are opening the file in a desktop app that includes the codec — or adding the codec to Gmail itself, which is exactly what this extension does.

Frequently asked questions

Related fixes