← Back to Blog

Articles

Learn About the Spotify Catalog Tool

Most conversations about owning your catalog focus on what happens when a platform disappears. This one's about something simpler: just having your own copy of what's already live, in your own hands, today — not waiting for a crisis to make you wish you had it.

That's what the Spotify Discography Exporter does. Paste your Spotify artist link, get back a spreadsheet with every title, every URL, every ISRC — the exact metadata a distributor, a sync licensing opportunity, or your own records might ask for someday, sitting in a file you own rather than a page you'd have to screenshot.

What it actually pulls

This is specifically for an artist's own released catalog — the official releases tied to a Spotify Artist page — not a personal listening library or a liked-songs playlist. If it's something you put out, it shows up: title, direct URL, and ISRC code, the identifier that follows a recording everywhere it's distributed. That last one matters more than it sounds; it's the thing that ties a track to royalty reporting no matter which platform or distributor is handling it at a given moment.

Looking to move something else? If it's your own liked songs or playlists you want out, that's a genuinely different job — TuneMyMusic or Soundiiz are built specifically for that, and do it well. This tool is for your own discography specifically.

The one-time setup, honestly described

There's a real two-minute step before the first export — creating a free Spotify developer app to get a Client ID and Secret, since that's what Spotify's own API requires to authorize a request. It's a one-time thing: create the app once on Spotify's own developer dashboard, save the two values, and every export after that is just paste and go.

Why free and open source, specifically

This isn't a lead-generation tool with a paywall a few exports in. It's free because the actual argument behind Artisanal Indie only holds up if the tools back it up — asking artists to trust that their catalog data should be portable, then charging them to access their own metadata, would be a pretty thin position to stand on. It's open source for the same reason: the code doing the pulling is inspectable, not a black box asking for trust it hasn't earned.

Related