Music Library Doctor
Blog · Audiophile

Fake FLAC is the audiophile problem of 2026

Plex, Roon, and Navidrome trust the wrapper. Fake FLACs (lossy audio in lossless containers) play back as if they were genuinely lossless — and they're spreading.

The problem

FLAC is a lossless container. The audio inside it can be anything — including a 128 kbps MP3 source that someone transcoded to FLAC for storage. The wrapper is genuinely lossless; the audio is genuinely not. Plex, Roon, Navidrome, Subsonic, Jellyfin — every modern media server reads the container, sees "FLAC", lights up the lossless badge, and serves the file. The audiophile workflow trusts that badge. The audio doesn't deserve the trust.

How Music Library Doctor does it

  1. 1 Understand the math. A lossless container preserves whatever audio you put into it. If the source was a 128 kbps MP3, the FLAC contains exactly that information — no more. The container's losslessness only refers to its compression of whatever it received.
  2. 2 Identify the entry points. Fake FLACs sneak in through bulk archive rescues, torrented "lossless" rips of dubious provenance, well-meaning friends transcoding their MP3 collections to FLAC for sharing, and ripping software that defaults to lossy intermediate steps.
  3. 3 Look at the spectrum, not the format. Real lossless rips show full-spectrum content out to the Nyquist limit (22 kHz for 44.1 kHz audio). Fake FLACs from lossy sources show a sharp cliff at ~16 kHz, exactly matching the original lossy bitrate.
  4. 4 Audit at library scale. Spek for spot checks; FFT-based library scoring (like Music Library Doctor's Audio Quality Score) for the whole collection at once.
  5. 5 Decide on a policy. Some audiophiles delete fake FLACs and replace. Others tag them as "lossy source" and keep them as the only available copy. Either is defensible; doing nothing because you trust the badge is not.

Supported today

Rekordbox · Serato DJ · VirtualDJ (incl. Favorite Folders) on Windows 10+ and macOS (Apple Silicon + Intel).

Why native integration matters

Media servers don't audit because that's not what they're designed to do. They read tags, parse containers, and serve files — and that's the right scope for a media server. The audit step has to happen at the file system layer, and it has to happen at library scale. Music Library Doctor's FFT pipeline decodes each file and inspects the actual signal, regardless of container format. It runs on the file system directly, so Plex, Roon, Navidrome, and any other media server don't need plugins or integrations — clean up the files, the server rescans, the badges now mean what they say.

Frequently asked questions

Doesn't a fake FLAC at least sound lossless on lossless playback?

It sounds like its source. If the source was 128 kbps MP3, the playback sounds like a 128 kbps MP3 — the FLAC container can't add information that isn't there. The lossless badge is misleading you about what you're hearing.

Why would anyone make a fake FLAC?

Sometimes deception (torrent uploads passing off lossy as lossless). Sometimes well-meaning archiving (someone transcoding their MP3 collection to FLAC because they think it'll "preserve" it). The result is the same either way — disk space wasted, false lossless indicator.

Can I tell from listening?

Sometimes, on accurate playback gear. The high-frequency cliff at 16 kHz is audible in cymbals, air, and fast transients on a good system. But systematic library auditing is more reliable than per-track listening for a large collection.

What about high-bitrate MP3 to FLAC (320 kbps → FLAC)?

Same principle — the FLAC contains what the source contained. A 320 kbps MP3 transcoded to FLAC is closer to lossless than a 128 kbps transcoded, but it's still lossy audio in a lossless container. FFT scoring would show a cliff at the higher frequency the 320 encoder allowed.

Get your library in shape in minutes

Free tier covers detection and viewing. Lifetime access is $49 — $19 for the first 100 DJs.

Related guides