ISRC guide
Rights workflows should be documented before release, not reconstructed during a dispute.
- Save license PDFs or screenshots with timestamps.
- Keep split sheets and contributor approvals in the project folder.
- Record territory, term, allowed uses, and payment terms for each asset.
This is operational education for producers, not legal advice. For a signed deal, dispute, takedown, or high-value sync, ask a qualified music lawyer in the relevant territory.
ローカルな文脈
法律、税務、プライバシー、権利、ロイヤリティ、契約のルールは管轄によって異なります。この記事は編集上の出発点であり、法的または会計上の助言ではありません。
行動する前に、お住まいの国の現地法、支払い方法、プラットフォームの利用可否、税金、音楽権利の管理を確認してください。
クイック回答
ISRC guide: An ISRC is the identifier for a specific recording version. Use one ISRC per final master, keep it consistent across distributors, and assign a new one when the audio version materially changes. This is operational education for producers, not legal advice. For a signed deal, dispute, takedown, or high-value sync, ask a qualified music lawyer in the relevant territory.
What producers should actually document
An ISRC is the identifier for a specific recording version. Use one ISRC per final master, keep it consistent across distributors, and assign a new one when the audio version materially changes.
Treat clearance as chain-of-title work: who owns the recording, who owns the composition, what use was approved, what territory and term apply, and who gets paid.
A credit line, DM, beat-store receipt, or friendly verbal yes can be useful evidence, but it is not the same as a license that names the rights and permitted exploitation.
ISRC
Identifies a specific recording or version.
Producer action Assign one per final master, remix, live version, or edit that is distributed.
ISWC
Identifies the underlying composition.
Producer action Register the work and splits with the correct PRO or society.
UPC/EAN
Identifies the release product.
Producer action Use distributor release metadata consistently across stores.
Risk map before release
| Area | Common failure | Conservative move |
|---|---|---|
| Reusing ISRC on a new master | Streams and claims can attach to the wrong recording | Assign a new ISRC when audio materially changes. |
| Wrong writer split | Publishing royalties can be frozen or misdirected | Correct registrations before release campaigns scale. |
| Mismatched artist names | Platforms and royalty reports may fragment data | Use consistent casing, featured artist format, and aliases. |
| Missing territory data | International collections can fail silently | Keep PRO, publisher, and neighboring-right society records aligned. |
Jurisdiction notes for international releases
Use this as a routing map, not legal advice. A beat uploaded from one country can generate claims in another because platforms, PROs, publishers, labels, and neighboring-right societies each operate on their own rules.
| Territory | Operational caution |
|---|---|
| US | Separate master, composition, mechanical, performance, sync, and DMCA processes. SoundExchange applies to non-interactive digital performance royalties for recordings. |
| EU/EEA | Moral rights and collective-management rules can be stricter than a US-only workflow. Platform takedowns and neighboring rights can involve local societies. |
| UK | PRS, MCPS, and PPL often sit in different parts of the rights stack. Do not assume a US PRO registration covers UK exploitation cleanly. |
| Brazil | ECAD and local publishing administration can affect public performance and neighboring-right collections. Portuguese contract language may matter. |
| Russia | Local collection and enforcement conditions can change quickly. Keep contracts, source files, and payment evidence in case platforms request proof. |
| China | Platform clearance, lyric use, and local distribution rules may require local partner review before release or sync use. |
| Japan/Korea | JASRAC, NexTone, KOMCA, and local neighboring-right workflows can be precise about splits, covers, and sync. Metadata accuracy matters. |
| Turkey/Indonesia | Local collecting societies and platform policies may diverge from US templates. Confirm language, term, and territory in writing. |
| Spanish multi-region | Spain, Mexico, Colombia, Argentina, Chile, and other Spanish-speaking markets are not one legal region. Use country-specific review for campaigns. |
| Arabic multi-region | MENA markets vary by country, platform, and local partner. Treat Arabic-language exploitation as multi-territory unless a contract says otherwise. |
Clearance and enforcement workflow
- 1. Finalize the master first
Assign ISRC after the recording version is locked. - 2. Register the composition
Use exact writer and publisher splits to obtain or link ISWC. - 3. Prepare release metadata
UPC, titles, explicit flags, contributors, language, and artwork should match distributor rules. - 4. Archive codes
Store ISRC, UPC, ISWC, PRO work numbers, and distributor links in one catalog sheet. - 5. Audit statements
Compare reports by ISRC and work title to catch mismatches early.
Red flags that should stop the upload
| Red flag | Why it matters | What to do |
|---|---|---|
| No source file or license text | You cannot prove what rights came with the asset. | Pause release until the vendor, collaborator, or rights owner confirms terms in writing. |
| Worldwide sync or broadcast promised in a casual message | Sync and broadcast often need explicit rights language. | Ask for a formal license or exclude the use from the pitch. |
| Multiple writers but no split sheet | Publishing money may be misdirected or frozen. | Get dated approvals before distribution. |
| A platform claim arrives before release day | Fingerprinting can reveal hidden samples or duplicate loops. | Resolve the claim before pitching editors, ads, or sync buyers. |
This is operational education for producers, not legal advice. For a signed deal, dispute, takedown, or high-value sync, ask a qualified music lawyer in the relevant territory.
Use Plugg Supply as a source-control step for music assets: keep license notes, source links, stems, and export metadata together before release.
Learning path
関連アンサーハブ
よくある質問
- Can I reuse an ISRC after remastering?
- If the audio is materially different, use a new ISRC. Minor metadata corrections do not usually require one.
- Does my beat need an ISRC before an artist records vocals?
- Your instrumental release needs its own ISRC. The artist vocal version is a different recording and should have its own ISRC.
- Can a distributor assign ISRCs?
- Yes. Many distributors assign them automatically unless you provide your own.
- Does ISRC handle publishing?
- No. Publishing uses work registrations and may link to ISWC or society work numbers.