Last updated: September 11, 2026
Key Takeaways
- Prepare songs for digital music distribution by delivering lossless audio at native specs, compliant 3000×3000 px artwork, and clean metadata to avoid costly rejections and missed playlist windows.
- Audio must be WAV or FLAC at your master’s native sample rate and bit depth with a –1.0 dBTP true peak ceiling (see Step 1 for full specs).
- Artwork must be square, 3000×3000 pixels minimum, RGB, and free of URLs, logos, QR codes, or explicit content. Once a release is live, cover art changes require a takedown and re-delivery.
- Standardize artist name spelling, use legal names for songwriters, and document all splits and rights clearances in writing before upload to prevent metadata errors and post-release takedowns.
- Upload 4–6 weeks before your release date and visit OnesToWatch for artist spotlights and industry insights.
What “Prepared For Distribution” Actually Means
Prepared for distribution means delivering a lossless master, compliant cover art, clean metadata, and cleared rights to your distributor before a realistic release date. Each asset category has one core rule.
A release that passes distributor QC and platform ingestion without rejection lands on the target date with correct metadata and cleared rights. This article focuses on the pre-submission QA layer between “song is done” and “upload to distributor.” It does not explain how distribution works, rank distributors, or cover monetization strategy.
This guide assumes a finished or near-finished master, a distributor account (DistroKid, TuneCore, CD Baby, or similar), basic familiarity with uploading files, and a target release date. No prior knowledge of ISRC, UPC, LUFS, or metadata fields is required. Distributor rules differ, platform specs update, and rights clearance can take longer than expected. Verify current specs with your distributor and platform documentation before submitting.
The Pre-Flight Process At A Glance
The seven phases below are ordered by rejection risk and fix complexity. Audio and artwork trigger most rejections. Metadata errors are hardest to fix after delivery because they require redelivery and can split your streaming history. Rights issues can force a takedown after the release is already live. Timing determines whether you hit playlist pitching deadlines.
- Audio export and file specs
- Artwork compliance
- Metadata fields
- ISRC and UPC identifiers
- Rights clearance
- Release timing
- Rejection triage
Step 1: What Audio File Format Should I Upload For Music Distribution?
Deliver a lossless WAV or FLAC at your master’s native sample rate and bit depth, typically 24-bit/44.1 kHz or higher.
Velveteen’s audio file prep guide instructs artists to keep the file at the sample rate and bit depth used for the final master and avoid quality-changing processing before delivery. Spotify and Apple Music both accept this approach. Spotify strongly prefers FLAC for delivery and also accepts compliant PCM WAV. Apple Music’s delivery specifications require WAV (16-bit or 24-bit) or FLAC at 44.1 kHz or higher and recommend uploading the highest-quality lossless master available.
The common advice to “export 16-bit/44.1 kHz” before upload does not apply when your master was produced at 24-bit. Veniam Mastering’s 2026 technical guide advises against dithering to 16-bit before delivery because most distributors accept 24-bit and many prefer it. Deliver the native master and let the platform handle conversion.
On loudness, Veniam Mastering’s 2026 guide confirms that Spotify, Tidal, Amazon Music, and Deezer all target –14 LUFS integrated loudness. Apple Music normalizes to –16 LUFS via Sound Check. Platform normalization handles playback loudness, so pushing a master louder only reduces dynamics. A true peak ceiling of –1.0 dBTP is the practical hard limit, because AAC and MP3 encoding can add up to 1 dB of intersample peaks and cause clipping.
Common rejection cause: clipped or distorted audio, incorrect file format (such as MP3 as the master), or a file that fails QC due to excessive loudness or long silence at the start or end. Fix: re-export from the original session at native specs with a –1.0 dBTP true peak ceiling.
Step 2: What Are The Cover Art Requirements For Spotify And Apple Music?
Use a square 3000×3000 pixel image in JPEG or PNG, RGB color mode, with no URLs, logos, QR codes, prices, social handles, or explicit imagery.
Apple Music’s artwork requirements specify a minimum of 3000×3000 pixels, square (1:1) aspect ratio, RGB color mode, JPG or PNG format, and 72 DPI or higher. Auripy’s March 2026 cover art guide confirms that the safest universal target across major streaming platforms is a square 3000×3000 pixel RGB JPEG or PNG under 10 MB.
Banned elements that trigger rejection include:
- Website URLs or social media handles
- Streaming platform logos or badges, including the words “Spotify” or “Apple Music” in the artwork
- QR codes, pricing, or promotional text
- Photos of celebrities or public figures without proof of permission
- Explicit nudity or hate symbols
- Blurry, pixelated, or upscaled low-resolution images
Auripy notes that cover art cannot be updated on an existing release without taking it down and re-releasing it, which loses stream history. The art needs to be correct before the first upload.
Common rejection cause: artwork containing a URL or social handle, or artwork below minimum resolution. Fix: replace it with a clean, high-resolution square image exported from the original source file. Screenshots and messaging-app copies often fail QC.
Step 3: What Metadata Do I Need Before Distributing A Song?
Gather artist name, track title, version, featured credits, songwriters, producers, genre, language, explicit flag, and release date, and keep spelling identical across every release.
PlayGeet’s Music Distribution Hub lists the full required metadata fields: release title, track titles, primary artist, featured artists, composers, songwriters, producers, genre, language, explicit content flag, release date, copyright owner, and record label if applicable. Spelling consistency across releases matters because mismatched artist names split streams across duplicate profiles on Spotify and Apple Music.
The Black Turn’s 2026 rejection guide identifies promotional text in titles, such as “(Official Video)” or “(Prod. by X),” and featured artists written into the title field, as common metadata rejection causes. The version field handles “Remix” or “Live,” and the featured-artist field handles features. Composer and lyricist credits must use legal names rather than stage names or band names.
Common rejection cause: mismatched metadata between the audio file and the distributor form, or missing songwriter credits. Fix: standardize spelling and verify credits before submission. Keep a text file with the exact artist name spelling and paste from it on every submission.
Step 4: ISRC And UPC/EAN — Who Assigns What
An ISRC identifies one recording, a UPC or EAN identifies one release, and your distributor typically assigns both unless you already own your own codes.
An ISRC (International Standard Recording Code) is a 12-character alphanumeric identifier that permanently tags one specific sound recording. A UPC (Universal Product Code) is a 12-digit barcode that identifies the commercial release as a whole. One album with 12 tracks has 1 UPC and 12 ISRCs. Velveteen’s release metadata guide summarizes it as “The UPC is the box. The ISRC is the serial number on each thing inside it.”
Distributors such as DistroKid, TuneCore, and CD Baby assign both codes automatically during upload. Artists who own their own ISRCs should use them consistently across releases. Stream history attaches to the ISRC, so moving to a new distributor and redelivering under the existing ISRC preserves play counts and playlist positions. Redelivering under a new ISRC makes platforms treat it as a new recording starting at zero.
Common rejection cause: duplicate ISRCs, such as reusing one ISRC across a radio edit, extended mix, and club remix, or mismatched UPCs. Fix: verify codes with your distributor before upload and assign a new ISRC to every distinct version.
Step 5: Rights Clearance For Samples, Beats, Cover Songs, And Splits
Secure written clearance for every sample, beat, and cover before upload, and document splits before submission.
Sample clearance requires permission from two separate rights holders: the master recording owner and the composition owner. Sample clearance typically takes 2 to 6 months from first contact to signed agreements. The timeline breaks down into research and identification (1–2 weeks), initial contact and response (2–6 weeks), negotiation (2–8 weeks), and legal review (2–4 weeks). Major labels often take 4 to 8 weeks just to acknowledge a request. Start clearance the same week the track is finished.
For cover songs, a mechanical license is required for the underlying composition. In the US, the Music Modernization Act of 2018 allows streaming platforms to handle mechanical licensing for streaming-only distribution. A mechanical license is always required for physical copies or downloads. Incorrect metadata, especially the original songwriter credit and exact song title, is the most common reason cover songs are rejected or trigger copyright claims after release.
Unlicensed samples cause many post-delivery takedowns. Releasing a track with an uncleared sample can result in the distributor removing the release from DSPs, a DMCA takedown, a copyright infringement claim, or litigation.
Common rejection cause: unlicensed samples or missing split sheets. Fix: obtain written clearance and document splits before submission.
Step 6: How Far In Advance Should I Upload My Release?
Upload 4–6 weeks before your release date to allow for QC, delivery, and playlist pitching.
The Spotify for Artists pitch window opens when a release is in “upcoming” status and closes on release day. Artists need at least 7 business days before the release date and should pitch within 3 days of uploading. PlayGeet advises scheduling releases at least 2–4 weeks in advance to maximize playlist opportunities and reduce the risk of delays.
If you are already inside the window, prioritize the highest-risk items, which are artwork, rights, and metadata, and communicate with your distributor about expedited delivery. Avoid announcing a release date publicly until the release is confirmed and in processing. Announcing before confirmation risks the date changing after promotional content has already been published.
Common rejection cause: uploading too late for playlist pitching or missing the release date entirely. Fix: set a realistic date and work backward from the playlist pitching deadline. If a release still gets pulled or delayed after you follow this timing window, the next section maps the most common rejection and delay causes to their fixes.
Step 7: Why Did My Release Get Pulled Or Stuck? A Rejection And Delay Triage
This section covers rejection and delay causes that many guides skip. Run through the table below before resubmitting. It maps each common symptom to its likely cause and a specific fix, so you can read the exact rejection reason, adjust only the flagged field, and resubmit the same release rather than creating a new one.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Artwork rejected | URL, social handle, platform logo, or image below 3000×3000 px | Re-export a clean square from the original source file with no promotional text |
| Audio rejected | MP3 uploaded as master, clipping, or long silence at start or end | Re-export WAV or FLAC from the original session at native specs with a –1.0 dBTP true peak ceiling |
| Metadata rejected | Mismatched artist name, promotional text in title, or missing songwriter credits | Standardize spelling, move credits to correct fields, and use legal names for writers |
| Identifier conflict | Duplicate ISRC reused across versions, or mismatched UPC | Assign a new ISRC to every distinct version and verify the UPC with your distributor before upload |
| Rights flag or takedown | Unlicensed sample, uncleared cover, or non-exclusive beat with fingerprint conflict | Secure written clearance or replace the sample before resubmitting |
| Release stuck in review | Normal queue, duplicate audio, or manual policy check | Count business days, check the distributor dashboard, and contact support with the UPC and submission date |
DistroKid And TuneCore Upload Requirements
Distributor-specific rules affect how you apply this checklist. DistroKid does not handle mechanical licensing for cover songs, so artists must arrange licensing separately and timelines depend on how quickly they secure a license. TuneCore offers licensing assistance for covers as a separate paid add-on with its own processing queue on top of standard moderation. Both platforms assign ISRCs and UPCs automatically. DistroKid’s Audio Swap feature, limited to its Ultimate plan, is intended for minor fixes only and excludes remixes, alternate versions, and new recordings, which require a distinct delivery.
For a look at artists shaping upcoming release cycles, explore OnesToWatch’s Top Artists To Watch in 2026.
Common Mistakes, Blockers, And Practical Tips
Common Mistakes
- Downsampling the master to 16-bit/44.1 kHz before upload when the native master is 24-bit
- Including a URL or social handle in cover artwork
- Inconsistent artist name spelling across releases, which splits the discography into duplicate profiles
- Missing songwriter credits or using stage names instead of legal names
- Uploading inside the 4-week window and missing the playlist pitching deadline
- Assuming the distributor will fix metadata errors after delivery
What To Watch For
- Artwork that looks sharp at full size but pixelates at 64×64 pixels. Test at thumbnail size before uploading.
- Beat licenses that are non-exclusive. A legally purchased beat can still be flagged if the producer used uncleared samples or the same instrumental already exists in fingerprint systems.
- Royalty-free library loops that trip automated copyright-detection systems even when the license is valid.
If This Happens…
- Release goes live but streams split across duplicate profiles: the issue comes from metadata consistency. Standardize the artist name and request a metadata correction through your distributor.
- Release approved by distributor but missing from a platform: the distributor dashboard showing “approved” does not prove a specific store received the package. Ask the provider to confirm the exact recipient and payload before assuming delivery.
- Cover song rejected after submission: confirm the exact original title and primary songwriter name as registered and verify the title field contains no alternate spellings or extra words like “(Cover)” that matching systems misread.
How To Know Your Pre-Flight Worked
Successful pre-flight shows up in a few clear ways.
- Distributor QC passes without rejection and the dashboard shows the release as approved
- Release goes live on the target date across all selected stores
- Artist profile shows correct metadata, including name, credits, and genre, with no duplicate profiles
- Streams route to the correct artist page rather than splitting across two profiles
- Spotify for Artists confirms the release is in “upcoming” status with enough lead time to pitch
If a release goes live but streams split across duplicate profiles, treat it as a metadata consistency problem. If a release is rejected, use the triage table above to identify the cause before resubmitting. The fix for a rejected release usually takes a few minutes. The variable is how quickly the distributor explains the problem and re-delivers.
Variations, Adaptations, And Next Steps
The pre-flight process adapts by release type and artist situation.
- First-time uploader: allow extra time for artist-page creation and profile mapping, which platforms must complete before the release appears correctly.
- Artist with an existing catalog: verify that the artist name on the new release matches every previous release exactly. One character difference creates a duplicate profile.
- Single vs. EP or album: an EP or album has one UPC but one ISRC per track. Verify every track’s ISRC is unique before upload.
- Track with samples or featured artists: treat rights clearance and split-sheet documentation as non-negotiable pre-upload steps.
10-Minute Pre-Flight For Artists Already Inside The Release Window
- Confirm audio is WAV or FLAC at native bit depth with a –1.0 dBTP true peak ceiling and no clipping.
- Confirm artwork is 3000×3000 px, RGB, with no URLs or logos.
- Confirm artist name spelling matches every previous release exactly.
- Confirm songwriter credits use legal names.
- Confirm rights clearance is in writing for every sample, beat, and cover.
- Pitch on Spotify for Artists immediately after upload.
Logical next-stage topics after a clean release include playlist pitching strategy, royalty splits and publishing registration with a collecting society (ASCAP, BMI, PRS), and post-release promotion planning. For inspiration on who is breaking through next, see OnesToWatch’s Top Artists To Watch in 2026.
Frequently Asked Questions
The questions below cover the points artists most often ask after running the checklist.
What Audio File Format Should I Upload For Music Distribution?
Use WAV or FLAC at your master’s native specs. See Step 1 for the full spec and why 16-bit downsampling is unnecessary.
What Are The Cover Art Requirements For Spotify And Apple Music?
A square image at 3000×3000 pixels minimum in JPEG or PNG, RGB color mode, and under 10 MB. Avoid URLs, logos, QR codes, and explicit imagery. Step 2 explains the details and how to avoid pixelation issues.
What Metadata Do I Need Before Distributing A Song?
You need core credits, titles, and ownership fields with consistent spelling. Step 3 lists every field and explains how to avoid duplicate profiles and title rejections.
How Far In Advance Should I Upload My Release?
Upload 4–6 weeks before your release date. Step 6 breaks down that window and the Spotify for Artists pitch deadline.
What Is An ISRC And Do I Need One?
An ISRC uniquely tags each recording and carries your stream history. Step 4 explains how distributors assign ISRCs and when to use your own codes.
Why Did My Release Get Rejected?
Most rejections fall into audio, artwork, metadata, identifier, or rights issues. The triage table in Step 7 links each symptom to a likely cause and fix.
Do I Need A Split Sheet Before Uploading?
Yes. Document all ownership splits between producers, co-writers, and featured artists before submission. A split sheet specifies each contributor’s percentage of the master and composition. Resolving disputes after release is live costs more time and money than agreeing on splits upfront.
For more context on where new releases fit in the current landscape, explore OnesToWatch’s Top Artists To Watch in 2026.
Conclusion: Run The Checklist Before Every Release
A clean release protects playlist windows, promotional momentum, and your time. The seven-step pre-flight checklist, covering audio at native specs, artwork at 3000×3000 px with no prohibited elements, metadata spelled consistently across every release, ISRCs and UPCs verified before upload, rights cleared in writing before submission, a 4–6 week lead time, and a rejection-and-delay triage pass, covers every category that causes rejections and delays.
Run the checklist before every release. After each drop, confirm that streams route to the correct artist page, metadata displays accurately across platforms, and the distributor dashboard confirms delivery to every selected store. Over time, a consistent pre-flight habit removes problems that come from files and forms instead of from the music itself. To see how emerging artists are turning clean releases into momentum, check out OnesToWatch’s Top Artists To Watch in 2026.