FLAC vs ALAC vs WavPack: Which Lossless Format in 2026?

Updated October 2026: Spotify Lossless now streams FLAC up to 24-bit/44.1 kHz in 50+ markets; FLAC 1.5.0 and WavPack 5.8–5.9 add multithreaded encoding; new WavPack vs FLAC and ALAC vs FLAC head-to-heads and FAQ.

Why this matters

If you build an OTT service, a music app, a post-production tool, or any product that stores original audio before it gets compressed for delivery, you will have to choose a format for the high-quality master — and the lossless family is where that choice lives. This article is written for a product manager, founder, or operations lead with no audio background: by the end you will understand what "lossless" actually means, how FLAC, ALAC, and WavPack differ, why they all come out roughly the same size, and exactly when your product needs lossless instead of the cheaper lossy codecs. Every spec number here traces back to its controlling document — for FLAC, that is now a formal IETF standard — not a secondhand blog summary.

FLAC vs ALAC vs WavPack: the short answer

FLAC, ALAC and WavPack are all lossless: each decodes back to the original audio bit for bit, so none of them sounds better than another. FLAC is the open IETF standard (RFC 9639) used by Tidal, Qobuz, Amazon Music and, since September 2025, Spotify; ALAC (Apple Lossless Audio Codec) is the format of iPhone, Mac and Apple Music; WavPack is the archivist’s choice, adding 32-bit float, DSD and a hybrid lossy-plus-correction mode. FLAC and WavPack land within about one percent of each other on file size, with ALAC a little larger. At CD quality (1,411 kbit/s of stereo PCM) a FLAC file at about 61% of the original works out to roughly 860 kbit/s, or about 390 MB per hour of audio. Pick by where the file must play, not by quality.

What "lossless" really means

A codec is an agreed method for compressing sound on one end of a link and reconstructing it on the other. Most codecs a video product uses — AAC, Opus, MP3 — are lossy: they permanently discard parts of the signal a listener is unlikely to notice, and the decoded audio is similar to the original but not identical. A lossless codec makes a different promise. It compresses the audio, and when you decode it you get back the original data exactly, bit for bit, with nothing missing. The trade is right there in the name: you lose nothing, but you save less space.

The numbers make the trade concrete. A music codec like Opus, covered in the Opus article, can carry a stereo song at 128 kbit/s. The same song stored losslessly typically runs around 700–900 kbit/s — five to seven times larger. So lossless is never the cheap option. It is the faithful option, and you pay for fidelity in bytes.

How does a lossless codec save any space at all if it throws nothing away? It exploits predictability. Real audio is not random: the next sample is usually close to the last few. A lossless encoder builds a small mathematical model that predicts each upcoming sample from the ones before it, then stores only the tiny difference between the prediction and the truth — a number that is almost always much smaller than the original sample, and therefore needs fewer bits. Decode the differences, run the same model forward, and the original returns exactly. This idea — predict, store the error, reverse it — is the engine inside all three formats below. The same family of ideas appears in how audio compression works, and the raw uncompressed starting point is the PCM described in what is digital audio.

Figure 1. The trade in one picture: lossy is small but approximate; lossless is larger but bit-exact.

FLAC: the open standard everyone can use

FLAC — the Free Lossless Audio Codec — is the most widely deployed lossless format and the one with the most open governance. For most of its life it was defined only by documentation on the Xiph.org website, but in December 2024 it became a formal internet standard, IETF RFC 9639, on the Standards Track (RFC 9639, December 2024). That matters for a product team: a codec defined by a stable, citable standard is a codec you can build on without fear of it shifting under you.

FLAC's reach is wide. It codes from 1 to 8 channels, sample rates from 1 Hz up to 1,048,575 Hz, and integer bit depths from 4 to 32 bits per sample — far more than any real recording needs, which is the point: it will never be the format that can't hold your audio (RFC 9639, §1). Internally it works in four steps. First it cuts the stream into short blocks of up to 65,535 samples. Then, for stereo, it removes redundancy between the two channels by storing a mid-and-side representation instead of plain left-and-right — because the two channels of a stereo recording are usually very similar, the difference between them is small and cheap to store (RFC 9639, §4.2). Next it runs the predictor described above, using either one of five fixed formulas or a custom linear-prediction model with up to 32 coefficients. Finally it packs the leftover prediction errors with Rice coding, an entropy method tuned for streams of small numbers with the occasional outlier (RFC 9639, §4.4).

