Convert FLAC to WAV

Converting FLAC to WAV decompresses lossless audio into plain PCM for software that refuses to read FLAC — samplers, older editors, game engines, analysis tools. Nothing is lost to compression, the file roughly doubles in size, and it is written as 16-bit. The decoding happens in your browser, not on a server.

  • Where it runs In your browser. The file is never uploaded.
  • Lossless Nothing is discarded. The WAV holds exactly what the FLAC held.
  • File size limit Up to 100 MB per file, free, without an account.

Up to 100 files at once. Mixed formats are fine.

This is decompression, and the audio is unchanged by it

FLAC stores the same samples a WAV does, packed more efficiently. The encoder predicted each sample from the ones before it and wrote down the difference; the decoder runs that in reverse and reconstructs the original stream exactly. There is no approximation anywhere in the process and no setting that could introduce one.

So the useful way to think about this conversion is unzipping rather than converting. The recording that comes out is the recording that went in, occupying about twice the disk it did a moment ago, in a container that has been the lowest common denominator of digital audio since 1991.

The software that still will not open a FLAC

The list is shorter than it was and it is not empty. Hardware samplers and groove boxes generally implement WAV and nothing else, because a FLAC decoder is code and firmware is expensive. Older DAW versions, some game engines and a great deal of embedded and automotive software take the same view.

The other large group is scientific and speech tooling. Forced aligners, transcription pipelines, acoustic analysis packages and a good deal of research code read PCM directly out of a WAV header and stop there — not because the audio is better, but because supporting one format removes a dependency and a class of bugs. The requirement is about their code, not your recording.

Before converting, try opening the FLAC

The most common version of this task is unnecessary. Audacity, Reaper, Logic Pro, Ableton Live, foobar2000 and VLC all read FLAC without help, and have for years. People convert because a decade-old forum answer said to, or because one program in a chain complained and they assumed the rest would.

Ten seconds of testing saves a doubled library. Drag the FLAC into the application that is actually going to use it. If it opens, you are finished; if it refuses, come back and convert only the files that program needs rather than the whole collection.

The WAV is written as 16-bit, whatever the FLAC held

FLAC records the bit depth of its source and can carry 24-bit audio. The WAV produced here is 16-bit PCM. For a CD rip, a download or any 16-bit master that changes nothing at all, and the conversion is bit-exact.

For a 24-bit studio FLAC it is a real reduction, and it is the one thing on this page worth checking before a bulk conversion. If the destination is a sampler, a game engine or a transcription tool, 16-bit is what it wanted anyway. If it is a mastering session where the extra headroom is the point, decode with a desktop tool that preserves the depth and keep the FLAC as the master either way.

Roughly double the bytes, and where they come from

Uncompressed CD-quality stereo costs 176,400 bytes a second — about 10 MB a minute — because every sample is written out as a plain number with no attempt to save space. FLAC of the same material typically lands at 50 to 60 percent of that, so decoding roughly doubles what is on disk.

How exactly it doubles depends on the recording rather than on any setting. Sparse, quiet material compressed hard and therefore expands more; a dense, loud master that only reached 70 percent expands less. Nothing about the WAV can be tuned — it has no quality control because it performs no compression.

The tag block has nowhere to land

FLAC files in a library are usually well tagged, with title, artist, album, track number and embedded artwork. WAV offers only an optional INFO chunk, which has no place for a picture and which most software neither writes nor reads, so a converted library arrives as a folder of files identified by their names.

That is why this conversion should be aimed at a task and not at a collection. Decode the tracks a sampler or an analysis tool needs, use them, and keep the FLACs as the thing that holds the library together. Converting a tagged FLAC library into an untagged WAV one is a step nobody enjoys undoing.

Leaving the MD5 behind

A FLAC stream header carries an MD5 of the decoded audio, written at encode time, which lets a decoder years later verify that what it reconstructs is what was originally encoded. It is the quiet feature that makes FLAC an archive format rather than a small copy.

A WAV has nothing comparable. A WAV with a corrupted block is still a structurally valid WAV and will play the corruption without complaint. Nothing is broken by the conversion — the verification does not exist on the other side, which is another reason the FLAC is the copy to keep.

Going back to FLAC when the work is done

