Find ISRC Code, Step by Step for Your Music Catalog

If you manage more than a handful of tracks, you already know the moment: a distributor rejects a delivery, a royalty statement doesn't match, or a sync request asks for a code you can't locate. This guide covers how to find ISRC code for a track you released yourself, and how to look one up for a recording you don't own, without guessing or duplicating codes that already exist.

What an ISRC Actually Identifies

An ISRC is not a song title or a catalog number you assign yourself. An ISRC is a 12-character ISO 3901 identifier that uniquely tags one specific sound recording, with the first two characters as the country code, the next three as the registrant, the next two as the year, and the last five a unique recording number. Two details matter more than the format itself.

First, the code identifies the recording, not the composition. An ISRC identifies sound recordings, not the song itself, while songs are identified by ISWC codes, so different recordings, edits, remixes and remasters of the same song will be assigned their own ISRC. Second, once it's set, it's permanent. Once a code is encoded, it should never be changed, even if the rights to the recording are transferred to a new owner, and there is only ever one ISRC code for every song's given recording. That permanence is exactly why finding the right one matters more than finding one fast.

How to Find the ISRC Code for a Track You Released

If the recording is yours, the code already exists somewhere in your paperwork. Work through these in order:

1. Check your distributor dashboard. Most distributors assign and display the ISRC at the release or track level as soon as you submit metadata.

2. Check the delivered audio files. Distributors and mastering engineers frequently embed the ISRC directly in the file's metadata tags before delivery.

3. Check your label or publisher's release sheet. Encoding is usually left to mastering engineers, record label staff, digital distributors, or CD manufacturers, so you shouldn't have to do the encoding yourself, but you will in most cases have to get the code from them.

4. Search the official registry as a fallback. The IFPI maintains the authoritative record. The International ISRC Database contains over 150 million unique ISRCs registered with associated recording and release data, and it is searchable by artist and title or by entering the ISRC directly.

If you're prepping a batch of releases for a distributor or licensing partner, this is also the point to line up your metadata all at once rather than track by track. Our guide on how to prepare a catalog for library submission walks through the full checklist, ISRCs included.

How to Find the ISRC of a Track You Don't Own

For recordings outside your own catalog, is a competitor's release, a sample source, a track you need to license, use the public and semi-public databases rather than a random link-paster:

1. IFPI's official search. ISRC search is a database of international recording data, providing sound recording data to those searching for the corresponding ISRC codes to be used for their recordings. It supports both name search and direct code lookup.

2. SoundExchange's database. SoundExchange ISRC Search is a database of nearly 20 million ISRC codes, useful for US-registered digital performance recordings.

3. MusicBrainz. A community-maintained, open database that often carries ISRCs alongside release credits and is genuinely useful for cross-checking a code you already found elsewhere.

4. Streaming platform lookup tools. You cannot see the ISRC directly inside the regular Spotify app, however, Spotify exposes ISRCs via its Web API, which is what most "paste a Spotify link" finder tools are quietly querying on your behalf.

One honest caveat before you trust the first result: asking for the ISRC of a song is often a question with more than one right answer, because searching by title can easily return a different code than the one printed on the specific release you're holding, and neither is wrong, so whenever a code has to line up with a play log, royalty statement, or delivery, match the exact version and release, not just the song title.

Why the Same Song Can Return Different Codes

This trips up more catalog managers than any other ISRC issue. Every unique recording of a song, album version, radio edit, remix, live recording, remaster, or language version, should have its own ISRC, which allows platforms and royalty systems to distinguish between them and attribute usage correctly. Cross-source disagreement isn't a bug in whichever database you're using. Cross-source disagreement about "the" ISRC of a track is normal, not a data bug. When you find an ISRC, record which specific edit it belongs to alongside it, not just the artist and title.

What an ISRC Can't Tell You About the Track

Here's the part most ISRC finder tools skip entirely: the code is an administrative key, not a description. It tells a royalty system which recording earned a play. It tells you nothing about tempo, key, mood, instrumentation, or whether the track actually fits a sync brief. If you're licensing music, an ISRC gets a track paid correctly, but a supervisor still needs to know it's a 92 BPM, minor-key track with a cinematic, hopeful mood before they'll shortlist it. That's a separate metadata layer, and it's the one most libraries neglect until a submission deadline forces the issue. Our guide to tagging music for sync licensing covers what that layer needs to include.

Building the Full Catalog Record: ISRC Plus Audio Tags

Once you've matched the right ISRC to the right recording, the practical move is to attach it to a metadata record that actually describes the track. That's where TrackTag Studio batch audio analyzer fits into the workflow. Drop your files in and TrackTag Studio returns up to 35 fields per track, BPM and key measured directly from the audio signal (not guessed), plus genres, moods, instruments, vocals, structure, and a written description, then export everything as CSV, XML, or JSON alongside whatever identifiers you already track, ISRC included.

If you're clearing a backlog, My Library connects a local folder and shows every file as Tagged or Untagged, so you can run an "Analyze untagged" pass on exactly the tracks missing descriptive metadata, while your ISRCs stay wherever your delivery system already keeps them. For teams doing this at scale, our walkthrough on batch tagging music files covers folder structure and export formats in more depth.

The two workflows connect naturally: the API lets a distributor or marketplace auto-tag uploads the moment ISRCs are assigned, the MCP server lets you ask an AI assistant to analyze or search local files by name mid-conversation, and the Zapier integration can push a finished analysis straight into the same Google Sheet or Airtable base where you're tracking codes. None of that replaces the ISRC lookup itself, but it means the code and the description end up living in the same record instead of two disconnected systems.

Find the code through the official databases above, confirm it matches the exact version you're delivering, and pair it with real audio metadata so the record is actually useful once it's found.