Two practical features make FLAC the safe default. It carries an MD5 checksum of the original audio in its header, so a decoder can prove the file is intact — useful for an archive you will trust for a decade (RFC 9639, §8.2). And it defines a streamable subset: each frame carries enough information that a player can start decoding from the middle of a stream without reading the file header, which is exactly what an HTTP streaming service needs. That is why FLAC is the codec behind Tidal (which dropped the proprietary MQA format for open FLAC), Qobuz, and Amazon Music, all delivering up to 24-bit / 192 kHz today. Spotify joined them in September 2025: its Lossless option streams FLAC at up to 24-bit / 44.1 kHz to Premium subscribers, available in more than 50 markets by October 2025 (Spotify Newsroom, 2025). On the tooling side, the reference encoder libFLAC 1.5.0 (February 2025) added multithreaded encoding, which cuts the time to convert a large back catalog on a many-core server (Xiph.Org, 2025).

ALAC: Apple's lossless, for Apple's world

ALAC stands for Apple Lossless Audio Codec (Apple’s apps simply call it “Apple Lossless”). It is Apple's own answer to FLAC, and for years the reason it existed was simple: Apple's players didn't decode FLAC, so the Apple ecosystem needed its own lossless format. ALAC compresses to a bit-for-bit identical copy of the original, just like FLAC, and supports 16-, 20-, 24-, and 32-bit audio in 1 to 8 channels (Apple ALAC project). Apple released the encoder and decoder as open source under the Apache 2.0 license in October 2011, so ALAC is no longer locked to Apple's platforms — but in practice it still lives almost entirely inside them.

The defining technical fact for a product team is the container. ALAC normally lives inside an MP4 / .m4a file, the same ISO base-media container that holds AAC, using a small block of setup data Apple calls a "magic cookie" (Apple ALAC project). Containers are covered in audio in containers. This is why ALAC is the codec behind Apple Music Lossless and Hi-Res Lossless, which stream up to 24-bit / 192 kHz to Apple devices at no extra subscription cost. Two delivery limits matter when you plan a lossless tier: per Apple, Bluetooth connections are not lossless (most AirPods use the AAC Bluetooth codec, while AirPods Max with USB-C can play lossless over a USB-C cable), and an iPhone or iPad needs an external DAC for sample rates above 48 kHz (Apple Support, 2026). If your product has to match Apple Music’s lossless tier or hand files to Apple’s Music app, ALAC is the format your delivery path will speak; plain playback on iPhone and Mac also works with FLAC.

WavPack: the flexible one with a hybrid trick

WavPack, created by David Bryant and shipping since 1998, is the least famous of the three and the most versatile. In its normal mode it is an ordinary lossless codec like the other two. Its signature feature is hybrid mode, which no mainstream rival offers: instead of one file, WavPack can produce two — a small, self-contained lossy file (.wv) that plays fine on its own, plus a correction file (.wvc) that, added back, restores the full lossless original (WavPack documentation, 2024).

That split is genuinely useful in a production pipeline. You can ship or stream the lightweight .wv for everyday playback and keep the .wvc correction file in the archive, so you hold a perfect master without storing a separate full-size lossless copy. WavPack also handles more exotic inputs than the others — including 32-bit floating-point audio, the format modern editing tools capture in — and it can also store DSD, the 1-bit format of SACD-style masters. That is why it shows up in mastering and archival workflows more than in consumer streaming. The project is actively maintained: WavPack 5.8.0 (January 2025) made multithreaded encoding the default in its command-line tools, and 5.9.0 (January 2026) is the current release (WavPack changelog, 2026).

They're all lossless — so how do you choose?

Here is the fact that surprises people: because all three are mathematically lossless, they all sound exactly the same — identical to the original and identical to each other. There is no "better-sounding" lossless codec, only smaller or larger files and faster or slower decoding. The Hydrogenaudio community’s lossless comparison puts FLAC and WavPack within a fraction of a percent of each other on file size (about 61% of the original CD audio for both in its test set), with ALAC slightly larger than either.

