Drop your Rekordbox collection and find out what it can actually do — how much of it has somewhere to go, which tracks nothing follows, where the tempo holes are, and what is still sitting there un-gridded. It runs in this tab; nothing is uploaded.
Drop your Rekordbox XML here
In Rekordbox: File → Export Collection in xml format. Nothing is uploaded — the file is read and measured inside this tab, and you can watch the network panel to check.
Every piece of DJ software can show you a key distribution. It is the least useful chart in the booth, because owning tracks in a key tells you nothing about whether you can get from one to another. Key and tempo have to be read together: a collection that is 40% 8A looks healthy right until you notice the 8A is all 126 and the 9A you would step into is all 174.
So the measurement this tool is built on is reach — for each track, how many others sit one safe Camelot move and one pitch range away. It is the number that tells you whether a collection is navigable, and it is why two DJs with the same track count can have completely different nights.
The catalog is the control. Our public catalog holds 440,000+ analysed tracks, and the same reach calculation runs against it, so every number about your collection sits next to what the same track would find in a large one. The two extremes are worth knowing before you start: 7A is the best-connected key we hold — one safe move out of it reaches 88,253 tracks — while 2B reaches 33,564. If your collection leans on the second, it will feel tighter than its size suggests.
| Measurement | What it tells you |
|---|---|
| Playable share | Tracks with a tempo, a key, and somewhere to go. The one composite number here. |
| Reach | Per track, how many others are one safe move and one pitch range away — yours against ours. |
| Dead ends | Analysed tracks nothing in your collection follows. Exportable as CSV with the catalog count for each. |
| Key coverage | All 24 Camelot keys, and which are empty. |
| Tempo gaps | The widest run of empty tempo inside the range you cover — the jump you cannot make gradually. |
| Prep state | No beat grid, no cue points, never played, never rated. |
| File quality | Bitrate under 256 kbps, and formats a CDJ may refuse off a USB stick. |
| Duplicates | Same artist and title with mix names stripped. |
| Shape | Genre concentration and how many tracks you added per year. |
The export contains your track metadata — titles, artists, tempos, keys, ratings, play counts, cue points and file paths. It does not contain the audio.
No. There is no upload endpoint behind this page and no request is made when you drop a file — you can open the network panel and watch. The XML is read with the browser's own file reader, parsed in the tab, measured in the tab and rendered in the tab. Nothing is stored, nothing is logged, and reloading the page destroys the result. The comparison against our catalog works the other way round: the key and tempo distribution of our catalog travels to you with the page, and the comparison happens on your machine.
A track is playable when it has a tempo, a key, and at least one other track in your own collection that is a safe Camelot move away and within 6% on the pitch fader. That is deliberately the lowest bar a record has to clear to be mixable at all — not a judgement about whether it is any good. A track can be your favourite record in the world and still be a dead end, and that is a statement about the gap around it rather than about the track.
It is the default pitch range on a CDJ, so it is the window you actually have without reaching for the range button. Wider is possible — ±10% and ±16% are a button press away, and master tempo will hold the key while you do it — but a tool that assumed you would stretch every mix to its limit would flatter the answer. The window is stated on the page so you can read the numbers as what they are.
Up to around 120 MB of XML, which is roughly 60,000 tracks. Above that the browser's own XML parser is the limit rather than anything we control, and the page will tell you so instead of hanging. Everything below that is fast — the measurement itself takes well under a second even on a very large collection, because it sorts each key once and then binary-searches the tempo window rather than comparing every track to every other track.
Not yet — this reads Rekordbox XML only, because that is the format we already parse properly for library import and we would rather support one format correctly than four badly. If you are on Serato or Traktor, most DJ software can export or convert to Rekordbox XML, and that export will work here.
Two options, and the right one depends on the track. If it is a record you love, the fix is buying the bridge — the CSV export lists each dead end with how many tracks we hold that would follow it, so you know whether the material exists before you go looking. If it is a record you bought once and never played, the fix is deleting it: a collection you cannot navigate is worse than a smaller one you can.
No, and the tool is careful not to say so. A dead end means nothing else in your collection sits one safe move and one pitch range away from it. A 174 BPM drum and bass track in a collection of house records is a dead end in that collection and a completely normal record everywhere else. It is a map of your collection, not a review of your taste.
Build a set from the tracks that do connect