Vocal Remover Vocals BPM Finder BPM Key Finder Key Track ID ID
⚡ 30 min remaining

Get more Cloud Assist minutes
Pricing

Lossless Audio Checker

Check FLAC, WAV or AIFF files for lossy-codec fingerprints. Runs on your device — files never uploaded.

Drop audio files here or click to browse

FLAC, WAV, AIFF, MP3, M4A · processed on your device

Private — processed on your device, never uploaded

How to Check for Lossless Audio

  1. 1 Upload a FLAC, WAV, AIFF, MP3, or M4A file
  2. 2 Read the spectrogram — a sharp horizontal cutoff with nothing above it is the usual mark of a lossy encode
  3. 3 Use the overlay buttons to highlight evidence: the cutoff line and spectral holes
  4. 4 Check the verdict and use the forensic guide below the result to understand what was detected

How to Read Your Spectrogram

A spectrogram shows every frequency in your audio over time. The horizontal axis is time (left to right), the vertical axis is frequency (low at the bottom, high at the top), and brightness indicates energy. Here's what to look for.

What does a file with no codec signature look like?

A file with no codec signature usually shows colour and texture all the way up to the Nyquist frequency (22.05 kHz for 44.1 kHz files). Energy fades toward the top — most music has less high-frequency content — but there is no abrupt cutoff: a gradual, uneven fade with noise texture above the music. Older and band-limited recordings fade earlier, in the same gradual way.

What to check: Toggle the Cutoff overlay — it should sit at or near the Nyquist limit. The Holes overlay shows few dots on dense music; sparse music shows more whether or not it was encoded.

What does a transcoded file look like?

A file converted from MP3/AAC to FLAC/WAV shows a sharp horizontal line where all content abruptly disappears. Above the line: solid black. Below it: normal audio. This "shelf" is the signature of lossy compression — the encoder permanently discarded frequencies above that point. A lossless master with a steep low-pass shows the same shelf, so check where it sits against the reference table.

What to check: Toggle Cutoff — the red dashed line sits where the content stops. Toggle Holes — orange dots mark silent bins between loud ones; next to a wall they support the reading, on their own they prove nothing.

What do the overlay layers show?
OverlayColorWhat It ShowsGood SignBad Sign
CutoffRed lineDetected frequency ceiling21 kHz and above, or near NyquistSharp shelf between 16 and 21 kHz
HolesOrange dotsSilent bins next to loud neighborsFew or no dotsDense clusters next to a wall
How to use the zoom controls

The forensic workstation lets you inspect specific frequency ranges in detail:

  • Frequency slider — hover on the left edge of the spectrogram to reveal two vertical sliders. Drag them to zoom into a frequency band (e.g. 15-22 kHz to inspect the cutoff region).
  • Ctrl+Scroll — zoom the frequency axis centered on your cursor position. Great for quick inspection without leaving the spectrogram.
  • Drag to select — click and drag a rectangle to zoom into a specific time + frequency region. Useful for inspecting the edge where the content stops.
  • Double-click or press the Reset button to return to the full view.
Frequency cutoff reference table

LAME, the most common MP3 encoder, low-passes at a frequency set by the bitrate. A wall at one of these positions, with digital silence above it, is a codec fingerprint. Other codecs put their walls elsewhere.

CutoffLikely SourceWhat It Means
< 16.5 kHz128 kbps MP3A wall here usually means a low-bitrate encode
16.5 – 19 kHz192 kbps MP3A wall here usually means a mid-bitrate encode
19 to 21 kHzMP3 at 256–320 kbps, Opus at any bitrateA wall here points to a lossy source but may get no verdict. An older master with a 20 kHz low-pass looks the same
21 kHz and aboveNo codec wallNever read as Transcoded — this includes encodes that kept the full band (MP3 at V0, AAC at 256 kbps from Apple's or FFmpeg's encoder)
What about fake Hi-Res and upscaled files?

"Fake Hi-Res" files claim 24-bit/96kHz but actually contain 16-bit audio padded with zeros. The tool detects this two ways: by checking if the raw sample bytes have zero-padded lower bits (WAV/AIFF), and by checking if decoded float samples snap to a 16-bit quantization grid (works for FLAC/ALAC too). If detected, the verdict shows Upscaled with the effective bit depth. A 16-bit source that was gain-changed, dithered or resampled at 24-bit is not detectable. The batch table runs the same check.

Upsampled is different — the file claims a high sample rate (e.g. 96 kHz) but all spectral content stops well below the Nyquist limit, suggesting it was upsampled from a lower-resolution source. It is found when the upsampler left a clean wall at the old limit; a cheap upsampler that leaves images above it is not.

What do the Evidence percentage and the coverage lines mean?

A Transcoded result shows a score margin: how far the codec evidence (where the wall sits, how steep it is, the silence above it, intensity stereo) outweighs the signs of a recording, capped at the top of the scale. It is not the chance that the file was encoded. A result with no signature shows which checks ran and which could not, instead of a number: a percentage there would suggest a certainty the spectrum cannot give. Use the overlays as context either way — a flat horizontal shelf points to a codec; a fuzzy, uneven fade points to a recording.

