One wrong digit, one bounced release. Check the codes.
Paste ISRCs and UPCs — one per line, mixed is fine. ISRCs get structure-checked; UPC/EANs get their check digit recomputed. Typos surface here instead of in a distributor rejection email.
Nothing is uploaded — your audio never leaves your device.
| Code | Type | Verdict | Detail |
|---|
Codes are plumbing. Placement is the point.
SongPlaylists in the studio handles the release machinery and the growth after — pitching, playlists, momentum. Sign up: 3 full packs free.
Frequently asked questions
What does a valid ISRC look like?
Twelve characters: two-letter country code, three-character registrant, two-digit year, five-digit designation — like USRC17607839, often displayed with dashes. There's no check digit in an ISRC, so validation means structure: right lengths, right character classes, plausible year.
How does UPC validation work?
UPC-A (12 digits) and EAN-13 carry a mod-10 check digit — the last digit is computed from the others. The tool recomputes it: mismatch means a typo somewhere, guaranteed. That's a real mathematical check, not a guess.
Do I need to buy ISRCs and UPCs?
Usually not — most distributors assign both free when you release through them. You need your own only if you want codes that stay yours across distributors (labels do this via their national ISRC agency and GS1 for barcodes).
Can the validator tell if a code is registered to someone else?
No — that requires the global registries, which aren't publicly queryable in real time. This checks that a code is well-formed, which catches the overwhelmingly common failure: transcription typos.