General information, not legal or financial advice. This is a US-focused, education-first guide to ISRC codes — what they are, how to get one, and the mistakes that cost people money. Agencies, fees and rules change, and they differ entirely outside the US, so treat every specific figure here as accurate as of mid-2026 and a starting point to verify on the agency’s own site before you pay or apply. It is not a substitute for advice from a music attorney or your distributor’s support team about your own catalog.
An ISRC (International Standard Recording Code) is a permanent 12-character fingerprint for a single sound recording — one specific master. You almost never need to buy or apply for one: every major distributor (DistroKid, TuneCore, CD Baby and the rest) assigns ISRCs free when you upload, and that is the right route for nearly everyone. Self-registering your own prefix from the US ISRC Agency costs a one-time ~$95 and only makes sense for labels and prolific releasers. The three things that actually matter: never pay a per-code reseller, give every new version of a song its own ISRC, and always carry your existing codes forward when you change distributors — re-minting them makes platforms treat your catalog as brand-new and can wipe your streaming history.
Almost every guide to ISRC codes gets the framing wrong before it starts, because it treats “getting” a code as a quest you have to go out and complete. For the overwhelming majority of artists, you never get an ISRC at all — your distributor mints one for free the moment you upload, and you could release music for a decade without ever touching the process directly. So if the real action isn’t in acquiring a code, where is it? It’s in the three things nobody puts on the “how to get an ISRC” page: not paying a reseller for something you get free, understanding that every version of a song needs its own code, and — the one that actually costs people real money — carrying your existing codes with you when you switch distributors instead of letting a careless re-upload erase your stream counts, playlist placements and saves overnight.
This guide is built around those gotchas rather than the trivial mechanics. We’ll define the ISRC precisely and show you how to read one, untangle it from the UPC and ISWC that producers constantly confuse it with, walk the three legitimate routes to a code and when each makes sense, and then spend the most time on the part that matters: protecting the data your catalog has already earned when you move it. The companion piece to bookmark alongside this one is our overview of music metadata, where the ISRC sits among the dozen other fields that decide whether your release is found and paid; this article is the deep dive on the single most important of those fields.
What an ISRC actually is
An ISRC is a globally unique, permanent identifier for one sound recording. It is a 12-character alphanumeric code, defined by the international standard ISO 3901, and administered worldwide by the IFPI — the International Federation of the Phonographic Industry — which appoints a national agency in each territory to allocate codes. In the United States that agency is operated by the RIAA. The job of the code is narrow and specific: it says “this exact recording, this particular master, is distinct from every other recording on earth.” Not the song, not the album, not the artist — the recording. That precision is the whole point, because it is what lets a streaming service, a collection society, a radio monitor or a chart compiler look at a play and know with certainty which of the millions of tracks in the system just generated money, so that the money routes to the right owner instead of disappearing into an unmatched pool.
This is why the framing “how do I get one” is slightly misleading. You do not need to acquire an ISRC the way you acquire a business licence; you need each recording to carry one by the time it reaches the platforms, and the distributor you use to reach those platforms will attach a valid code automatically unless you tell it to use yours instead. Every distributor that matters — DistroKid, TuneCore, CD Baby, LANDR, Ditto, AWAL and the rest — does this as a standard part of delivery, at no extra charge. If your entire interaction with ISRCs is “I uploaded a song and a code appeared in my dashboard,” you have done it correctly and you can stop reading the parts about self-registration. The reason this guide goes further is that a few situations — running a label, releasing constantly, or moving an existing catalog — reward understanding the code rather than just letting it happen to you.
It helps to be able to read one, because the structure tells you something useful and exposes a common misconception. The code breaks into four conceptual parts: a five-character prefix that identifies the registrant who owns the code, a two-digit year of reference, and a five-digit designation that uniquely numbers the recording. The diagram below dissects a worked example so you can see each segment do its job.
Two details in that anatomy regularly catch people out. The first is the year: it records the year the ISRC was assigned, not the year the song was recorded or released, so a 2026 code on a track you wrote in 2019 is correct, not a mistake. The second is more current and almost never mentioned: the 2019 revision of ISO 3901 retired the old “country code plus registrant code” split and now treats those first five characters as a single allocated prefix block with no fixed geographic meaning. US registrants may receive prefixes beginning US, QM, QZ or QT — so a code that doesn’t start with “US” is not necessarily foreign or wrong. If you ever audit your catalog and panic at a QZ prefix, that’s why; it is a perfectly normal US allocation.
ISRC vs UPC vs ISWC, untangled
The most common and most expensive confusion in this whole area is treating three different codes as if they were variations on one. They are not interchangeable, and they are not even a clean hierarchy — they identify three different things that happen to travel together. Getting them straight is the difference between an operator who knows where each royalty comes from and an amateur who wonders why half their income never shows up. The ISRC, as we’ve established, identifies a recording. The other two identify a release and a composition, and each is issued by a completely different body.
A UPC (Universal Product Code) identifies a release as a product — the single, EP or album that you actually put into stores, the unit a shop or a DSP treats as one item for sale. It’s the same kind of barcode number that sits on a box of cereal, issued by the global standards body GS1, and in music it answers “which product is this.” The key relationship to memorize is that one release carries one UPC no matter how many tracks it holds, while every track inside it carries its own ISRC. A ten-song album is one UPC wrapping ten ISRCs. A standalone single is still one UPC and one ISRC. Like the ISRC, your distributor assigns a UPC for free at upload, and the only reason to buy your own from GS1 is to run a serious catalog under your own barcode prefix.
An ISWC (International Standard Musical Work Code) identifies the composition — the song as written, the melody and lyric that exist independently of any particular performance of them. It is administered globally by CISAC and assigned by your performing rights organization (ASCAP or BMI in the US, for instance) when you register the work, which is a different process from distribution entirely. The defining property is that a single composition keeps one ISWC forever, no matter how many times it is recorded: think of a standard like “Folsom Prison Blues,” which has one ISWC for the song but dozens of ISRCs for the studio cut, the live versions, and every cover. The ISWC routes the songwriter’s side of the money, the part your distributor never touches, which is exactly why understanding music publishing as separate from distribution matters so much. The map below lays the three codes side by side.
Once the three are distinct in your head, a lot of downstream confusion dissolves. You stop wondering why your distributor doesn’t collect your songwriting royalties (different code, different body), why a remaster needs a new ISRC but keeps the same ISWC (new recording, same composition), and why a deluxe edition of an album gets a new UPC (new product) even though most of its tracks keep their original ISRCs (same recordings). These codes operate in parallel, each answering a different question, and the money only fully reaches you when all three are correct and linked. If you’re mapping out a first release, our guides on how to distribute music and how to register your music show where each code enters the workflow.
The three ways to get an ISRC
There are exactly three legitimate routes to an ISRC, and the honest truth is that almost everyone should take the first one. The reason this section exists is not to present them as equal options to weigh, but to tell you plainly which fits your situation so you don’t over-engineer a non-problem or, worse, get talked into paying for something free. The diagram lays out all three with their real tradeoffs; the text walks each one.
Route one — let your distributor assign it. When you upload a release through any reputable distributor, it generates and attaches a valid ISRC to every track as part of delivery, free, instantly, with nothing for you to manage. The codes are real, recognized everywhere, and there is no asterisk: a song that gets famous on a DistroKid-assigned ISRC is no less legitimate than one on a code you registered yourself. For an artist releasing singles and the occasional EP, this is not just the easy option, it is the correct one. If you’re choosing a distributor, our comparison of DistroKid vs CD Baby and our DistroKid review walk the current options, and every one of them handles ISRC assignment for you.
Route two — register your own prefix. If you want to own and control your codes rather than have a vendor issue them, you can self-register with the US ISRC Agency for a one-time administrative fee of around $95 as of mid-2026. That fee buys a registrant prefix — the five-character block at the front of every code you’ll create — which is yours for life and lets you assign up to 100,000 ISRCs per calendar year to recordings you own, at no further cost. This only makes sense for two kinds of people: labels managing many artists’ catalogs, and prolific releasers who want their codes’ identity to belong to them and travel with them across any distributor. For everyone else it is overkill, because you take on the responsibility of tracking your own assignments and avoiding duplicates in exchange for control you may never need. Verify the current fee on the agency’s own site before applying, since it is exactly the kind of figure that moves.
Route three — your label assigns it. If you’re signed, the label issues codes from its own registrant prefix as part of releasing your record, and there is nothing for you to do except confirm the codes end up correctly attached to your metadata. This is the same mechanism as route two, just operated by someone else on your behalf. And then there is the route that is not on the diagram because it shouldn’t exist in your life at all: never pay a per-code reseller. The US agency is explicit that companies claiming to sell individual ISRCs without authorization are issuing invalid codes that risk colliding with someone else’s — and you already get valid codes free from any distributor. If a site offers to sell you ISRCs for a couple of dollars each, that is a tax on confusion, and now you’re not confused.
The rule that trips everyone — a new version is a new recording
Here is the single rule that generates more support tickets and mismatched royalties than any other: a new version of a song is a new recording, and a new recording needs a new ISRC. The studio version, the radio edit, the clean (lyric-censored) version, the acoustic take, the live recording from a show, a remaster done years later, and any remix all count as distinct recordings, and each one must carry its own distinct code. This is not bureaucratic pedantry — it is how the system keeps the streams and royalties for your acoustic version from being credited to your studio version, and how a sync supervisor licensing “the live take” references precisely the recording they mean. If you put out a deluxe edition where the original tracks are remastered, each remastered track is technically a new recording and needs a fresh ISRC.
The flip side of this rule is where people make the opposite mistake, and it is just as costly. The same master delivered to Spotify, Apple Music, Amazon, YouTube and every other platform keeps the same ISRC on every one of them. You do not generate a new code per platform, per country, or per format — one recording carries one ISRC for its entire life, everywhere it appears. The ISRC is a property of the master, not of the delivery. So if you ever find the same recording sitting under two different ISRCs, something has gone wrong: the platforms now see two recordings where there is one, your play counts are split between them, and you have a deduplication problem to untangle. The codes only do their job when one master maps to exactly one code, no more and no fewer.
Note that the composition’s ISWC follows a parallel but different logic, which is worth holding in mind so you don’t over-apply the ISRC rule. A remaster or a new recording of the same song keeps the same ISWC, because the composition hasn’t changed even though the recording has. The exception is when the songwriting itself changes — a rewrite with different splits or a substantial adaptation can be a new work warranting a new ISWC. The clean mental model: change the recording and you change the ISRC; change the song and you may change the ISWC. Keep those two axes separate and the version question stops being confusing. If versions and rights are new territory, our primer on how to copyright your music covers the ownership layer underneath all of this.
Switching distributors without erasing your streams
This is the section that justifies the whole article, because it is the one place where an ISRC mistake costs you something you cannot get back: your accumulated streaming history. Almost everyone switches distributors eventually — for better rates, better features, or simply because a service shuts down or annoys them — and the migration is genuinely safe if you do one thing right and genuinely destructive if you don’t. The thing is this: you must carry your existing ISRCs and UPCs forward to the new distributor. Skip it, and the damage is immediate and largely irreversible.
Here is the mechanism, because understanding it is what makes you careful. When you move to a new distributor and re-upload your catalog without supplying the original codes, the new distributor does what it always does for a new upload: it mints fresh ISRCs and a fresh UPC. The streaming platforms then look at those tracks, see codes they’ve never encountered, and conclude — correctly, from their point of view — that these are brand-new recordings and a brand-new release. The consequence is that a duplicate of your song appears alongside the original, your play counts and save history are split or stranded on the old version, the “popularity” signals that drive algorithmic recommendation reset to zero, and any editorial or algorithmic playlist placements that pointed at the old version are simply gone, because the thing they pointed at no longer matches what’s live. Years of compounding can evaporate in a single careless migration.
The fix is unglamorous and completely effective. Before you migrate anything, export or screenshot every ISRC and every UPC from your current distributor’s dashboard — most list them under each release’s track details — and save them in a master sheet you control. When you set up the new distributor, enter those existing codes instead of letting it generate new ones; every serious distributor has a field for “I already have an ISRC” and “I already have a UPC” precisely for this. Then keep the rest of the metadata identical: same track titles, same spellings, same featured-artist credits, same release date where the platform allows. The platforms match on a combination of the codes and the metadata, so a mismatch in either can still trigger the “new release” behavior even when the codes are right. Match everything, and the platforms recognize the move as a hand-off of the same release rather than the birth of a new one.
There is one more piece of sequencing that trips people even when their codes are perfect: the order of operations. Do not take your catalog down at the old distributor before the new delivery is live and confirmed. Set up the new distributor with your existing codes, let the release go live, and verify on each platform that the move landed on the same recording — same ISRC, intact stream count, playlists still attached — and only then issue the takedown at the old distributor. Pulling the old release first creates a window where the track is gone, and a gap in availability is itself a signal that can cost you algorithmic momentum and placements. Migrate by overlapping the two, confirm the hand-off, and retire the old delivery last.
This is also the clearest argument for route two above. When your codes are issued under your own registrant prefix, they belong to you rather than to a distributor, so the question “will my codes survive the switch” never even arises — they’re yours, and you simply hand them to whoever delivers your music next. For a hobbyist that ownership isn’t worth the admin, but for anyone with a catalog that earns real money and expects to outlive its current distributor, the portability is exactly what the $95 buys. Either way, the discipline is the same: know your codes, keep a record of them, and never let a re-upload silently re-mint them. For the broader picture of how those streams turn into money in the first place, our explainer on how music royalties work and the deeper dive into streaming royalties set the context.
Embedding the code so it travels with the file
An ISRC lives in two places, and most people only think about one of them. The primary home is your distributor’s and the platforms’ databases, where the code is linked to your recording’s metadata and used to match plays to payments. But the code can also be embedded directly into the audio file itself, and doing so is a cheap insurance policy that pays off in exactly the moments that matter. Embedding means the identity travels with the file even when it’s passed around outside the streaming system — handed to a mastering engineer, sent to a sync library, delivered to a radio station, or archived for a reissue years later — so the recording always announces what it is.
The mechanics depend on the file format. For a WAV, the ISRC goes into the file’s metadata as part of the Broadcast Wave (BWF) extension, stored in a RIFF chunk that broadcast and professional systems read. For an MP3, it lives in an ID3 tag, the same metadata container that holds the title and artist. You don’t need special software to do this: free, well-known tag editors such as Kid3 and MP3Tag let you write the ISRC field by hand, and many professional mastering engineers will embed the codes as a standard part of delivery if you give them to them — which is one good reason to have your ISRCs assigned before the master is finalized rather than after. At the delivery layer, the modern supply chain uses DDEX standards to carry the ISRC alongside the audio when distributors hand releases to platforms, but that part is handled for you; the file-level embedding is the piece you can control directly.
In day-to-day practice, embedding is belt-and-suspenders rather than strictly required — the distributor’s database is what the platforms actually pay against — but the cost is a few minutes and the payoff is that your recording is never anonymous. A file that knows its own ISRC is dramatically easier to reconcile when it surfaces in a context the streaming system doesn’t cover, and it removes an entire class of “wait, which version is this” problems from your future. If you’re building good habits around your masters, treat embedding the code the same way you treat backing up the project file: small effort, large protection.
Charts, and when you genuinely don’t need one
If charting or serious analytics are anywhere in your plans, the codes stop being optional housekeeping and become eligibility requirements. Chart compilers and the data services behind them — Billboard and the Luminate data that feeds it, the Official Charts in the UK, and the platforms’ own counting — rely on the ISRC and UPC to attribute streams and sales to the right recording and release. Missing or duplicate codes are a frequent reason deliveries get rejected by DSPs or plays fail to count, which is the quiet way a release underperforms its real numbers. Getting your codes clean and consistent isn’t about prestige; it’s the precondition for your music being counted at all, and it’s tightly bound up with the rest of getting a release live, which our guides on getting music on Spotify and landing on Spotify playlists cover from the promotion side.
So when do you genuinely not need an ISRC? The honest answer is narrower than the “you always need one” advice you’ll usually read, but it’s real. A private demo you’re sending to a collaborator, a free SoundCloud upload you have no intention of monetizing, a beat you’re posting purely as a portfolio piece, or any recording you are not distributing for streaming or sale — none of these strictly require an ISRC, because nothing in the royalty-and-chart machine is being asked to track them. If a recording will never enter the commercial supply chain, the code serves no function. This matters for producers especially: not every WAV you make needs to be registered the instant it exists.
That said, the threshold flips the moment commercial intent appears, and it flips automatically. The instant you push a track to Spotify, Apple Music or any store through a distributor — or you decide you want it counted toward charts and royalties — it needs an ISRC, and the distributor assigns one without you asking. Because the code is free through that route and future-proofs the recording, the practical default for anything you might ever release is simply to let it get a code at distribution and keep a record of it. The only real decision is whether a given recording is leaving your hard drive for the commercial world; if the answer is yes, or even a strong maybe, the code question answers itself. If you’re monetizing through other channels too, our guide on selling beats online covers where licensing and codes intersect for producers.
Put it into practice
Three exercises, escalating from “find what you already have” to “plan a migration without losing data.” Do them in order; each builds the muscle the next one needs.
- Open your distributor or label dashboard and locate one of your released tracks under its release or track details.
- Read off its ISRC and note which of the four segments is the prefix, the year of reference, and the designation.
- Cross-check it: look the same recording up in a public ISRC database (such as the IFPI search or SoundExchange) and confirm the code matches.
- Start a master sheet — one row per recording — with the track title, its ISRC, and its release’s UPC. You’ll thank yourself at switch time.
- Take a real or imagined three-track EP and write out how many of each code it uses: how many ISRCs, how many UPCs, how many ISWCs.
- Now add a remix of track two as a bonus cut — update the counts and explain which codes change and which stay the same, and why.
- For one track, identify which body issues each of its three codes (distributor/agency, distributor/GS1, PRO/CISAC).
- Write one sentence explaining which royalty each code routes, so the “why” is locked in, not just the “what.”
- Using your master sheet, export or screenshot every existing ISRC and UPC from your current distributor before touching the new one.
- Draft the exact metadata you’ll re-enter at the new distributor — titles, spellings, credits, dates — so it matches the live release character-for-character.
- Identify, for your chosen new distributor, the field where you supply an existing ISRC and an existing UPC rather than generating new ones.
- Write a one-paragraph migration checklist you could hand to someone else, ending with how you’ll verify on the platforms that no duplicate was created.
Frequently asked questions
No. Every major distributor — DistroKid, TuneCore, CD Baby, LANDR, Ditto and the rest — assigns ISRCs for free when you upload a release, and those codes are fully valid. The only time you pay is if you choose to self-register your own registrant prefix with the US ISRC Agency, a one-time fee of about $95 that buys a prefix for life. You should never pay a per-code reseller a couple of dollars per ISRC: those sellers are usually unauthorized, the codes they issue can be invalid or collide with someone else’s, and you already get the same thing free from any distributor.
An ISRC identifies a single sound recording — one specific master — while a UPC identifies a release as a product, the single, EP or album that bundles one or more recordings. A ten-track album has ten ISRCs (one per recording) and one UPC (for the release). Your distributor assigns both for free at upload. They answer different questions: the ISRC says which recording this is, and the UPC says which product this is. There is also a third code, the ISWC, which identifies the underlying composition rather than the recording.
Yes. An ISRC is tied to a specific recording, so the studio version, the radio edit, the clean version, the acoustic take, the live recording, a remaster and any remix each need their own distinct ISRC. The exception that trips people the other way: the same master delivered to Spotify, Apple Music and every other platform keeps the same ISRC everywhere — you do not mint a new code per platform. One master, one ISRC, everywhere it goes.
The fastest place is your distributor or label dashboard, usually under the release or track details. You can also read it out of the file’s embedded metadata with a free tag editor like Kid3 or MP3Tag, and for already-released music you can look it up in public databases such as the IFPI’s ISRC search or SoundExchange’s repertoire. Keeping a simple master sheet of every ISRC you’ve been assigned saves enormous pain later, especially before a distributor switch.
This is the most expensive mistake in the whole topic. If you re-upload your catalog to a new distributor without supplying your original ISRCs, the new distributor mints fresh codes, and the streaming platforms treat each track as a brand-new recording — a duplicate appears, your play counts and save history split or reset, and playlist placements tied to the old version are lost. Always export or screenshot every existing ISRC (and UPC) before you migrate, give them to the new distributor, and keep the rest of the metadata identical so the platforms recognize it as the same release.
As of mid-2026 the US ISRC Agency, operated by the RIAA, charges a one-time administrative fee of about $95 for a registrant prefix (also called a rights-owner prefix). That prefix is yours for life and lets you assign up to 100,000 ISRCs per calendar year to recordings you own, at no further cost. It only makes sense for labels and artists releasing a lot of music who want full control and portability; for a few singles a year, letting your distributor assign free codes is the better call. Verify the current fee at the agency before applying, since it can change.
An ISWC (International Standard Musical Work Code) identifies the underlying composition — the song as written, its melody and lyric — while an ISRC identifies a specific recording of that song. One composition has one ISWC even if it is recorded a hundred times; each of those recordings gets its own ISRC. The ISWC is administered by CISAC and assigned by your PRO (such as ASCAP or BMI) when you register the work, and it routes the songwriter’s side of the royalties, which your distributor does not collect.
Not necessarily. If a track is a private demo, a free SoundCloud upload you are not monetizing, or something you have no intention of distributing for streaming or sale, it does not strictly need an ISRC. The moment you push it to Spotify, Apple Music or any store through a distributor — or you want plays counted toward charts and royalties — it needs one, and your distributor will assign it automatically. When in doubt, having an ISRC costs nothing through a distributor and future-proofs the recording.