Convert rekordbox XML and Traktor NML with a visible loss report
Move the supported parts of a library with evidence you can review: playlist order, file references, cues, loops and grid anchors. See what the destination profile changes before you import it.
DJ Library Handoff
The fictional XML example includes nested playlists, a repeated track, a loop, changing BPM, a cue colour and a hotcue beyond Traktor slot 7. Export to NML to inspect the actual reported tradeoffs.
Supported scope: One UTF-8 XML/NML/CSV up to 2 MiB; 3,000 tracks/CSV rows, 500 playlist/folder nodes, 12,000 playlist references, 128 cue/grid markers per track, 20,000 XML elements and 32 XML nesting levels. rekordbox XML 1.0.0; Traktor NML 12–20 input, v19 output profile. 24 MiB uncompressed handoff output; 30-second worker timeout. CSV mapping: 60 columns. Local absolute paths only; no UNC/remote/streaming links, proprietary databases, Serato crates, audio transfer or application sign-in.
Your library source
Required fields are marked with an asterisk.
DJ handoff workbench
Review your output, then save it to your device.
Make the next step clear.
Your findings, assumptions and next steps will appear here after you run the check.
DJ Library Handoff · https://dj.kitforma.com/ · KitForma
Local files and explicit path remaps
Actual XML/NML and playlist output
Target-specific loss and comparison report
Understand the evidence.
Focused guides explain the rules, the edge cases and the checks worth doing before you act.
Convert rekordbox XML to Traktor with a loss review
Make a test handoff that distinguishes cue timing, beatgrid coverage and source-specific metadata.
Read the guide ↗Field guide / 02Remap DJ music paths without guessing a drive
Use explicit folder prefixes and volume roots to prepare references for another computer.
Read the guide ↗Field guide / 03Use CSV and M3U8 as honest DJ handoff formats
Choose simple inventory formats without mistaking them for a complete prepared library.
Read the guide ↗Before you start
Can this move my music files or check whether they exist?
No. It reads library metadata and writes local file references. Copy the audio separately. A valid file URI only proves that the reference has supported syntax; this browser tool does not open or inspect the referenced music files.
Does it support Serato, rekordbox master.db or streaming libraries?
This release supports exported rekordbox XML 1.0.0, Traktor NML versions 12–20 and mapped CSV. It does not read Serato crates, encrypted or proprietary databases, device exports or streaming-service identifiers. It cannot create portable local tracks from a streaming subscription.
Which cues and grids survive a conversion?
Supported cue, fade-in, fade-out, load and loop positions are mapped. NML output keeps one BPM and the first grid anchor, with slot 0–7 handling; variable tempo, additional anchors and metre/beat-phase changes are reported. Cue colour and extra attributes are outside the output profile. The generated file is reopened to compare supported fields, but you still need to check timing in the destination application.
Why must I enter a volume root for some NML files?
Traktor can store a volume name such as Macintosh HD separately from a directory. The same name can refer to different mount locations on different machines. Enter the actual source root, and for POSIX NML output enter both target volume name and target root. This avoids silently assigning an external-drive track to the startup volume.
Are playlists and duplicate entries preserved?
Static playlist hierarchy and entry order are retained, including repeated references to the same track and empty folders in a full-collection export. Selecting playlists includes their referenced tracks and ancestor folders. Smart-list rules are not converted. Invalid references are refused rather than silently removed.
What is inside the handoff ZIP?
The converted XML/NML, a track CSV, per-playlist M3U8 references, a JSON report with supported data, and the unchanged original metadata source. The original source includes the entire imported library even when you select fewer playlists. Audio files are never included. Review that original-source scope before sharing the ZIP.
Sources & assumptions
Formats, algorithms and supported features are documented below. Check the stated scope and inspect your output before using it.
- AlphaTheta: rekordbox playlist XML format ↗
Official collection, URI, playlist, tempo and position-marker field specification.
- Native Instruments: working with playlists ↗
Playlist export/import and the distinction between static playlists and smartlists.
- Native Instruments: making a library portable ↗
NML/M3U export and the separate option to copy actual music files.
- traktor-nml-utils: independent NML parser ↗
NML is documented from real exports; independent parser and Traktor 3/4 fixtures used for release verification, not a production dependency.
- Pyrekordbox: independent XML reader ↗
Independent rekordbox XML reader and genuine test exports; no encrypted database support is implied.
Reviewed 2026-10-18. Read our methodology or report an issue.