Because the audio is the same, the decision is driven by where the file has to play, not by quality. Matching Apple Music or feeding libraries in Apple’s Music app? Use ALAC. Building an open, cross-platform music tier or a hi-res streaming catalog? Use FLAC — it is the de-facto industry standard and the only one defined by a public RFC. Need 32-bit float support or the hybrid lossy-plus-correction workflow for an archive? Use WavPack.

WavPack vs FLAC and ALAC vs FLAC: head to head

The audio is identical in every pair; the differences are compatibility, extra features and tooling. This table is what decides the format in a real product.

WavPack vs FLAC: choose FLAC unless you need one of WavPack’s three extras — 32-bit float, DSD, or the hybrid .wv + .wvc split. Size and quality are a wash. ALAC vs FLAC: choose ALAC when the library must live in Apple’s Music app or match Apple Music exactly; Apple devices themselves play FLAC, so for everything else FLAC opens more doors and saves you a second catalog. Browser figures are from caniuse (2026); service lists from the vendors.

Converting between them is also lossless. Because each format decodes to the same PCM, you can move a library from ALAC to FLAC (or back) without losing anything, for example ffmpeg -i track.m4a -c:a flac track.flac. Keep the tags and artwork in mind: they map between formats but are worth checking on a sample before a bulk run. One trap: converting a WavPack 32-bit float master to FLAC or ALAC forces a conversion to integer samples, so that step is no longer bit-exact.

Common mistake: shipping lossless to listeners who can't hear the difference

The most expensive lossless error is using it for ordinary delivery. A lossless stream is five to seven times the size of a transparent lossy stream, and on phone speakers, laptop speakers, or typical earbuds, listeners cannot tell the two apart in a blind test. Paying for lossless bandwidth to every viewer of a video product is a cost with no perceptible benefit. The right pattern is to keep your masters lossless and deliver lossy — encode the high-quality lossless master once, then transcode to AAC or Opus for streaming. Reserve lossless delivery for a deliberate, opt-in audiophile or music tier, where the user has chosen it and often has the hardware to benefit.

FAQ

Is WavPack better than FLAC?

Not in sound: both are lossless and decode to identical audio, and their file sizes differ by well under one percent. WavPack is better only for 32-bit float masters, DSD, or its hybrid lossy-plus-correction mode; FLAC is better for compatibility.

Which is better, ALAC or FLAC?

Neither sounds better, because both are bit-exact. ALAC is the right choice for Apple Music parity and Apple Music app libraries; FLAC is the right choice for Android, Windows, web browsers and services like Tidal, Qobuz, Amazon Music and Spotify.

What is ALAC audio? What does ALAC stand for?

ALAC stands for Apple Lossless Audio Codec. It is Apple’s lossless audio format, usually stored in an .m4a (MP4) file, and the codec behind Apple Music Lossless. See also the ALAC glossary entry.

What is WavPack?

WavPack is an open-source lossless audio codec that produces .wv files and, in hybrid mode, an extra .wvc correction file that turns a small lossy file back into the lossless original. Short definition: WavPack glossary entry.

Does Spotify use FLAC?

Yes. Since September 2025 Spotify Premium’s Lossless setting streams FLAC at up to 24-bit / 44.1 kHz, replacing the Ogg Vorbis stream for users who switch it on.

Can I convert ALAC to FLAC without losing quality?

Yes. ALAC and FLAC are both lossless, so decoding one and encoding the other keeps every sample; only metadata needs checking.

Is FLAC an official standard?

Yes. FLAC was published as IETF RFC 9639 on the Standards Track in December 2024. A short definition is in the FLAC glossary entry.

Where Fora Soft fits in

In the video products we build — OTT and internet-TV platforms, e-learning systems, and media tools — the lossless decision usually shows up at the storage layer rather than the delivery layer. A streaming service keeps a lossless or near-lossless mezzanine (our OTT and IPTV platform development team builds that storage tier into the ingest pipeline) so it can re-encode to new delivery codecs later without quality loss, while shipping AAC or Opus to viewers. A music-adjacent app that wants to match Apple Music's lossless tier has to speak ALAC inside MP4, while a cross-platform catalog leans on FLAC. Getting the master format right at the start saves a painful, lossy-by-accident re-encode of an entire library later. Our music software development team builds hi-res and lossless tiers with FLAC and ALAC delivery, and our audio and video processing development work sets up the lossless mezzanine and the AAC and Opus transcode ladder behind it.

The book

