A WAV file that throws an "unsupported format" error is rarely corrupted. Most apps reject valid WAV variants because they only understand one encoding. The file is fine; the software is picky. This guide walks you through the format codes that cause rejection, shows you how to check which one your file uses, and tells you exactly how to convert it so it opens everywhere.

How the WAV Format Identifies Audio Encoding

Every WAV file carries a fmt chunk with a 16-bit audio format field. That number tells a player or editor what kind of audio data follows. PCM gets the code 1. Everything else is a variant, and that is where the trouble starts.

  • 1 = PCM. Standard uncompressed audio. Every app supports this.
  • 2 = Microsoft ADPCM. A compressed format. Most basic tools cannot decode it.
  • 3 = IEEE float. Floating-point samples, usually 32-bit. High-end editors handle it; many do not.
  • 6 = A-law. Telephony companding. Common in European phone systems.
  • 7 = mu-law. Telephony companding. Common in North American voicemail.
  • 0xFFFE = WAVE_FORMAT_EXTENSIBLE. Used for more than two channels or bit depths above 16. The real encoding hides in a sub-format GUID, and older software never looks that far.

When a program refuses a WAV, it is rejecting a format code other than 1. That is a compatibility gap, not a file error.

Common WAV Variants That Apps Reject

32-Bit Float WAV

Format code 3 means floating-point samples. If your DAW says wav format not supported or daw won't import wav, the float encoding is the culprit. The file is valid. The app just cannot read it.

Wave Format Extensible

Code 0xFFFE appears in WAVs with more than two channels or high bit depths. The outer format field says "extensible," and the real encoding sits in a sub-format GUID inside the chunk. Older or simpler software checks only the outer code and rejects the file, even when the audio is plain PCM underneath.

ADPCM WAV

Microsoft ADPCM (code 2) is compressed. If you have a file where adpcm wav won't open, the codec is the problem. Most basic audio tools decode only PCM. Convert it first.

Telephone and Voicemail Formats

Phone systems produce 8 kHz mu-law or A-law WAVs (codes 7 and 6). Desktop editors lack the codec or expect a higher sample rate and refuse to open them. The file is intact. It uses a format the app does not support.

How to Check the Actual Format Code

Before you try to repair anything, confirm the format code. That tells you whether the file is an unsupported variant or genuinely damaged.

  1. Open a terminal.
  2. Run ffprobe file.wav (use your file name).
  3. Read the codec field. You will see values like pcm_s16le (16-bit PCM), pcm_s24le (24-bit PCM), or pcm_f32le (32-bit float).
  4. pcm_f32le means 32-bit float. adpcm, ulaw, or alaw means a non-PCM codec.

If ffprobe reports pcm_s16le and your app still says "unsupported," the header may be damaged. If it shows a non-PCM codec, the file is a valid variant and needs conversion, not repair.

Converting an Unsupported WAV to a Compatible Format

A WAV with a valid but unusual format is not corrupted. Convert it to 16-bit or 24-bit PCM and it opens everywhere.

Convert to 16-Bit PCM

Run ffmpeg -i input.wav output.wav. ffmpeg writes 16-bit PCM by default. That target works in every DAW and editor. For 24-bit PCM, add -sample_fmt s24le to the command.

Handling Low Sample Rates

Files from telephone systems arrive at 8 kHz. Some editors reject that sample rate even after conversion to PCM. Resample during conversion. The resulting file becomes a standard PCM WAV that any tool can open.

When the File is Actually Corrupted

If ffprobe cannot read the file at all or reports errors, the header may be damaged. Look for a missing or malformed fmt chunk, an incorrect file size, or garbage in the first few bytes. That file needs repair, not conversion. A tool like wav.repair can attempt to recover the audio data.

If the file plays in a media player but your editor refuses it, the format code is almost certainly the issue. Do not assume corruption. Check the format first.