Beta founding offer: lock in 50% off any plan for life, before the beta ends. Claim founding pricing →
ISRC codes, honestly

There is no real
ISRC generator

Any tool can output twelve characters in the right shape. What it can't do is register them. Here's how ISRCs are actually assigned, how to get yours for free, and how to find the code your track already has.

By Christiaan Maks, Founder & DeveloperUpdated

The short answer

ISRCs are assigned, not generated

An ISRC is only meaningful because a specific registrant, a label, distributor, or ISRC agency, allocated it to one recording and logged it. A random "generator" can copy the format, but it cannot register anything.

That distinction is the entire point of the system. Collecting societies and streaming platforms trust an ISRC because they can trace its registrant prefix to the company that issued it. A code minted outside that chain, however well-formed, routes no royalties and identifies nothing. If a generator page hands you a code, what you have is a string, not an identifier.

The real routes

Three ways to get a real ISRC

Every legitimate ISRC arrives through one of three doors, and for most artists the first one is free and automatic.

Your distributor assigns one (free)DistroKid, TuneCore, CD Baby, and every other mainstream distributor assign an ISRC automatically when you upload a release, at no extra cost. For most independent artists this is the answer: you never need to touch a generator, the code arrives with the release.
Your label mints oneLabels hold a registrant code and assign ISRCs to their own releases from it. If a label is releasing your track, the ISRC is their job, minted under their registrant prefix.
You become a registrant yourselfIf you release a lot of music and want control, apply to your national ISRC agency (usisrc.org in the United States, or the agency for your country) for your own registrant code. You then assign codes to your recordings under that prefix, following the format rules.
Why not fake it

What a generated ISRC breaks

Royalty routing fails

SoundExchange, PPL, and the other collecting societies match plays to recordings by ISRC. A code that was never registered to you routes nothing, and can collide with someone else's recording.

Distributors and DSPs reject or replace it

Distributors validate ISRCs at ingestion. A code minted under a registrant prefix you don't control is either rejected or silently replaced, and the code you wrote on your masters no longer matches what's live.

Collisions poison catalogs downstream

If your invented registrant prefix belongs to a real label, your "generated" code may already identify one of their recordings. Metadata databases then see one ISRC pointing at two different tracks, and both suffer.

It's permanent

An ISRC is assigned once and embedded everywhere the recording goes. Shipping a release with a made-up code is not something you can quietly fix later; the bad code travels with every copy.

Released already? Your track has a code. Find it.

If your music is on Spotify, Apple Music, or any other platform, your distributor already assigned it an ISRC. Look it up by artist and title with the free finder, check any code's format with the validator, or decode who issued it from its registrant prefix.

Free ISRC lookupISRC validator & decoderRegistrant code reference
FAQ

Questions people ask about generating ISRCs

No. Tools that output "generated" ISRCs only produce strings that follow the format: two letters, a three-character registrant, and seven digits. The format is the easy part. What makes an ISRC real is that its registrant code was allocated to an actual issuer by an ISRC agency, and that the issuer logged the code against a recording. No web tool can do that for you.
Release through a distributor. DistroKid, TuneCore, CD Baby, and the rest assign ISRCs automatically as part of the upload, at no extra cost. That is the normal route for independent artists, and the reason most musicians never deal with an ISRC agency directly.
You can type one, but it identifies nothing. The registrant portion of the code belongs to a specific company; a code under a prefix you don't hold is either unregistered (routes no royalties) or collides with a real recording owned by someone else. Either way, collecting societies and DSPs treat it as bad data.
Almost certainly yes, assigned by whoever distributed it. You can find it with the free ISRC lookup on this site: search by artist and title, and the code your release actually carries comes back. That code, not a generated one, is what you should use on royalty registrations and reporting.
Country (2 letters), registrant (3 characters), year (2 digits), designation (5 digits). The registrant code is the part you cannot invent: it is allocated by an ISRC agency to a specific label, distributor, or artist who applied for it. Everything after it only means something inside that registrant's own numbering.
It's worth it if you want your codes minted under your own prefix rather than your distributor's. In the United States you apply at usisrc.org; other countries have their own national agency. Once allocated, you assign codes yourself and keep your own register of what each designation number refers to.

Working with ISRCs at scale?

The SonoVault API resolves ISRCs to canonical recordings with cross-platform IDs, and finds the ISRC behind an artist and title, across 90M+ tracks. One API key, free tier included.

ISRC lookup for developersView the API docs →