Audio for Video: A Complete Guide to Sound in Video Products: From PCM and Codecs to Loudness, Accessibility, and Real-Time Voice Processing

This volume starts where the master does — PCM, sample rate, bit depth, channel layouts — so the 32-bit float files WavPack was built to swallow and the 24-bit/192 kHz tier Apple Music ships stop being spec-sheet lines and become numbers you can size storage against. It then walks the lossy side of the same fork in detail, AAC and Opus chapter by chapter, which is the half of the keep-masters-lossless, deliver-lossy rule you will actually be tuning every week. Written by Nikolay Sapunov, CEO at Fora Soft.

Read it on Amazon →Kindle & paperback · Fora Soft Video Engineering Handbook

See our case studies

References

1. IETF RFC 9639 — "Free Lossless Audio Codec (FLAC)", M.Q.C. van Beurden & A. Weaver, Standards Track, December 2024, ISSN 2070-1721. The controlling specification for FLAC. Supports: 1–8 channels, 1–1,048,575 Hz, 4–32 bits; four-stage encode (blocking §4, interchannel decorrelation §4.2, prediction §4.3, Rice residual coding §4.4); streamable subset §7; MD5 checksum in STREAMINFO §8.2. https://www.rfc-editor.org/rfc/rfc9639.html
2. Apple Lossless Audio Codec project (macOSForge / GitHub), Apple Inc., source released under Apache License 2.0, October 2011. Supports: bit-for-bit identical decode, MP4/M4A "magic cookie" carriage, 16/20/24/32-bit, 1–8 channels. https://macosforge.github.io/alac/
3. WavPack 5 Library Documentation, David Bryant, February 2024, and WavPack 4 & 5 File Format, April 2020. Supports: hybrid mode (.wv lossy + .wvc correction), 8/16/24/32-bit integer and 32-bit float PCM. https://www.wavpack.com/WavPack5LibraryDoc.pdf
4. Hydrogenaudio Knowledgebase — Lossless comparison (wiki.hydrogenaudio.org). Independent community benchmark: FLAC ≈ 61.05% and WavPack ≈ 60.83% of original size; ALAC slightly larger than both. Used as a community source for the relative-size claim only; absolute spec facts above defer to the standards documents.
5. Xiph.Org — "FLAC 1.5.0 released", 11 February 2025. Supports: multithreaded encoding in the reference encoder. https://www.xiph.org/flac/2025/02/11/flac-1-5-0-released.html
6. What Hi-Fi? — Hi-res music streaming services compared (2026). Supports 2026 deployment facts: Apple Music Lossless/Hi-Res uses ALAC up to 24-bit/192 kHz; Tidal, Qobuz, and Amazon Music use FLAC up to 24-bit/192 kHz; Tidal replaced MQA with FLAC. https://www.whathifi.com/advice/hi-res-music-streaming-services-compared
7. MP4 Registration Authority — registered codecs. ISO base media file format (ISO/IEC 14496-12) sample-entry codes alac (Apple Lossless) and fLaC (FLAC in MP4, with its dfLa configuration box). https://mp4ra.org/registered-types/codecs
8. Apple ALAC source repository (GitHub, macosforge/alac). Supports ALAC channel-layout and bit-depth detail (1–8 channels, 16/20/24/32-bit) and the Apache 2.0 license. https://github.com/macosforge/alac
9. Spotify Newsroom — "Lossless listening arrives on Spotify Premium", 10 September 2025 (updated October 2025). Supports: FLAC up to 24-bit/44.1 kHz, Premium only, 50+ markets. https://newsroom.spotify.com/2025-09-10/lossless-listening-arrives-on-spotify-premium-with-a-richer-more-detailed-listening-experience/
10. Apple Support — "About lossless audio in Apple Music" (checked October 2026). Supports: Bluetooth is not lossless; AirPods Max (USB-C) lossless over a USB-C cable; external DAC above 48 kHz on iPhone and iPad. https://support.apple.com/en-us/118295
11. WavPack changelog, David Bryant. Supports: 5.8.0 (27 January 2025) multithreading by default; 5.9.0 (16 January 2026); DSD handling. https://www.wavpack.com/changelog.txt
12. Can I use — FLAC audio format (checked October 2026). Supports: FLAC playback in Chrome, Edge, Firefox and Safari, ≈97% global support. https://caniuse.com/flac