Stop comparing catalogues
Every BPM Supreme versus DJcity comparison you have read ranks them on the same three things: how many tracks are in the vault, what they cost, and which genres they cover. All three matter, and both pools clear the bar. BPM Supreme and DJcity are both large, well-run, and stocked with the current-format edits working DJs actually play.
But catalogue size is not what you live with. What you live with is what lands in your library after you download: the tags, the version labels, the artist formatting, the junk left in the comment field. That is the axis nobody rates them on, and it is the one that decides whether your collection stays searchable a year from now. So let's rank them there.
What actually lands in your library
Start with the raw file, because that part is close to a tie.
Both pools ship 320 kbps MP3 at 44.1 kHz, full-quality DJ-standard files. BPM Supreme tags each MP3 with artist, title, year, cover art and BPM. DJcity fills in artist, title and BPM, and ships standardized cue points and beatgrids so tracks drop into Serato DJ Pro, Rekordbox, Traktor Pro or Virtual DJ ready to play.
Both also serve the version spread you expect: clean, dirty, instrumental, acapella, intro edits and remixes. The difference is emphasis. BPM Supreme fills more ID3 fields by default, including year and cover art on every file. DJcity leans on gig-prep, cue points and beatgrids already set. If you want to walk into a set with pre-cued, beatgridded files, DJcity's prep is the stronger hand. If you care about complete tags out of the box, BPM Supreme populates more fields.
Neither of those is a dealbreaker. The differences that compound over hundreds of downloads are in how the metadata is written, not whether it exists.
Where libraries actually get messy
Here is what we see on the aftermath side, cleaning up thousands of DJ libraries: the damage is rarely the audio. It is the metadata conventions, and they are the same conventions every pool ships.
- Version labels stuffed in the title. "Song (Clean)", "Song (Intro - Dirty)", "Song (Acapella Out)". Useful at the pool, noise in your browser. Two hundred tracks in and a search for "Song" returns nine near-identical rows you have to read one at a time.
- Pool branding in the comment or grouping field. Promo services routinely stamp a name, a URL or a batch code into the Comment or Grouping tag. It is free advertising for them and clutter for you, and it quietly breaks any smartlist or filter you build on those fields.
- Artist formatting that never agrees. "Artist ft. Guest", "Artist feat. Guest", "Artist & Guest", "Artist, Guest". The same collaboration written four ways becomes four different artists in your browser and an artist filter that never fully groups.
- Genre taxonomy that does not survive import. Each pool runs its own genre tree. Pull from two pools and you now have "Hip-Hop", "Hip Hop", "HipHop/Rap" and "Urban" all describing the same crate.
None of this is a knock on either pool. It is the nature of downloading from anyone. The point is that the pool you choose is only step one. Step two is imposing your own conventions on top of theirs, and step two is where most libraries fall apart.
Cleaning it up in Lexicon
This is the part the comparison usually skips, and it is where the two pools stop mattering, because once tracks are in Lexicon you standardize them the same way regardless of source.
- De-dupe first. Pull the same track from both pools, or grab a clean and a dirty that are really the same edit, and you get duplicates. Find Duplicates, in the Utility menu, scans your library and matches tracks by audio signature or by tags. The audio-signature match catches the same recording even across filetypes; the tag match catches Artist and Title pairs and works best once your tags are already clean.
- Fix the genre sprawl. Genre Cleanup pulls every unique genre value in your library into one list, so you can collapse "Hip Hop", "HipHop" and "Urban" into a single value in a few clicks.
- Consolidate artists. Artist Cleanup does the same job for artist names, so every spelling of a collaboration lines up under one entry and your browser groups the way you expect.
- Clean the titles. Run Smart Fixes to tidy titles, trimming version clutter and leftover branding, before it pollutes your search and your duplicate matching.
- Move the useful bits into tags. Rather than leave "Clean", "Dirty" or "Intro" buried in the filename, lift those into Custom Tags. Lexicon's tagging is genuinely deep, and once version and energy live in tags you can build a smartlist like "clean intros at 124 to 128 BPM" instead of squinting at titles.
Do that once, set the conventions, and every future download from either pool folds into a library that already has rules.
So which one fits you
On the axis that actually matters, what your library looks like after the download, it is close, and the honest answer is that your cleanup workflow matters more than the badge on the pool.
- If you want the most complete tags out of the box, year and art included, plus a deep versioned catalogue, BPM Supreme edges it.
- If you value gig-ready files with cue points and beatgrids already set, DJcity's prep saves you a step at load-in.
Pick the pool on catalogue and edits, the part only the pool can give you, and stop worrying about their metadata habits. Those are yours to overwrite. Choose the pool for the music, then own the library yourself.
