01
Paste the code
Dashes, spaces, lower case and a leading ISRC label all come out on the way in. The twelve characters are then checked segment by segment, so a bad code tells you which part is wrong.
Paste an ISRC and get the recording it belongs to on Spotify, checked character by character on the way. Paste a Spotify track link instead and get its ISRC back.
Looking it up on Spotify.
No release on Spotify carries this code. Spotify is a store rather than the ISRC registry, so a code that is genuinely assigned can still come back empty here.
A well formed ISRC does not prove the code is registered or that it is yours. Your own assigned codes live in your dashboard, as our codes guide explains.
Pick what describes the recording you are about to release.
The structure check runs entirely in your browser. The lookup is the one part that needs Spotify, and the code or the track id is all that goes to our server. Nothing is stored either way.
Dashes, spaces, lower case and a leading ISRC label all come out on the way in. The twelve characters are then checked segment by segment, so a bad code tells you which part is wrong.
A share link, a spotify: URI or a bare track id all work. The tool reads the id, asks for that recording and hands back the ISRC Spotify holds for it, ready to copy.
A well formed code gets looked up. If a release on Spotify carries it, you get the artwork, the artists, the album and the release date, with a link to open it.
An ISRC is the International Standard Recording Code, the permanent identifier for one recording. It is always twelve characters: two letters for the country of whoever registered it, three letters or digits for the registrant itself, two digits for the year the code was assigned, and five digits for that recording's own number within the year. US-RC1-76-07839 and USRC17607839 are the same code, written with and without the dashes that exist only to make it readable.
Codes are not bought one at a time from a central shop. The IFPI runs the standard and appoints a national agency in each country, the agency issues a three character registrant code to a label or a distributor, and the registrant assigns the year and the last five digits itself. If you release through a distributor, your ISRCs are assigned for you and appear in your dashboard alongside each track. Labels that register directly hold their own registrant code and number their recordings themselves.
One recording keeps one ISRC for life, on every store and in every territory. That is the whole point of it: royalties, charts and radio logs all match plays back to a recording through this code. Anything audibly different is a different recording, so a remaster, an edit, a live take or a new mix each need a code of their own. The release those recordings sit inside is a separate thing again, identified by a UPC or EAN barcode.
The lookup runs in both directions, which is what makes it useful when you only hold half the picture. A code somebody sent you resolves to the recording it belongs to, so you can check it is the one you think it is before it goes on a form. A track that is already live resolves back to its ISRC, so you can read the code off a release without asking anyone for it. One caveat on both directions: this reads Spotify, which is a store rather than the ISRC registry, so a valid code with no Spotify release behind it comes back empty.
An ISRC is the International Standard Recording Code, a twelve character identifier for a single recording. It stays with that recording for life, wherever it is released and however many times, and it is what stores, charts and royalty systems use to tell one recording from another.
Reading USRC17607839 left to right: US is the country of the registrant, RC1 is the registrant code issued to that label or distributor, 76 is the year the code was assigned, and 07839 is the recording's own number within that registrant and year. The dashes in US-RC1-76-07839 are a display convention and carry no meaning.
Copy the track's share link, switch this tool to the Spotify link mode and paste it in. The ISRC comes back with a copy button, along with the artwork and release details. If it is the URI or the raw id you need rather than the ISRC, our Spotify URI finder handles that side.
No, and the difference matters. The structure check only proves the twelve characters are shaped the way the standard requires. Anyone can type a code that passes. The lookup goes further by finding a real release that carries it, but Spotify is a store rather than the ISRC registry, so a code that is genuinely assigned to a recording that is not on Spotify comes back with nothing.
Yes. The same recording re-released as it is keeps its original code. Anything audibly different counts as a new recording and needs its own ISRC, including remasters, radio edits, extended mixes, live takes and re-recordings. Getting this wrong splits or merges your royalties in ways that are slow to unpick later.
The ISRC identifies a recording, the UPC identifies the release it ships inside. A five track EP has one UPC and five ISRCs. Our UPC and EAN checker does the same job as this page for the barcode half, including the check digit maths.
Different store, different identifiers. Apple does not publish the ISRC on its web pages, so a music.apple.com link cannot be read for one here. Our Apple Music artist ID finder covers the identifier Apple's own forms do ask for, which is the numeric artist id.
The structure check is a pure string operation and never leaves your browser. The lookup needs Spotify, and the only thing sent to our server is the code itself, or the track id pulled out of a link. No names, no files, no account, and nothing stored on either side.
Yes. Free to use, no account, no caps, and no Spotify login involved. It is a utility we build for artists and labels preparing releases.
Unchained assigns the ISRC for every track and the barcode for every release, and both sit in your dashboard from the moment you deliver. Plus royalty splits, playlist pitching and real support when something needs fixing.