Remix Metadata and Credits for Streaming Platforms
A remix needs a new ISRC, base title and version, original artist, remixer role, featured artists, performers, producers, engineers, original and new songwriters, publishers, ISWC where known, explicit state, language, genre, dates, artwork, lyrics, release UPC, provider IDs, and platform mappings. Apple currently requires the original artist as Primary and the remixer as Remixer. Verify every public surface after delivery.
Lead visual
Release metadata preflight
Title casing
Check before delivery, not after stores ingest the release.
Featured artist role
Check before delivery, not after stores ingest the release.
ISRC format
Check before delivery, not after stores ingest the release.
P line owner
Check before delivery, not after stores ingest the release.
Explicit tag
Check before delivery, not after stores ingest the release.
Fix before deliver
After delivery, corrections move through store updates, cache delays, and royalty systems that may already have recorded the wrong data.
Release · Remixes
Release data map
Decision
Fix release information before stores, societies, and royalty systems ingest it.
Evidence
Titles, artist roles, ISRCs, UPCs, ownership lines, explicit flags, files, and artwork specs.
Risk
Bad metadata travels into stores and takes longer to correct than it would have taken to preflight.
Good outcome
A release record that is easier to deliver, match, pitch, and pay correctly.
Key takeaways
- Assign a new ISRC to the remix and keep the original recording's ISRC as a separate relationship record.
- Use structured title-version, Primary, Remixer, contributor, writer, publisher, date, and explicit fields instead of title stuffing.
- Preserve original songwriters and publishers while adding only documented new musical-work contributions.
- Treat the distributor as the metadata sender and record every provider-specific field, preview, delivery, error, and correction.
- Inspect public artist mapping, title, roles, credits, audio, duration, artwork, explicit state, lyrics, dates, links, and territories.
Which fields belong in a remix metadata sheet?
Remix delivery specification
Fourteen identity fields before upload
Recording
Approved audio filename, checksum, duration, sample rate, bit depth, channel state, clean or explicit version, language, and master date.
Binds metadata to the exact accepted remix file.
Relationship
Original recording title, version, artist, ISRC, release, owner, link, source stems, and authorized remix agreement.
Preserves provenance without reusing the original recording identity.
ISRC
New remix ISRC, registrant, assignment source, assignment date, country prefix, year, designation, and internal record.
Creates a permanent identifier for this distinct recording.
Release
New or existing package, UPC, label, distributor, release ID, release date, original release date field if used, preorder, territories, and formats.
Separates recording identity from the product that contains it.
Title
Base song title, version text, remixer name if required, additional version, spelling, capitalization, punctuation preview, and localization.
Differentiates the remix without corrupting the canonical base title.
Original artist
Canonical name, Primary role, platform IDs, distributor artist slot, label mapping, localization, and approvals.
Keeps the remix attached to the correct source artist.
Remixer
Canonical name, Remixer or supported equivalent role, platform IDs, profile mapping, display intent, spelling, and approval.
Credits the remix creator without assigning an incorrect primary role.
Performers
Featured artists, vocalists, instrumentalists, groups, ensembles, samples, carried source performances, roles, identifiers, and approvals.
Preserves audible contributor identity and contractual credit.
Production
Remixer, producer, additional producer, remixing engineer, mixer, mastering engineer, assistants, programmers, editors, and actual roles.
Separates creative and technical contribution from performing-artist billing.
Composition
Original and new songwriters, composers, lyricists, shares, publishers, administrators, PROs, IPI numbers, ISWC, derivative consent, and split record.
Keeps the song ledger aligned with the changed recording.
Content
Explicit flag, clean relationship, lyrics, instrumental state, language, genre, mood, BPM, key, copyright lines, and advisory requirements.
Prevents store display and recommendation fields from contradicting the audio.
Visual
Artwork file, title and artist text, logos, credits, licences, dimensions, colour, explicit marks, version relationship, and approvals.
Joins the correct remix packaging to the correct recording.
Provider
Upload owner, workflow, field names, artist slots, role support, title preview, store targets, validation, acknowledgement, errors, and support case.
Translates the canonical sheet into the actual delivery system.
Public QC
Store URL, artist pages, title, version, roles, credits, audio, duration, explicit state, artwork, lyrics, date, territory, links, correction, and evidence.
Verifies what listeners received rather than what the form accepted.
How should original and remix identities remain separate?
| Original recording | Remix recording | |
|---|---|---|
| Audio | Approved original master and checksum | Approved changed master and its own checksum |
| ISRC | Keep the original recording's existing ISRC | Assign a new ISRC because the recording differs |
| Title | Canonical base title with no unnecessary Original Mix label | Same base title plus structured remix version information |
| Artists | Original performing artists in their applicable roles | Original artist Primary for Apple-aligned delivery plus remixer in the Remixer role and carried performers |
| Composition | Underlying writers, publishers, administrators, shares, and ISWC | Preserve underlying data and add only authorized new writer contributions |
| Product | Original UPC, release date, artwork, distributor release ID, and platform links | Remix release package, UPC if separate, remix release date, artwork, provider ID, and links |
| Economics | Original master and composition agreements and statements | Remix agreement, fee, master formula, split records, registrations, directions, and statements |
How should the remix identity be delivered and corrected?
Metadata supply chain
Seven gates from master to public record
- 01
Gate 1
Lock audio
Name the accepted remix file and versions, calculate checksums, confirm duration and explicit state, and archive approval.
- 02
Gate 2
Lock rights
Join release authority, agreement, samples, performers, writer splits, ownership or licence, territories, and signers.
- 03
Gate 3
Assign identity
Issue the new ISRC, choose release UPC, record original relationship, title version, dates, copyright lines, and provider IDs.
- 04
Gate 4
Map people
Resolve original artist, remixer, featured artists, performers, producers, engineers, writers, publishers, IDs, roles, and profiles.
- 05
Gate 5
Preview
Inspect provider title rendering, artist slots, role support, credits, artwork, explicit state, stores, territory, date, and warnings.
- 06
Gate 6
Deliver
Submit through the authorized account, preserve acknowledgement, validation, errors, changes, ticket, delivery state, and release link.
- 07
Gate 7
Verify
Play and inspect every public surface, route defects through the provider, record correction evidence, and recheck affected territories.
Identifier creation is not rights clearance
A new ISRC, UPC, distributor acceptance, correct artist page, public credit, or royalty payment does not prove that the master, musical work, samples, performers, or remix release were authorized.
validate the canonical identity before translating it into provider fields
Which primary sources define remix metadata and credits?
Frequently asked questions
Does a remix need a new ISRC?+
Yes. IFPI states that a remixed version differs from the original and must receive a new ISRC. Apple's current specification also requires a unique ISRC for a remixed or otherwise different track. Record the registrant, assignment date, code, audio checksum, duration, title version, contributors, and source relationship. Do not reuse the original recording's ISRC or infer ownership and permission from the new code.
How should a remix title be formatted?+
Keep the base song title intact and place the distinguishing description in the distributor's version field. Apple applies structured punctuation and supports remix version information, including a remixer name where appropriate. Do not add Original Mix to the standard version, duplicate featured artists, embed role labels in the base title, or improvise punctuation when the provider generates it. Preview the store title before submission.
Who is the primary artist on a remix?+
Apple currently says remix tracks must list the original artist as Primary and assign the remixer the Remixer role. DistroKid's current workflow similarly keeps the original artist in its artist field for a remix of another artist and adds the remixing artist as Remixer. Other providers can expose different fields and artist-slot rules, so follow the selected workflow and verify profile mapping publicly.
Do the original songwriters stay credited on a remix?+
Yes, the underlying composition and its writers and publishers remain relevant. Preserve their names, shares, publishers, administrators, PRO affiliations, IPI numbers, and ISWC where known. Add a new writer only when an actual musical-work contribution and authorized split are documented. A remixer role, production credit, fee, master royalty, or title mention does not automatically change composition authorship or publishing shares.
How do I fix wrong remix credits on Spotify?+
Spotify says it displays credits supplied by the label or distributor. Ask the authorized provider to correct and resend the structured track metadata, then preserve the case number, submitted fields, affected recording and territories, delivery acknowledgement, and public result. Spotify notes that some distributors do not support every credit. Correct the source metadata rather than editing only a marketing description or artwork line.
Get better release strategy in your inbox
Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.
Was this useful? Send a signal or flag a correction.
Keep reading
Pillar guide
Remixes for independent artists
A nine-gate remix decision and release chain joining audience purpose, master and song authority, controlled stems, agreement, acceptance, economics, new-recording identity, delivery, public QC, and learning.
Pillar guide
Release metadata guide
What metadata is, the ℗ vs © copyright lines, ISRC vs UPC, and the title and credit rules that decide whether your release is accepted and your royalties reach you.
Related guide
Remix release marketing strategy
A nine-state remix campaign loop and six-layer measurement hierarchy joining audience purpose, artist roles, approved assets, current Spotify timing, tagged channels, catalogue bridge, efficiency, and accounting.
Check your metadata before your distributor does
Run your titles, credits, copyright lines, and ISRC and UPC codes through the free checker and catch the rejection-bait errors before you upload. It all runs in your browser.