You have a finished song, a folder of files named final_master_v3_REAL.wav, and a sense that the next step involves signing up somewhere and paying someone. That is where most releases go wrong — not in the music, but in the twenty minutes of admin that decide how the track is identified, how loud it plays, and whether the money finds you a year later. This guide walks the path in order and explains what breaks at each step when the rule is ignored.
What a distributor actually does
A distributor is a delivery agent. It takes your audio, artwork and a structured package of metadata, formats that package to each service's ingestion spec and sends it out; later it receives royalty reports and money back and passes them to you. It does not decide whether a playlist picks you up, does not set a payout rate, and cannot fix a badly typed credit without a redelivery. What a distributor can do for you is determined by the quality of the package you hand it.
Which services a release reaches depends on the release, the territory, eligibility rules and what each provider currently supports. Anyone quoting a fixed number of stores is quoting a marketing figure, not a delivery guarantee. At Mazufa, destinations are confirmed per release before delivery.
What "free" means, precisely
Free should be checkable, not a slogan. With Mazufa there is no upload fee, no subscription and no per-release charge, and the commission is 0% — no percentage of your royalties is taken, and royalties received are passed through in full.
Two things sit outside anyone's control: your bank may charge its own transfer fee, and statutory tax may be withheld at source (below). Neither is a distributor's cut — and be sceptical of anyone promising 100% of what lands in your account, because nobody controls a bank's fees. The honest promise is about commission: 0%. Mazufa is invite-only, with human review of every complete application; you can apply here.
Step 1 — Get the master right
Streaming services normalise loudness on playback: a master louder than the target is turned down by the difference. That is the mechanism, and it is why loudness-war logic no longer pays.
You can predict that adjustment on exactly one service, because Spotify is the only one that publishes the figures: an integrated target of −14 LUFS and a true peak ceiling of −1 dBTP, or −2 dBTP if the master is louder than −14 LUFS. Spotify also states that positive gain is applied to softer masters to reach −14 LUFS, while it considers the track's headroom and leaves 1 dB for lossy encoding — so a quiet master with peaks against the ceiling may not be raised all the way.
The practical consequence: crushing a mix with a limiter does not make it louder on a streaming service, it makes it flatter at the same perceived level.
Two measurement details, because meters disagree:
- The current standard is ITU-R BS.1770-5 (November 2023). Many deployed meters still cite BS.1770-4 from 2015, which is superseded.
- Sample peak is not true peak. True peak is measured on an oversampled signal — 4× minimum under BS.1770, 8× is better. Inter-sample peaks can exceed the highest sample value in your file, which is how a master reading −0.3 dB in your DAW clips after encoding.
Everywhere else you are guessing. No normalisation target has been published by Apple Music, YouTube Music, Amazon Music, TIDAL or Deezer, and the numbers that circulate for them are widely reported rather than published by the service — not a basis for a mastering decision.
Check your own file with the loudness checker — it runs in your browser, and no audio is uploaded.
Step 2 — Metadata that survives the trip
Metadata decides whether your release is matched to your artist profile, credited correctly and searchable at all. It is also the part most often typed in a hurry. Rules that repay the effort:
- Write the title exactly as it should appear — not
Song Name (Prod. By Someone)unless that is genuinely the title. - Featured artists belong in the featured-artist field, not the track title.
- Keep artist name spelling identical across releases. One stray character forks your profile in two.
- Songwriter credits need real legal names, not stage names.
If your metadata uses Arabic, Persian, Urdu or another right-to-left script, one issue dominates: bidirectional text. When Latin tokens — a feature credit, a version tag, a number — are mixed into an RTL string, the Unicode bidirectional algorithm (UAX #9) reorders them for display, and the store page renders wrong even though the stored string is correct. Isolate mixed tokens deliberately and check the rendered result, not the raw text. The Music Biz Metadata Style Guide covers the rest.
The metadata checker catches the common structural errors before delivery.
Step 3 — Identifiers: ISRC and UPC
These two codes are not interchangeable, and confusing them causes real problems downstream.
| Code | Identifies | Shape |
|---|---|---|
| ISRC | The recording | 12 characters: 2 country + 3 registrant + 2 year-of-reference + 5 designation |
| UPC / EAN | The release (the product) | UPC-A is 12 digits; EAN-13 is 13 |
Commonly got wrong: hyphens are a display convention only and are not part of the code; there is no check digit in an ISRC, so a tool validating one by checksum is wrong; an ISRC identifies the recording, not the song (that is an ISWC) and not the release; and ISRCs stay with your recordings when you change distributor.
You need a new ISRC for a remix, edit, live version or instrumental — any materially different recording — but not to re-release the same recording. Remasters are narrower than commonly claimed: under the IFPI ISRC Handbook (§A.10.1), a new ISRC is assigned only if the remastering involved creative input to the recording itself. Level changes, invariant EQ or compression, de-noising, de-clicking, speed or pitch correction, sample-rate conversion and dithering are explicitly excluded as "essentially invariant or technological adjustment processes". Safe rider: if the remaster is sold as a separate track alongside the original, it is a separate product and needs its own code.
A UPC check digit is computable: from the right, alternate ×3 and ×1 across the digits before it, sum them, and the check digit is whatever brings the total to the next multiple of 10. A UPC-A becomes an EAN-13 by prefixing a zero, and the check digit does not change. Verify yours with the ISRC and UPC checker.
Step 4 — Artwork and scheduling
Artwork should be square, high resolution, and free of URLs, logos, social handles and anything reading as advertising. Text legible on your monitor may be unreadable at the size a phone renders it — check at thumbnail scale.
Schedule two to four weeks ahead. That window is a working reality rather than a store rule: it lets delivery complete, and gives you time to claim your artist profile and pitch the release before it exists.
Step 5 — Getting paid without losing a third of it
No streaming service publishes a per-stream rate, so distrust any figure presented as one. Spotify states plainly that it does not pay per stream: revenue is pooled and divided by streamshare. Differences between countries follow from local subscription pricing and ad rates, not from a published per-country rate — no service publishes one of those either.
The largest avoidable deduction is tax, not commission: with no W-8BEN on file, US-sourced royalties are withheld at the statutory 30%, and filing one — claiming your country's treaty rate where a treaty exists — is the fix.
Two details save wasted effort: line 6 of the W-8BEN accepts a foreign tax identification number, so most artists need no US ITIN, and the form is valid through the last day of the third succeeding calendar year, so it is not an annual chore. The payout calculator shows how withholding changes what you receive.
Pre-release checklist
Work through this before you schedule anything:
- Integrated loudness and true peak both measured, true peak with oversampling.
- No limiter pushed past the point where dynamics disappear.
- Artist name spelled identically to previous releases, character for character.
- Featured artists in the featured field, version tags in the version field, title clean.
- Songwriter legal names collected for every contributor.
- RTL metadata checked in rendered form, not as a raw string.
- ISRC per recording, a new one only where the recording is materially different.
- UPC check digit verified.
- Artwork square, high resolution, no logos or URLs, legible at thumbnail size.
- W-8BEN completed with your foreign TIN and treaty position confirmed.
- Release date two to four weeks out, destinations confirmed for this release.
Get those eleven lines right and the admin stops being the part of releasing that costs you money.