Fake Transcodes: Why Converting MP3 to FLAC Never Restores Audio Quality
The "Fake 320" and "Fake Lossless" trap: how streaming rippers inflate container bitrates while audio data remains permanently truncated.
1 The Pixelated Image Analogy
Imagine taking a low-resolution 200x200 pixel image from an ancient flip-phone and saving it as an uncompressed 4K TIFF image in Photoshop:
The result? The file now weighs 50 Megabytes, yet the image remains completely blurry and pixelated.
The exact same principle applies to digital audio: when a 128 kbps lossy encoder strips all frequencies above 16 kHz to save space, that mathematical information is destroyed forever.
2 What is a Fake Transcode (Deceptive Upsampling)?
A fake transcode occurs when an audio stream originally encoded at low bitrate (e.g., 96 or 128 kbps) is re-encoded into a higher bitrate container (such as 320 kbps MP3) or even a lossless container (16-bit 44.1 kHz WAV or FLAC).
3 How to Spot a Fake 320 on a Spectrogram
Standard DJ gear and media players only inspect the file header metadata (which reads "320 kbps"). But the spectrogram displays physical acoustic reality: if high frequencies abruptly cut off flat above 16 kHz with total silence up to 22 kHz, you are dealing with a counterfeit 128k rip.
4 Common Sources of Fake Transcodes
Online YouTube/SoundCloud Rippers: Web rippers that advertise "Download WAV from YouTube" simply extract the 128 kbps Opus or 160 kbps AAC stream and wrap it inside an uncompressed WAV container.
Bootleg File Sharing Channels: Dubplates or club edits frequently circulate where an uploader re-encoded a low-res promotional preview into 320k to distribute it as an official master.
Audit Your Collection Now
Automatically flag fake 320 kbps MP3s before they compromise your live sound.
Audit My Tracks Now