You downloaded a track, the tag says 320kbps, the file is the right size for 320kbps, and it still sounds thin through the club system. That's not your imagination and it's not your ears. It's a fake 320, and it's more common in DJ pools, download sites, and shared drives than most working DJs realize.
Here's what's actually happening inside that file, why the label can't be trusted, and how to check your own library in a few minutes.
What "fake 320" actually means
An MP3 is a lossy format. Encoding a track at 320kbps keeps almost all of the detail from the original recording. Encoding the same track at 128kbps throws a lot of that detail away to make a smaller file, mostly high-frequency content: the stuff that adds air and sparkle to a mix rather than the stuff that carries the beat.
A fake 320 starts life as that smaller file. Someone takes the 128kbps MP3 and re-encodes it at 320kbps. The file gets bigger. The tag changes to say 320kbps. Every piece of metadata now claims a real 320 encode. But the detail that got thrown away during the original 128kbps pass never comes back, because it was deleted, not compressed. Re-encoding a smaller file into a bigger one doesn't restore what's missing, it just describes the same missing detail using more bits.
It's the same problem as photocopying a blurry photo on a higher-resolution setting. The new copy takes up more space on the page. It's still blurry, because the blur was already there before you copied it.
Why the label can't tell you anything
File size and tag both look right on a fake 320. That's exactly why so many end up in circulation without anyone catching them. A DJ who checks a track's properties in Rekordbox or Serato sees 320kbps in the metadata field and has no reason to distrust it, because the software is reading the tag, not the actual audio.
The one thing a re-encode can't fake is the frequency content. A genuine 320kbps MP3 carries detail up near 20kHz, close to the edge of human hearing. A file that started at 128kbps has a hard cutoff much lower than that, usually somewhere in the 16kHz range or below, because that's where the original low-bitrate encoder stopped keeping information. Re-encoding at a higher bitrate afterward doesn't move that cutoff. It's baked in.
That cutoff is visible on a spectrogram as a flat line where the top of the frequency range should show activity. It's the one part of the file a fake 320 can't hide, because it isn't a matter of what the tag says. It's a matter of what's actually in the audio data.
Why this keeps happening
Fake 320s aren't usually malicious. Most trace back to a chain of re-encodes: a track gets ripped from a low-bitrate stream, shared as 128kbps, someone converts it to 320kbps to match their library's format standard without realizing the damage is already done, and it keeps circulating from there. Each new copy inherits the same ceiling. Nobody along the chain necessarily lied on purpose. The file just picked up a label that stopped being true several transfers ago.
DJ pools and download sites vary a lot in how carefully they check this before a file reaches a subscriber. A pool that batch-converts promo pools without auditing source quality can ship thousands of fake 320s without anyone on either end noticing, because the failure is invisible to a file browser. It only shows up on playback, through a system good enough to expose the missing top end, which at a paying gig is exactly the system you're playing on.
How to check your own files
You don't need studio gear to catch this. You need something that reads the actual frequency content of the file instead of trusting its tag.
Look at a spectrogram. Free tools exist that render one. A flat cutoff line where the top of the frequency range should show natural activity is the tell. If a track drops off hard and cleanly at a specific frequency, especially somewhere well under 20kHz, that's the signature of an upscale, not a real encode.
Listen for it, with the right reference. A fake 320 next to a genuine one on the same system will sound noticeably duller in the top end, even if the difference is hard to name until you A/B them. This works best on a track you already know well.
Or run it through a tool that does the read for you. Tune Check is a free tool from Bangerz Army that reads a file's actual frequency content in your browser, nothing gets uploaded, and tells you whether a track is a real 320, a fake 320, or a case where the evidence is inconclusive rather than guessing either way. Drop up to 20 files at once and see the spectrogram behind each verdict.
Catching a fake 320 in your own library before a gig, rather than at the booth when the system exposes it, is the whole point. Bangerz Army built Tune Check because catching this is the same test we already run on every track before it goes in our own catalog. This just hands DJs that test for free, on the files they already own.
Frequently asked questions
Can you actually hear the difference between a real and fake 320?
On laptop speakers or cheap earbuds, often not. On a club PA, a monitor system, or good studio headphones, yes: the missing high-frequency detail shows up as a duller, flatter top end, most noticeable on cymbals, hi-hats, vocal sibilance, and anything with air or sparkle in the mix. The gap is most obvious in a direct A/B against a genuine 320 of the same track.
Does converting a file to a lossless format like WAV or FLAC fix a fake 320?
No. Converting a lossy file into a lossless container doesn't add back detail that was already discarded. A 128kbps MP3 converted to FLAC is still missing the same high-frequency content. It's just wrapped in a format that's lossless from that point forward. The damage happened at the original low-bitrate encode, and no later conversion undoes it.
Is it illegal to relabel a fake 320 as a real one?
Mislabeling bitrate isn't typically a legal issue on its own. It's a quality and trust issue. The bigger risk for a working DJ is playing a file that sounds noticeably worse than expected in front of a paying crowd, or building a library where you can't tell which tracks are actually gig-ready without checking each one manually.
Are FLAC and WAV files ever fake too?
Yes. A lossless wrapper doesn't guarantee a lossless source. The same problem shows up when a low-bitrate MP3 gets converted to FLAC or WAV without ever regaining the detail the original compression removed. The file format changes; the missing frequencies don't.
Want the deeper walkthrough on sourcing tracks you don't have to double-check? Read how to build a DJ music library that's edit-first and gig-ready. Or run your own files through Tune Check right now, free, no upload.
Image credits. All photos via Pexels under the Pexels free-to-use licence. Hero: Hendrik B. Inline 1: Egor Komarov. Inline 2: Erik Mclean.