Music Library Doctor
Blog · Rekordbox

Rekordbox 6 encryption: what actually changed

When Rekordbox 6 encrypted master.db, third-party tools either updated or died. Here's the technical story and how to choose tools that survived.

Download Free → See pricing

The problem

The shift from Rekordbox 5 (plain SQLite) to Rekordbox 6 (encrypted SQLite via SQLCipher) was a major break for the third-party tooling ecosystem. Migration tools, playlist converters, and library auditors that read master.db directly all stopped working until they added encryption support. Some never did. The Pioneer DJ-recommended path is XML export — but XML is lossy and slow. Knowing whether a tool actually supports encrypted master.db is the difference between a tool that works on your library and one that quietly fails.

How Music Library Doctor does it

  1. 1 Recognize the encryption. Rekordbox 6+ encrypts master.db using SQLCipher with a vendor-derived key. Opening the file without the key returns garbage; the file size, schema, and structure all read as encrypted noise to a plain SQLite reader.
  2. 2 Understand why tools broke. Rekordbox 5-era tools used standard SQLite libraries (better-sqlite3, sqlite3, etc.) which have no encryption support out of the box. Adding SQLCipher requires linking a different SQLite build and knowing the key derivation logic.
  3. 3 Check tool claims carefully. Many "Rekordbox-compatible" tools support 5.x master.db only. The marketing rarely makes the distinction — check release notes, changelogs, and explicit "Rekordbox 6+" claims.
  4. 4 Test with a real 6.x library. The reliable check: take a backup of your master.db (Rekordbox 6+), point the tool at it, see if playlists and folder hierarchy show up correctly. If they do, the tool genuinely handles encryption.
  5. 5 Prefer tools that write back, not just read. Reading encrypted master.db is the easy half of the problem; writing back (without breaking the encryption envelope) is harder. Tools that only read are limited to migration-out, not in-place repairs.

Supported today

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

Why native integration matters

Music Library Doctor was built post-Rekordbox 6 and treats encrypted master.db as the default, not an afterthought. Reading and writing encrypted master.db is the same code path as plain SQLite — the SQLCipher integration is foundational, not bolted on. That matters because in-place operations (missing-file repair, playlist transfer, folder consolidation) need to write back to master.db with the encryption envelope intact, and tools that only added encryption read support can't do the write half.

Frequently asked questions

Does Rekordbox 7 use the same encryption?

Yes. Rekordbox 7 continues the SQLCipher-encrypted master.db format with schema evolutions. MLD handles both 6.x and 7.x.

Can I downgrade Rekordbox to avoid encryption?

Technically yes, but you lose access to anything that requires 6/7-specific features (newer hardware support, current cloud sync, etc.). Most DJs are stuck on the current version for hardware compatibility — the better answer is using tools that handle the encryption.

Does XML export get around the issue?

Yes, but XML is lossy: it drops nested folder hierarchy, simplifies cue point data, and doesn't carry hot cues with custom colors reliably. XML is the lowest-common-denominator escape hatch, not a substitute for native encrypted-DB support.

Is the encryption key sensitive?

It's vendor-derived and consistent across Rekordbox installations. The key isn't "secret" in the security sense — anyone who knows the derivation can produce it. The encryption is more about preventing casual tampering than protecting your library from anyone who has the file.

Get your library in shape in minutes

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

Download Free See pricing

Related guides

How-to
How to back up Rekordbox master.db safely
Rekordbox 6+ encrypts master.db with a vendor key. Music Library Doctor takes restore-tested backups before any write — encrypted DB supported.
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.
Library repair
Fix missing tracks in Rekordbox
Automatic bulk re-linking, encrypted master.db supported, external drives handled as 'offline' instead of deleted. Windows + macOS.
Playlist migration
Rekordbox → Serato DJ
One-click playlist transfer from Rekordbox master.db to Serato crates — no XML, no rebuilt hierarchy, encrypted Rekordbox DBs supported.