What the Checker Finds — and What It Cannot

Measured on real music: each source was encoded, decoded to a 16-bit FLAC and run through this tool. The table shows what usually happens, not a guarantee for one file.

ResultTypical sources
Usually foundMP3 at 128–320 kbps constant bitrate, Opus at 128–160 kbps, AAC at 128 and 256 kbps from the Fraunhofer FDK encoder
Sometimes found, often no verdictMP3 at V2, AAC at 128 kbps from Apple's encoder, HE-AAC at 64 kbps from Apple's encoder in a 44.1 kHz file
Rarely found; about one file in three reads No transcode foundOgg Vorbis at about 160 kbps
Not visibleMP3 at V0, AAC at 256 kbps from Apple's or FFmpeg's encoder, AAC at 320 kbps from FFmpeg's encoder, HE-AAC at 64 kbps from Apple's encoder in a 48 kHz file, Ogg Vorbis at about 320 kbps, and MP3 saved again with noise-shaped dither
Reads Transcoded although losslessA master with a steep low-pass below about 21 kHz, or a recording made at 22.05 or 32 kHz and converted up to 44.1 or 48 kHz

Frequently Asked Questions

How does lossless checking work?
The tool computes a spectrogram of your audio — a 4096-point FFT with a Hann window, sliding across the file in overlapping frames — and looks for the fingerprints a lossy codec leaves: a low-pass wall with digital silence above it, and intensity stereo. The position of the wall, how steep it is and what sits above it carry most of the weight; without a wall the tool never calls a file transcoded. When the evidence is ambiguous the tool gives no verdict instead of guessing.
What do the verdicts mean?
No transcode found: no lossy-codec signature in the spectrum — content reaches 21 kHz or runs close to the file's frequency ceiling, or rolls off the way a recording does with a noise floor above it. This is not proof of origin: an encode that kept the full band leaves no trace. Transcoded: a steep low-pass wall like a codec's sits below about 21 kHz, and the rest of the evidence (the silence above it, intensity stereo) points the same way. A wall is an indication, not proof: the usual cause is a lossy source saved again as FLAC or WAV, but a lossless master with a steep low-pass below about 21 kHz usually reads Transcoded too. Upsampled: the file claims a high sample rate but all content stops at or below a lower rate's Nyquist limit. Upscaled: a 24-bit file whose samples all sit on a 16-bit grid. Unknown: too short, too quiet, an edge that both a band-limited lossless file and a lossy encode could produce, or lossy cues with no codec wall to confirm them — the tool abstains rather than guesses.
Can the tool detect AAC transcodes?
AAC at 128 kbps shows a wall near 15–18 kHz. How often it is found depends on the encoder: some shape that edge gently, and the tool then gives no verdict. HE-AAC is found only by its low-pass wall: HE-AAC at 64 kbps from Apple's encoder often gets no verdict instead, and in a 48 kHz file it usually keeps content up to about 22 kHz and is not detectable from the spectrum. AAC at 256 kbps from Apple's encoder — iTunes and most store downloads — keeps the full band and is not detectable from the spectrum either.
Why would someone transcode lossy to lossless?
Sometimes it's accidental — someone converts their MP3 library to FLAC for a new player without realizing it doesn't improve quality. Sometimes it's deceptive — files sold or shared as 'lossless' that are actually upconverted MP3s. Either way, the original lossy compression permanently removed frequency content that cannot be recovered by re-encoding to a lossless format.
What about vinyl rips and older recordings?
Vinyl rips and tape transfers roll off gradually and keep an analog noise floor to the top of the spectrum, so they read as no transcode found, with a note about the roll-off. An older digital master with a steep low-pass near 20 kHz is different: it cannot be told from a codec wall and can read Transcoded.
Is my audio uploaded to a server?
No. All processing runs directly on your device using your own GPU or CPU. Your files never leave your machine — not even temporarily.
Is this the original Lossless Audio Checker (LAC)?
No. This is an independent tool by Brizm that runs on your device, with nothing to install. The desktop program of the same name is a separate project, and its website was offline when we last checked (October 2026). The verdict names are similar; the analysis is our own, and this page lists what it cannot see.
Does "No transcode found" mean my file is lossless?
No. It means none of the checks found a lossy-codec signature. Encodes that keep the full band — MP3 at V0, AAC at 256 kbps from Apple's or FFmpeg's encoder, high-quality Ogg Vorbis — and lossy files saved again with noise-shaped dither leave nothing to find. Treat the result as a screen that catches common transcodes, not as a certificate.
Why is there no bitrate or quality score?
The tool looks for traces of lossy encoding; it does not grade sound quality. When it finds a codec wall it shows where an MP3 at a given bitrate would put that wall, which is an estimate and assumes an MP3 encoder. A file with no codec signature has no bitrate to report.
Can I check an MP3 or M4A file?
Yes. An MP3 or AAC file is lossy by definition, and the result says so. The analysis shows where its encoder cut the spectrum; finding no codec wall in such a file does not make it lossless.
Brizm

Unlock Cloud Assist

Offload heavy processing to Cloud Assist. 15 free Processing Minutes to start.

or