How to diagnose a broken Rekordbox XML import
Use this checklist when playlists import empty, tracks disappear, or Rekordbox rejects an XML export.
1. Preserve the original export
Make a copy before editing. XML repairs can change track identifiers and playlist references, so keep an untouched file for comparison and recovery.
2. Confirm that the file is valid XML
A missing closing tag, unescaped ampersand, or damaged character encoding can prevent the entire document from loading. A valid Rekordbox export normally has DJ_PLAYLISTS as its root element.
3. Inspect the collection tracks
Each collection TRACK should have a stable TrackID. Check for duplicate IDs and missing Location values. Missing or malformed locations commonly produce absent tracks after migration between computers.
4. Check playlist references
Playlist entries refer to collection tracks by key. If a playlist key does not match any collection TrackID, the playlist may import with missing entries even though the XML itself is well formed.
Inspect encoded Location paths
Use the browser-only decoder to reveal percent-encoded spaces, user folders, drive letters, and network hosts without uploading the path.
Decode and inspect a Location value →
5. Treat BPM warnings separately
A missing or non-positive AverageBpm does not always make the XML invalid, but it can reveal incomplete metadata or an export problem. Review these tracks before relying on tempo-based workflows.
Run a private browser preflight
The free checker analyzes your XML locally in the browser. The file is not uploaded. It checks XML integrity, missing locations and BPM values, duplicate track IDs, and broken playlist references.
When automated checks are not enough
Version-specific behavior, path conversion, and library migration rules may require a manual review. You can request a fixed $49 review quote. A quote or inquiry is not an order, payment, sale, or revenue record.
Scope and limitations
This guide is diagnostic and does not guarantee compatibility with every Rekordbox release or player. Never overwrite your only library copy, and test repaired exports on a duplicate library first.