Serato DJ Pro 5 and your play history: what we checked, and where History lives now

Serato DJ Pro 5 is out, and the first question is the practical one: if I update, is my library, my crates and my play history still where my tools expect them? Here is what we checked, on one Mac, and what we found about History along the way.

What we checked on Serato DJ Pro 5.0.0

We updated a working Serato 4.0.10 Mac to 5.0.0 and looked at the files other tools read:

• The library (_Serato_/database V2) — still written and updated while you work.
• Crates (_Serato_/Subcrates) — still written.
• The live log (_Serato_/Logs) — still records every track you load onto a deck.
• History — recorded, but not where it used to be (next section).

That is one Mac and one upgrade path, not a promise for every setup. If you play with an unusual library layout or an external drive, check yours (below).

Where your play history lives now

Older Serato versions wrote one file per session into _Serato_/History/Sessions. Since Serato 4 that folder is no longer updated: on our test Mac the newest .session file dates from June 2026, while Serato had recorded sessions up to the night before. The history did not disappear — it moved into Serato’s own database:

~/Library/Application Support/Serato/Library/master.sqlite

Inside, the history_session table holds one row per session and history_entry one row per track, with its path, start and end time, whether it counted as played, and the device. Treat it as read-only: work on a copy, never write to it, and only with Serato closed.

Are you affected? A 30-second check

Open _Serato_/History/Sessions in Finder and look at the newest file. If it is far older than your last gig, anything that reads those files — a set exporter, a now-playing script, a tool that learns from your history — has stopped seeing your recent nights.

Before you update to Serato 5

1. Close Serato.
2. Copy your _Serato_ folder somewhere that is not synced (an external drive or a plain folder on the Desktop).
3. Copy ~/Library/Application Support/Serato/Library too — that is where master.sqlite and root.sqlite are.
4. Update, open Serato, load a few tracks, and check that your crates and library look right.
5. Do not update the day before a gig.

What Deck Caddie does about it

From version 1.0.72 Deck Caddie reads the nights recorded in master.sqlite as well as the old session files — only nights newer than the last old-style file, so nothing is counted twice — and its diagnostic report now checks the Serato files it relies on and warns in plain words if a newer Serato changes one. It still only reads: it never writes to your library or your History.

Why this matters: a suggestion engine is only as good as the history it learns from. See why your Serato history is a goldmine and how to choose what to play next in Serato.