How to Find ISRC Codes: Step by Step Guide

If you manage more than a handful of tracks, you already know the frustrating part of ISRC codes isn't understanding what they are, it's actually locating one when you need it. This guide walks through every reliable way to find ISRC codes, whether you're chasing down a single track or auditing an entire catalog for gaps.

What an ISRC Actually Identifies (and What It Doesn't)

Before you go looking, it helps to know what you're looking for. An ISRC is a 12 character code, structured as country code, registrant code, year, and a five digit designation number. CC is usually the country of the registrant, XXX identifies the company or individual issuing the code, YY is the last two digits of the year the ISRC was assigned, and NNNNN is a five-digit number that uniquely identifies the recording.

The part people miss most often: think of it as the passport number for one particular audio master, not for the song (composition) itself. That means each unique recording of a song, 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. If you're finding the "wrong" ISRC for a track, it's often not wrong, it's just attached to a different version than the one you're thinking of.

Step 1: Find the ISRC for a Track You Released Yourself

If the track is yours, the ISRC already exists somewhere in your delivery chain. Check in this order:

1. Your distributor dashboard. Most distributors assign and display ISRCs automatically. On DistroKid, for example, you click on the title of that release on your dashboard to get to the album page, then scroll down to find the ISRC listed across from the associated track. TuneCore, CD Baby, and similar services follow the same pattern: release page, then track level metadata.

2. Your DDEX delivery report or release spreadsheet, if a label or aggregator handled the upload for you. ISRCs are a required field in DDEX delivery, so they should already be sitting in whatever XML or CSV was generated at ingestion.

3. The file's own embedded metadata. ISRC can live inside the file itself, not just in a database. There is a designated ISRC code "ID3 tag" for an MP3 file which can be edited in using an application post MP3 encoding, and for WAV masters, it is possible to embed metadata in WAV files thanks to the Broadcast Wav File extension, with the ISRC code embedded into the AXML chunk. A tag editor or metadata viewer that reads ID3v2 or BWF chunks will surface it directly from the audio file, no internet lookup required.

Step 2: Find the ISRC for a Track You Don't Own

For tracks outside your own catalog, licensing checks, cover clearance, competitive research, you're relying on platform data rather than your own delivery records.

• Spotify. You cannot see the ISRC directly inside the regular Spotify app, however Spotify exposes ISRCs via its Web API. Several free tools (Soundcharts, Musicfetch, and others) exist specifically to query that API for you: paste a track link, get the ISRC back.
• Music databases. You can use online music databases such as Discogs, AllMusic, and MusicBrainz, which allow you to search for music by ISRC, artist, album, or track name. MusicBrainz in particular is useful because its data is user-contributed and cross-referenced, so it sometimes surfaces ISRCs that a single-platform lookup misses.
• Reverse lookups. If you already have an ISRC and need to confirm which recording it belongs to, some lookup tools support pasting the 12 character code directly to pull back title, artist, and release year.

One honest caveat all of these share: most commercially distributed recordings have an ISRC, but some demos, unofficial uploads, user-generated videos, or incomplete service records may not expose one through public platform metadata. A missing result doesn't always mean a missing code, sometimes it means the platform's public API just doesn't surface it.

Step 3: Find Every ISRC Across a Whole Library, Not Just One Track

Single-track finders solve a one-off question. They don't solve the actual problem library owners face: hundreds or thousands of files, some with ISRCs embedded, some only in a distributor's spreadsheet, some missing entirely, and no way to see which is which without opening each file.

The practical workflow is a two-pass audit:

1. Scan for what's already embedded. Run a batch metadata viewer or tag editor across the folder to pull ID3v2 TSRC or BWF fields at once. This gets you a list of files that already carry an ISRC without touching your distributor account.

2. Cross-reference against your delivery records. Match that list against your distributor's export or DDEX report. Anything present in your delivery data but missing from the file itself is a candidate for re-embedding. Anything missing from both is a genuine gap, likely an unreleased track, a pre-release master, or an older file from before you standardized delivery.

This is the same "what's covered, what isn't" logic that matters for any catalog metadata, not just ISRCs. If you're already running that kind of audit on a folder, it's worth doing it once for every field that makes a track findable and deliverable, not just the identifier.

Step 4: Fix the Gap ISRC Lookup Tools Never Solve

Here's the part every ISRC finder skips: an ISRC tells a system which recording it is, it says nothing about what the recording sounds like. Once you know a track has (or needs) an ISRC, you still need the descriptive metadata that makes it usable, BPM, key, genre, mood, instrumentation, and searchable keywords, especially if you're prepping the catalog for sync licensing submissions or a distributor or library submission.

This is where TrackTag Studio batch audio analyzer fits into the workflow. You drop the same batch of files you just audited for ISRC gaps, and TrackTag Studio returns the file-and-find fields (BPM, key, genre, mood, instruments, and more) that turn a folder of numbered masters into a catalog someone can actually search. BPM and key come from Precision Mode, measured directly from the audio signal rather than guessed, so the numbers you attach next to each ISRC are accurate, not estimated. If you're processing a large batch, the batch tagging guide covers the workflow in more depth.

Keep ISRCs and Catalog Tags in Sync Going Forward

Once a library is audited, the goal is to stop re-auditing it manually every quarter. A few ways to keep ISRC and descriptive tagging aligned as new files come in:

• My Library connects a local folder and shows every file as Tagged or Untagged, so new deliveries with missing descriptive tags surface immediately alongside whatever ISRC gaps you're tracking separately.
• The desktop app keeps folders connected permanently, useful if your catalog lives on a drive that Safari or Firefox can't read directly, since browser folder access only works in Chrome, Edge, and Brave.
• The API and MCP server let you fold tagging into an existing pipeline: a marketplace auto-tags uploads on delivery, a label enriches tracks the moment ISRCs are assigned, or an AI assistant like Claude Desktop checks a file's tags without leaving the conversation.
• Zapier connects the "Analysis Finished" trigger to a spreadsheet or Airtable base where you're already tracking ISRCs, so both identifiers land in the same row automatically.

Finding an ISRC is a five-minute task for one track. Finding every ISRC gap across a real catalog, and closing the descriptive metadata gap next to it, is the actual job. Treat both as one audit instead of two separate chores, and your library stops losing tracks to missing identifiers or missing tags.