Why your Serato hot cues don't survive the jump to rekordbox
If you’ve ever dragged a folder of tracks from Serato into rekordbox and watched every single hot cue silently vanish, you’re not alone. This is one of the most common pain points DJs hit when they’re forced to switch platforms.
The short answer is: both platforms store cue metadata, but they store it in different places, in different formats, using different conventions. Neither is wrong. They were just built for different worlds.
Where Serato actually stores your cue points
Serato writes cue metadata into your audio file’s ID3v2 tag as a custom GEOB frame named Serato Markers2. Inside that frame is a base64-encoded binary blob containing every cue, loop, and color you’ve placed. It’s elegant — the cues travel with the file.
rekordbox stores cue metadata in its own library database. It doesn’t read Serato’s GEOB frame, so from rekordbox’s perspective the ID3 tag contains no cue data at all.
This is why copying the same MP3 into both apps gives you a loaded track with full grid and cues in Serato, and a track with zero cues in rekordbox. The file is identical. The databases are not.
How briDJe handles the translation
briDJe reads your Serato library and a rekordbox.xml export into an editable working copy, then prepares the destination from there. Colors, loops and cue types are mapped to what the target supports, and the read-only export preview flags known limits, so check a few tracks in your DJ software afterwards.
What this means for you
If you’re moving a library today, review the read-only preview and spot-check a small sample before you move your main library.
You can try briDJe free for 15 tracks — that’s enough to verify the transfer works for your specific cue style before committing.