Why this matters earlier than people think
With fifty tracks nobody needs a system. With five hundred it's too late to introduce one — order then means going back through five hundred files, and that's exactly why nobody does it. The cheapest moment for a structure is the one at which it still feels unnecessary.
The benefit only shows up in the set, but then it shows up immediately: the track still has two minutes to run, and you need something that holds the energy and fits tonally. With a system that's three seconds. Without one you scroll.
The one distinction that carries everything
Folders = origin
Where the file sits and where it came from. Every track in exactly one folder. Sensibly sorted by source of purchase or by period — not by genre, because genres are a matter of opinion and they change.
Playlists = intent
What you need the track for. The same track may appear in twenty playlists without the file existing twenty times. Everything that changes with your taste lives here.
Anyone who doesn't make this separation ends up copying files into genre folders — and six months later no longer knows which version is the maintained one.
The system in 7 steps
Software-independent — the terms are named differently from program to program, the principle is the same everywhere.
- 1
Put everything in one place
One single music folder on one drive, sorted inside it by source or purchase date. As long as files are scattered across the desktop, downloads and three hard drives, no software can build a reliable library — it loses the references the moment something gets moved.
- 2
Run the analysis and check the beatgrids
The analysis gives you tempo and key. For electronic music the result is usually right; for live recordings, older recordings, and anything with a fluctuating tempo, it usually isn't. Check by hand, once, the tracks you actually play — otherwise a wrong grid catches you out at the worst possible moment.
- 3
Folders for origin, playlists for intent
This is the most important distinction. The folder says where a track came from and where the file lives. The playlist says what you need it for. A track belongs in exactly one folder, but in as many playlists as you like — anyone who tries to solve everything through folders ends up copying files.
- 4
Introduce an energy scale
Three to five levels, from "background" to "peak". This is the piece of information that helps you most in a set and that no software knows on its own: tempo and key say nothing about whether a track fills the dance floor or empties it.
- 5
Set cue points and tags
Four to eight cues per track, always to the same pattern — for example, entry, break, drop, exit. A consistent scheme across your whole collection is worth more than a particularly clever scheme for individual tracks.
- 6
Build set playlists instead of searching
Before every gig, three to five playlists for the sections of the night. In the booth you want to choose between suggestions, not search through a collection.
- 7
Back up — the database too
Two things need backing up: the music files and the software's database with its grids, cues and playlists. Anyone who backs up only the files still has their music after a drive failure, but months of work are gone.
The energy scale: the rating that's missing
Every piece of software gives you tempo and key. None of them gives you the thing that really counts in a set: how does this track land on the floor? You have to award that rating yourself — and it's worth every minute.
Background. Plays without demanding attention. For the start, the breaks, the in-between.
Holds. Whoever is dancing keeps dancing. It brings nobody new onto the floor.
Fills. Pulls people onto the floor. The working range where most sets happen.
Peak. The moment everything runs towards. Use it sparingly — the effect comes from rarity.
How you represent this technically — stars, colours, tags, the comment field — depends on your software and is secondary. What matters is that the meaning stays the same across the whole collection. What you then need these levels for is in the guide to building a set.
Backing up: two things, not one
The most expensive data loss in DJing isn't the music — you can buy that again. What's expensive is the work on the music: beatgrids, cue points, ratings, playlists. Those don't live in the audio files but in your software's database.
So both belong in your backup: the music folder and the program's database folder. A second drive plus a copy kept off-site makes sense. Back up only the files and after a failure you start from zero — with a complete music collection.
The half hour a week
What matters isn't the system but the habit. New music gets processed as it's added, not at some point later:
Run the analysis. Spot-check the grid — the software is rarely wrong, but it is wrong sometimes.
File it in the right source folder. Purchase, pool, free download: where a track came from decides later whether you find it again.
Assign an energy level. One of the four levels above. Ten seconds now, saved in the middle of a set.
Set 4 to 8 cue points. To your fixed scheme — the same one on every track, otherwise it will not help you live.
Add it to the right playlists. A track that is in no playlist does not exist during a set.
Listen to it all the way through, once. Otherwise you do not know your own music — and you find that out at the worst moment.
A tidy-up day every six months never manages it — it gets postponed because it's big. Half an hour after buying music always manages it.
Frequently asked questions about the DJ library
Folders or playlists — which is better?
Both, but for different things. Folders describe a file's origin and its actual storage location; every track sits in exactly one. Playlists describe intent — genre, mood, energy, a particular night — and the same track can sit in as many as you like. Anyone who tries to map everything through folders inevitably ends up with duplicated files and, six months later, no longer knows which version is the maintained one.
How do I sort tracks by energy?
Set a scale with three to five levels and stick to it rigidly — for example: 1 plays in the background, 2 holds the floor, 3 fills it, 4 is peak. Depending on the software, this gets mapped through tags, rating stars, colours or comment fields; which field you use is secondary. What matters is that the meaning stays the same across your whole collection. This one piece of information helps more in a set than any other, because tempo and key say nothing about how a track feels.
How many cue points should I set per track?
Four to eight, and always following the same pattern — say, intro, break, drop, outro. Fewer isn't enough for flexible transitions, more you won't find fast enough in a set, and most gear only offers eight pads anyway. More important than the number is consistency: if cue 1 means the same thing in every track, you don't have to think about it in the booth.
How often should I tidy up my library?
Not in big clean-up sessions, but as you add tracks. Every new track gets analysed, filed, given an energy level and cued immediately — otherwise a pile of unprocessed files builds up that nobody ever works through. Half an hour a week for new music keeps a collection permanently usable; a tidy-up day every six months never manages that.
What happens to my library if I switch software?
Music files can always be carried over; the work put into them not necessarily. Beat grids, cue points and playlists live in that particular program's database, and the formats aren't compatible with each other. Conversion tools exist, but none of them work reliably without loss. If you think a switch is possible, you should at least back up your playlist structure separately as plain text lists — that survives any software change.
How do I back up my DJ library properly?
Two things, and both are necessary: the music files and the software's database folder. If you only back up the music, after a drive failure you'll have all your tracks but every grid, cue, rating and playlist will be gone — precisely the work that took months. A second hard drive plus an off-site or cloud copy is sensible.
Should I rename my files?
Only following a fixed scheme, and ideally before the collection gets large. "Artist - Title (Version)" without special characters has proven reliable, since some devices and file systems struggle with them. More important than the file name, though, is the metadata inside the track itself: it's read by every piece of software, travels along when you copy the file, and survives a change of program too.
Phase 3
Library and preparation on the learning path
DJLearn takes you through analysis, cue workflow and playlist building — with lessons, exercises and quizzes. Free, no subscription.
Start for free