Windows · local web app · DJ tooling
The whole music-library cleanup, in the right order, in one window.
Highlights
One process, one port
A single local server on 127.0.0.1:8780 running the entire workflow. Not three tools you remember to run in sequence.
In dependency order
Kill duplicates, then remove bad-quality files, then tag what survives. Doing it in any other order wastes work.
Nothing leaves the machine
Your library is scanned in place, locally. No uploads, no cloud lookups of your collection.
Cleaning up a large music library is not one job, it is three, and the order matters. Tag everything first and you will re-tag duplicates you are about to delete. Delete duplicates before checking quality and you may keep the wrong copy of a pair.
FreekyClean runs the whole sequence in one place, in the order that does not waste your effort.
The stages
DupScratch finds and removes duplicates first, so nothing downstream is done twice.
WubCheck then flags files that are not good enough to play out: wrong bit depth, wrong sample rate, bitrate too low, or transcoded from a worse source.
GhostTagger finishes by filling in the metadata and artwork on what survived.
Each stage also exists as its own tool, for when you only need the one thing.
Why local
A Python backend serving a browser client at 127.0.0.1:8780. One port, one process, one server.
A music library is thousands of large files and a lifetime of collecting. Uploading it somewhere
to be tidied is the wrong shape of solution.