ISRC Code Finder: An Afternoon Checklist

If you searched for an isrc code finder because you need to track down codes for a batch of releases, paste-a-link tools only solve half the problem. They tell you the ISRC for one Spotify track at a time. They don't tell you which of your 400 files are missing one, which ones are duplicated by mistake, or what else is missing from your catalog besides the code itself. This checklist covers all three, and you can work through it in an afternoon.

What an ISRC actually is (and isn't)

An ISRC is a 12 character identifier assigned to one specific sound recording, not to the song as a composition. It is a unique, 12-character identifier for a specific sound recording or music video, think of it as the passport number for one particular audio master, not for the song itself. The code breaks into four parts: a country code, a registrant code identifying the label or rights owner issuing the code, a two-digit year the code was assigned, and a five-digit designation number unique within that registrant and year.

Two things trip people up every time. First, each unique recording of a song, whether an album version, radio edit, remix, live recording, remaster, or language version, should have its own ISRC so platforms and royalty systems can distinguish between them and attribute usage correctly. Second, you cannot see the ISRC directly inside the regular Spotify app, though Spotify exposes ISRCs via its Web API. That's why third-party lookup tools exist at all: the code is there, it's just not shown in the consumer interface.

Step 1: find the ISRCs you already have (30 minutes)

Before searching anything, check the sources most likely to already have your codes on file. Most distributors display the ISRC for each delivered track directly on their release pages. If you distribute through DistroKid, for example, you locate the ISRC by clicking the title of a release on your dashboard to get to the album page, then scrolling down to find it listed. DistroKid has been appointed by the US ISRC Agency to assign codes and generates a new one automatically for every song you upload, free of charge.

Beyond the distributor dashboard, check two more places before reaching for a lookup tool. ISRCs can be embedded directly into WAV, MP3, FLAC and other audio file metadata, and mastering or tagging tools often show this field. If those come up empty, that's when a paste-a-link ISRC finder for Spotify or Apple Music earns its keep, one track at a time. Keep a running spreadsheet as you go: artist, title, ISRC, and source (distributor, file tag, or lookup tool). You'll need it in step 4.

Step 2: audit your files against your catalog (30 minutes)

A spreadsheet of codes is only useful if you know which files it actually matches. This is the step most ISRC finder tools skip entirely, because they only ever see one track at a time and have no view of your library as a whole.

Connect your music folder to TrackTag's My Library view and it indexes every file locally, marking each one Tagged or Untagged with sortable columns and folder aliases so you can see gaps at a glance. The scan itself never leaves your machine: file names and sizes are read locally, and nothing uploads until you explicitly analyze a track. That distinction matters when you're auditing a catalog you don't want sitting on someone else's server before you've even confirmed what's in it. Browser folder access works in Chrome, Edge and Brave; if you're on Safari or Firefox, or you want folders to stay connected without repeated permission prompts, the desktop app for Mac and Windows handles that.

Cross-reference the Untagged list against your ISRC spreadsheet from step 1. Any file with no ISRC and no tags is a genuine backlog item, not just a paperwork gap.

Step 3: fill the metadata gap an ISRC finder can't close

An ISRC tells a platform which recording it's looking at. It says nothing about what the recording sounds like, and that's exactly the information sync licensors, playlist curators and marketplaces ask for next. This is where a catalog audit stops being an ISRC problem and becomes a tagging problem.

Run the Untagged backlog through TrackTag Studio batch audio analyzer. Core analysis returns the 9 fields that file and find a track (BPM, key, genre, subgenres and keyword tags) for 1 credit per track. Ultra returns all 35 fields, including instruments, vocals, song structure, production notes and a full written description, for 2 credits. Both run the same engine on the same audio, so Ultra isn't more accurate, it's just more complete; you can always send a Core track back through for Ultra later for the 1-credit difference. BPM and key come from Precision Mode, which measures both directly from the audio signal rather than guessing, benchmarked at 15 out of 15 tempo agreement against the leading industry analyzer, so the numbers you attach to each ISRC hold up under scrutiny.

If you're prepping specifically for sync submissions, the workflow for what fields actually matter to music supervisors is covered in the sync licensing tagging guide. For the mechanics of running hundreds of files through at once, see the batch tagging guide.

Step 4: export a delivery-ready sheet (30 minutes)

Once your backlog is tagged, merge the two datasets: ISRCs from step 1, tag fields from step 3. TrackTag Studio exports as TXT, CSV/Excel, XML, JSON (including schema.org JSON-LD), Markdown or PDF, as a whole batch, a hand-picked subset, or one file per track zipped up. Export to CSV, add your ISRC column, and you have a single sheet that answers both questions a distributor, sync agent or catalog buyer will ask: which recording is this, and what does it sound like. The catalog submission guide walks through what a buyer-ready delivery sheet typically needs beyond tags and codes.

Step 5: automate the next intake

The checklist above fixes today's backlog. The point of automation is to stop having a backlog next quarter. If you take deliveries from other artists or labels, the public API lets you POST a track on upload and get the same JSON analysis back, at 10 requests per minute and 2,000 analyses per day per key by default, so new files get tagged the moment they land instead of piling up. The Zapier integration adds an Analysis Finished trigger and an Analyze Track action, so a new file dropped in Dropbox can be tagged automatically and logged into the same Google Sheet or Airtable base where you're already tracking ISRCs. For quick lookups while you work, the MCP server lets Claude Desktop or Cursor analyze a track or search your local files by name from inside a conversation, without leaving your editor.

Quick checklist recap

Check your distributor dashboard and file metadata before searching anywhere else. Audit your files against your ISRC list using a library index, not memory. Tag whatever's left in the Untagged pile. Export ISRCs and tags into one sheet. Wire up the API or Zapier so this stops being a recurring afternoon. That's the whole job, and it fits in one sitting.