The return trip is exact for 16-bit material: encoding the WAV back to FLAC yields the same samples the first FLAC held, because neither direction discards anything. That makes WAV a perfectly safe working format in the middle of a chain, which is precisely what it was designed to be.

The tags do not make the return trip, since the WAV never held any. If the file is going back into a library, re-tag it, or keep the original FLAC and treat the WAV as scratch — the second option is nearly always less work.

Batch limits, in FLAC minutes rather than megabytes

A hundred files per drop, 100 MB per file. Because FLAC is already compressed, that ceiling corresponds to roughly seventeen to twenty minutes of music per track, which covers songs and most classical movements and stops short of a single-file concert recording.

The decoding is cheap — no analysis, no encoder, only prediction run backwards — so a batch is quick. Watch the total rather than the count: a hundred tracks decoding to WAV is several gigabytes being assembled inside a browser tab, and it is worth converting in two passes rather than one.

How to decode a FLAC into a WAV

  1. Drop your FLAC files onto this page, or click to choose them.
  2. Each is decoded to uncompressed 16-bit PCM inside your browser.
  3. Download the WAV, or take the set together as a ZIP.

FLAC against WAV: compressed lossless against raw samples

FLAC compared with WAV
FLACWAV
Full nameFree Lossless Audio CodecWaveform Audio
File extension.flac.wav, .wave
Media typeaudio/flacaudio/wav
CompressionLossless — nothing is discardedUncompressed
First published20011991
Published byXiph.OrgMicrosoft
SpecificationRFC 9639RIFF WAVE
LicensingOpen standardPublished, not standardised
Standing todayCurrentCurrent
Bit depth3232
Audio channelsup to 8up to 65,535
Opens in a browserEvery browserEvery browser
Considered insteadAIFF, MP3AIFF

What survives

Nothing is discarded. FLAC and WAV both store their content losslessly, so the conversion is a change of packaging rather than a change of quality, and it can be repeated without accumulating damage.

document properties can cross over — both FLAC and WAV have somewhere to store it.

Opening the result

WAV is a container rather than a single format. What actually plays is the codec inside it — usually PCM — which is why two files with the same extension can behave differently on the same device.

Audacity reads both FLAC and WAV, so there is a way to check the result against the original without a second tool.

File size and quality

WAV stores the samples raw, so the file grows substantially without gaining anything. It is the right direction only when a program on the far side refuses FLAC, which is the usual reason for doing it.

What each format is for

FLAC is Xiph.Org's format, published in 2001. It records 32 bits per channel.

WAV comes from Microsoft and dates from 1991, specified as RIFF WAVE. Audacity, Adobe Audition and Reaper all read it.

FLAC to WAV: the compatibility questions

Does converting FLAC to WAV lose anything?

Not from the compression, because FLAC is lossless and decoding it reproduces the samples exactly. There is one thing to watch: the WAV is written as 16-bit PCM, so a 24-bit FLAC does not come out as 24-bit. For a 16-bit source — CD rips and most music — the audio is identical.

How much bigger will the WAV be?

Roughly double, because FLAC typically compresses to 50 to 60 percent of uncompressed audio. A 350 MB album becomes around 620 MB, and a five-minute track of 28 MB becomes about 53. WAV has no quality setting to adjust; it does not compress at all, which is the whole point of it.

Will my tags and cover art survive?

Effectively not. FLAC has a proper tag block and a picture block; WAV has only an optional INFO chunk that carries no artwork and that most software neither writes nor reads. Expect an untagged file. That is a real loss for a music library and irrelevant if you are decoding in order to feed an editor.

Can I convert back to FLAC afterwards?

Yes, and for 16-bit material the round trip is exact — the FLAC you get back holds the same samples as the one you started with. The tags will not come back, because WAV never held them, so re-tag or keep the original FLAC as the library copy.

Does my software actually need this?

Possibly not. Audacity, Reaper, Logic, Ableton, foobar2000, VLC and every current media player read FLAC directly. The conversion is genuinely required for hardware samplers, older DAW versions, some game engines and embedded players, and a lot of scientific and speech tooling that only implements PCM. Try opening the FLAC first — it takes ten seconds.

Is the file uploaded to decode it?

No. The FLAC is decoded and the WAV assembled inside the browser tab, with no server involved. Files are capped at 100 MB each — around seventeen to twenty minutes of FLAC — and a hundred can be dropped at once.

More about these formats