WAV: Browser Support, Features, Known Issues

What is WAV?

WAV, short for Waveform Audio File Format, is a RIFF-based container that Microsoft and IBM defined to store digital audio. The format usually wraps Linear Pulse Code Modulation samples without compression, the same coding used on audio CDs. The IETF documents the WAV codec registry in RFC 2361, and the standard MIME type is audio/wav.

Which browsers does WAV support?

WAV plays natively in every modern desktop and mobile browser, with Chrome, Edge, Safari, Firefox, Opera, Samsung Internet, and the Android Browser all decoding Linear PCM WAV through the audio element without a plugin. Internet Explorer is the only mainstream browser that never added support.

What are the key features of WAV?

WAV packs several technical traits that explain why archives, recording studios, and Web Audio API engineers still ship the format. The container balances raw audio fidelity, a simple file layout, and broad codec flexibility through the IETF codec registry.

• Uncompressed Linear PCM audio: WAV usually stores Linear Pulse Code Modulation samples with no compression. CD-quality 16-bit stereo at 44.1 kHz uses 1,411 kbit/s, the same data rate audio CDs use, which preserves every sample for archival and mastering work.
• Bit depth and sample rate range: WAV supports 8-bit, 16-bit, 24-bit, and 32-bit float samples at any sample rate from 8 kHz up to 192 kHz. The range covers voicemail through studio masters in a single container.
• Codec flexibility through RFC 2361: WAV can wrap Linear PCM, ADPCM, mu-law, A-law, and IEEE float through the codec registry that IETF RFC 2361 defines. Browsers ship reliable Linear PCM playback only, so re-encode any other codec before serving WAV to the web.
• MIME types and file structure: The standard MIME type is audio/wav, and MDN also recognizes audio/wave, audio/x-wav, and audio/vnd.wave. The file extension is .wav, and the byte layout follows the chunk-based RIFF specification with a fmt header chunk and a data chunk.
• 4 GiB file size ceiling: The RIFF format uses a 32-bit chunk size, which caps a single WAV file at 4 GiB, about 6.7 hours of stereo CD-quality audio. The European Broadcasting Union RF64 extension lifts this limit for long broadcast and archival recordings.
• Royalty-free public spec: The format is publicly documented and royalty-free, which is why the Library of Congress, the British Library, the Macaulay Library, and Indiana University all use WAV as the master archival format for sound preservation.

How do you check if a browser supports WAV?

You can confirm WAV support inside any browser using the HTMLMediaElement.canPlayType() API. The call returns one of three strings for each WAV MIME type alias.

The return values are probably (the browser is sure it can play the file), maybe (likely yes, decoding the file header is needed to confirm), or "" (an empty string, which means no). Test the canonical type audio/wav along with audio/wave and audio/x-wav, since some browsers only recognize a subset of the aliases. The MediaSource.isTypeSupported() API returns the same result for adaptive streaming pipelines.

Paste this snippet into the browser DevTools console to confirm WAV support and the MSE pipeline:

// Run in the DevTools console of any browser to test WAV playback.
const a = document.createElement("audio");
const canWav = a.canPlayType("audio/wav");
const canWave = a.canPlayType("audio/wave");
const canXWav = a.canPlayType("audio/x-wav");

console.log("audio/wav support:", canWav || "no");
console.log("audio/wave support:", canWave || "no");
console.log("audio/x-wav support:", canXWav || "no");

if (window.MediaSource) {
  console.log(
    "MSE WAV (audio/wav):",
    MediaSource.isTypeSupported("audio/wav")
  );
}

If every result is empty, the browser cannot play WAV and the page should fall back to MP3 or AAC inside MP4. The MDN cross-browser audio basics guide recommends pairing two source elements inside the audio tag so the browser picks whichever format it can decode.

What are the known issues with WAV?

WAV is the most reliable choice for short audio clips and archival masters, but several edge cases break in production. The biggest hits are the codec restriction inside the RIFF wrapper, the 4 GiB file size cap, and the bandwidth cost of streaming uncompressed Linear PCM over mobile networks.

• Internet Explorer cannot play WAV in HTML5 audio: IE 5.5 through IE 11 reject the audio/wav MIME type in the audio element, even though IE 9 to 11 support the element itself. Pages that still serve IE traffic need a Flash or Windows Media plugin fallback, both of which fail to load in modern Windows.
• Only Linear PCM is reliable across browsers: Every modern browser plays Linear PCM WAV, but ADPCM, mu-law, A-law, and IEEE-float WAV files fail in many builds because the browsers only register Linear PCM in their codec table. Re-encode any user-uploaded WAV to 16-bit Linear PCM before serving it to an audio element.
• 4 GiB file size ceiling: The 32-bit RIFF chunk size limits a single WAV file to 4 GiB, about 6.7 hours of stereo CD-quality audio. Recording sessions longer than that need RF64, BWF, or W64 wrappers, none of which a browser can play directly.
• Bandwidth cost is high: A 1,411 kbit/s Linear PCM stream burns through about 10.6 MB per minute. Long-form audio over WAV strains mobile data plans and CDN bills, so reserve WAV for short sound effects and master uploads, and stream MP3 or AAC for music and speech.
• Mobile autoplay restrictions: iOS Safari, Chrome for Android, and Firefox for Android block WAV autoplay without a user gesture, the same rule that applies to MP3 and AAC. Wire a tap or click handler before calling play() on the audio element.
• No native gapless looping: The audio element loops on the WAV duration only, which leaves a small gap between iterations. Sample-accurate music loops need the Web Audio API and an AudioBufferSourceNode with the loop flag set true on the decoded WAV buffer.

In my experience, the codec restriction is the most surprising failure. A WAV file that plays in VLC, Audacity, or QuickTime can return an empty canPlayType string if it ships ADPCM or mu-law inside the RIFF wrapper, since the browser only decodes Linear PCM. Always re-encode user-uploaded WAV to 16-bit Linear PCM at 44.1 or 48 kHz before exposing it to an audio element, or feed the bytes to AudioBufferSourceNode through Web Audio API decodeAudioData, which understands the same codec set.

Citations

All WAV version numbers and platform notes in this guide come from these primary sources:

• MDN Web Docs - Media container formats: developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Containers
• MDN Web Docs - Audio codec guide: developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Audio_codecs
• MDN Web Docs - HTML audio element: developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/audio
• MDN Web Docs - Cross-browser audio basics: developer.mozilla.org/en-US/docs/Web/Media/Guides/Audio_and_video_delivery/Cross-browser_audio_basics
• WHATWG HTML Standard - Media: html.spec.whatwg.org/multipage/media.html
• IETF RFC 2361 - WAVE and AVI codec registries: datatracker.ietf.org/doc/html/rfc2361
• Wikipedia - WAV: en.wikipedia.org/wiki/WAV
• Wikipedia - HTML5 audio: en.wikipedia.org/wiki/HTML5_audio
• Wikipedia - Resource Interchange File Format: en.wikipedia.org/wiki/Resource_Interchange_File_Format
• Macaulay Library - Why wave (.wav) files: macaulaylibrary.org/resources/why-wav
• McGill MMSP - Wave file specifications: mmsp.ece.mcgill.ca/Documents/AudioFormats/WAVE/WAVE.html