Library & Prep

Library Database

Reviewed by

The local file maintained by DJ software that stores all analyzed track data including BPM, key, cue points, and beatgrids.

A library database is the proprietary data store that DJ software maintains on the host computer to index a DJ's music collection and record all analysis results and prep work. It holds BPM, Camelot key, waveform data, beatgrid positions, cue points, loop markers, play count, rating, and organizational structure such as playlists or crates, separately from the audio files themselves.

Why it matters

Because all prep work lives in the database rather than the audio file, the database is effectively the DJ's most valuable asset after the music itself. Losing or corrupting the database without a backup means losing every cue point, beatgrid correction, and organizational decision accumulated over years of preparation.

In practice

Back up the database on a separate schedule from the audio files. In Rekordbox, use the built-in backup tool under Preferences to export a timestamped snapshot to an external drive. In Serato, the primary database lives in the _Serato_ folder inside your Music folder (~/Music/_Serato_ on macOS). Serato also creates a separate _Serato_ folder at the root of any external drive you have imported tracks from. Copy both the Music/_Serato_ folder and any drive-level _Serato_ folders alongside your music whenever you clone or migrate your library.

Frequently asked questions

On macOS, Rekordbox stores its main database in ~/Library/Pioneer/rekordbox/ as a file typically named master.db. On Windows the equivalent path is C:\Users\[username]\AppData\Roaming\Pioneer\rekordbox\. The database is a SQLite file encrypted with SQLCipher, which means it cannot be opened by a standard SQLite browser, though Rekordbox itself reads and writes it normally. Regular backups are important because a crash during a write operation can corrupt the file.
Renaming or moving a file after it has been analyzed will break the database link, resulting in a missing-file warning the next time the software opens. Editing a file's ID3 tags in an external application can also cause the software to flag the track as changed or, in some cases, reset fields that the software manages independently. Make organizational changes inside the DJ software whenever possible to keep the database and file paths in sync.
Yes, but only a subset of it. When you export tracks from Rekordbox to a USB drive, the software writes a condensed version of the database into a PIONEER folder at the drive root that contains only the tracks and associated data you chose to export. The full library database stays on the computer; the USB holds just enough for the CDJ or XDJ to read waveforms, cue points, loops, and beatgrids for those specific tracks.
Ben Modigell

Hey, it's Ben Modigell 👋

I DJ and produce as so I so — downtempo, minimal, dub house, tech house, and techno (releases on Spotify and SoundCloud, links above). Everything I write here comes from my own gigs, studio sessions, and library cleanups: the rules I follow, the failure modes I've actually hit, and the workflow I use when nobody's watching. If a technique didn't earn its place in my own sets, it doesn't make it into a tutorial.

DJingMusic ProductionTech HouseMinimal HouseDub HouseTechnoDowntempoLibrary Organization