Download Queue
Explore
Local Auto-Tagger
Paste (or drop) the folder or file you want to fix. Supported formats: FLAC, MP3, M4A/AAC, OGG Vorbis, Opus, WAV, AIFF, WMA, WavPack, Monkey's Audio, Musepack, TrueAudio. SpotiFLAC will scan them, find the correct Spotify metadata, and let you compare before applying changes.
Files in the same group are acoustically the same recording — review before deleting anything; a match is a strong hint, not a certification.
Groups every copy of the same recording in the folder above — by ISRC, then by artist/title and duration for the files that have none — and keeps the best copy of each. Fast enough for a library of thousands, where the fingerprint scan is not.
Following
Paste an artist link. The catalogue that already exists is recorded as seen, so the first thing downloaded is the first thing released after you follow — not four hundred back-catalogue tracks. Use Reset on a row if you do want the back catalogue.
Your library
Built from what this install has actually downloaded. Genre, release year and duration are only recorded for downloads made since this feature landed, and a genre needs metadata enrichment to have been on — each section says how much of your history it could use.
Settings
Check endpoint reachability for each SpotiFLAC provider.
How each provider has actually behaved on this machine — attempts, how often they worked, how long they took, and what the last failure said. Worst first. An extension listed as never tried is not broken; nothing has reached it yet, usually because another provider earlier in your service order keeps succeeding first.
Registry URLs tell SpotiFLAC where to look for installable extensions. Sources
can come from a terminal export, from a .env file, or
be added here. You can remove any of them, including ones set outside the app.
A directory lists registries (not extensions directly) for you to review. Nothing here is bundled either — add a directory URL someone shared with you, then click Discover to probe each registry it lists for reachability before deciding whether to add it above.
A registry's sha256 checksum proves a package wasn't corrupted in transit — it says nothing about who published it. Trust a maintainer's public key here to verify their signed entries too; unsigned entries are exactly as trusted as they are today.