Music Library Doctor
How-to

How to repair a corrupted Rekordbox encrypted database

Rekordbox showing database errors? MLD diagnoses the encrypted master.db, attempts schema repair, and falls back to the most recent verified backup.

The problem

When Rekordbox shows "Cannot open database" or your library appears empty after launch, master.db is often partially corrupted — a write was interrupted, the disk had a hiccup, or the encryption key state is out of sync. Rekordbox itself has no repair tool. The official guidance is to delete master.db and re-import from XML, which loses cue points, hot cues, beatgrid edits, and nested folder structure.

How Music Library Doctor does it

  1. 1 Install Music Library Doctor. Don't open Rekordbox yet — repeated launches against a corrupted DB can make things worse.
  2. 2 Open MLD's Library Health → Rekordbox panel. MLD opens master.db with the encryption key and runs schema integrity checks.
  3. 3 If the corruption is local (one table, salvageable rows), MLD attempts an in-place repair: copies salvageable rows into a fresh schema, preserves encryption, writes a new master.db.
  4. 4 If the damage is too severe, MLD lists its restore-verified backups by timestamp. Pick the most recent good one — restore is one click.
  5. 5 Reopen Rekordbox. The repaired or restored library loads with cues, hot cues, beatgrid, and playlist hierarchy intact.

Supported today

Rekordbox · Serato DJ · VirtualDJ (incl. Favorite Folders) on Windows 10+ and macOS (Apple Silicon + Intel).

Why native integration matters

Encrypted database repair needs three things most generic SQLite tools can't do: read the Rekordbox vendor encryption key, understand Rekordbox's schema (which tables hold what, which foreign keys matter), and produce output Rekordbox itself will accept on next launch. MLD does all three. If the damage is too severe for in-place repair, MLD's restore-verified backups (taken automatically before every operation) are the fallback — so you're never worse off than the last good state.

Frequently asked questions

What causes Rekordbox database corruption?

Most commonly: a Rekordbox crash or forced quit during a write, a disk filling up mid-save, an antivirus tool quarantining the file mid-transaction, or an external drive disconnect while Rekordbox was active.

Will I lose my cue points?

If MLD's in-place repair succeeds, cue points, hot cues, and beatgrids are preserved. If you have to fall back to a backup, you keep whatever the most recent backup contained — so the more recent the backup, the less you lose.

Does this work with Rekordbox 6 AND 7?

Yes. MLD handles the encrypted DB format used by both 6.x and 7.x. The repair logic adapts to the schema version automatically.

What if I have no recent backup?

MLD takes a backup before its own repair attempt, so even if the repair fails you can still get back to the broken state. If you've been running MLD for any prior operation (playlist transfer, missing-file fix), restore-verified backups should already exist.

Should I delete master.db and start fresh?

Only as a last resort, and only after trying MLD's restore. Starting fresh means re-importing every track and losing every cue point and beatgrid you've ever set.

Get your library in shape in minutes

Free tier covers detection and viewing. Lifetime access is $49 — $19 for the first 100 DJs.

Related guides