Before you clean a DJ library

1. Prove your backup works

Close your DJ software. Back up both the music and its library databases to a separate location. Restore a small sample into a test folder and check that it plays. Keep the backup untouched while you review duplicates.

Start with a copy of a small folder. Avoid cleanup immediately before a gig, on a disconnecting drive or while another tool is moving tracks.

2. Compare the copies you actually use

A confidence score is a clue, not proof that two files are interchangeable. Listen for clean and explicit edits, intros, outros, remixes and different mastering. Compare tags, artwork and audio quality. Check which path your crates and playlists reference, and confirm cues and loops in your DJ software.

Keep both versions when their purpose is unclear. A suggested keeper does not establish that its crates, cues or edits are the ones you need.

3. Review a small change, then check playback

Review every proposed file change. Know where archived copies will go and how you would restore them. A history label does not replace a verified backup. After a small cleanup, reopen the DJ software and check affected tracks, crates, cues and loops before proceeding.

Hard links make two paths refer to the same file data; they are not a backup. Permanent deletion needs a separate recovery plan.

4. Stop if a cleanup fails

Do not immediately repeat the run, empty the Trash or reorganize its archive. Keep the original folders, archive and history records in place. Note the cleanup mode and error. Check for missing files using your backup and the affected DJ library, then use support before changing more files.

Do not assume that every failed run has a complete restore record. Keep your separate backup available.

5. Share report facts without sharing your library

The Mac app’s JSON and CSV exports contain full paths. Do not upload those raw exports to a chat or public discussion. Use the separate local sanitizer before sharing a report, and keep its private mapping on your computer. The ChatGPT companion is still awaiting directory submission; it cannot scan audio or perform cleanup.

Read the companion privacy policy before uploading a sanitized report in a supported client.

What should the next guide cover?

Tell us which library problem you need help with through support. Describe the workflow without sending music, database files, real paths or private mappings. A support message is not permission to publish your story or subscribe you to community email.