Browse articles

Common rejection reasons, and how to fix them

The findings that stop a release or flag it for a reviewer, what each one actually means, and the fix for each, grouped by metadata, audio, artwork and rights.

8 min read Updated

On this page
  1. Metadata
  2. Barcodes and ISRCs
  3. Audio
  4. Artwork
  5. Rights and content matching
  6. Rejected by a person
  7. Fixing and resubmitting

When a release comes back, the reasons are listed on the release page and repeated in the email. This article is the long version of those one-line findings: what each one is really objecting to, and what to change.

A hard failure stops the release. A flag does not: it goes to the person reviewing your release, who may approve it, ask you something, or refuse it. Flags are marked as such below, so you can tell the difference between “this has to change” and “somebody will look at this”.

Metadata

What you seeWhat it meansWhat to do
Search-bait wording in the titleWords like “type beat” or “official audio” are keyword bait, not part of the nameTitle the track what it is called. Nothing else
Karaoke or “originally performed by”Karaoke and soundalike wording is not accepted at allThis one has no fix. The release cannot ship
”In the style of”Reads as a soundalike, which is impersonationIf it is your own original work, rename it without the comparison
”AI cover” or “AI voice” of another artistThe marketing format of voice-clone content, which is refusedOriginal work with AI in it is welcome and ships. Rename it so it is not sold as someone else’s voice
Control characters or odd spacing in a titleInvisible characters and doubled spaces break store ingestionRetype the title in plain text
ALL CAPS title (flag)Stores want standard casing unless the name really is stylisedUse normal casing, or leave it and let the reviewer confirm the styling
”feat.” written into the title (flag)Stores read featured artists from the credits, not the title textCredit the featured artist on the credit line instead
The release needs at least one main artistNothing is credited as the primary actAdd a main artist on the release, and on any track that overrides the credits
More than 4 main artistsStores treat that many primaries as “Various Artists”Keep the mains to the acts the release is by, and move the rest to featured
An artist is credited twiceThe same profile appears twice on one release or trackRemove the duplicate line
Artist pages are marked as existing but none are connectedWe do not know which store page this release belongs onPaste the Spotify or Apple Music profile link, or mark the artist as new to streaming
The connected profile has a different name (flag)The store page you linked is published under another nameCheck you linked your own page. If the name is right, the reviewer confirms it
Credits are missing a role categoryEach track needs a performer, a composition and lyrics credit, and a production and engineering creditAdd the missing person, or add the missing role to someone already credited
At least one credited person must not be fully AIA track cannot be credited entirely to AICredit the human who made it. Disclosure stays whatever it truly is
Publishing splits must total exactly 100%Splits are present but do not add upFix the percentages, or remove them all: splits are optional, not partial
Track numbering must run 1, 2, 3The tracklist has a gap or a repeatReorder the tracks so the positions are contiguous
The genre is not in the current listThe genre was removed or renamed since you picked itOpen the genre field and pick it again
The original release date is after the release dateA re-release cannot have come out later than itselfCorrect whichever of the two dates is wrong
The release date is more than two years out (flag)Usually a typo in the yearCheck the date, then leave it if it is deliberate
The label is not available on this accountThe release is branded with a label your account does not holdPick your own label, or the default one

Barcodes and ISRCs

What you seeWhat it meansWhat to do
The barcode must be 12 or 13 digitsWhat you pasted is not a UPC or EANRetype it, or clear the field and let one be assigned
This barcode is already used by another releaseA barcode identifies one release and is never reusedClear the field and let a new one be assigned
The ISRC is not a valid codeIt does not match the CC-XXX-YY-NNNNN shapeRetype it, or clear it and let one be assigned
This ISRC is used twice in this releaseTwo tracks carry the same recording codeGive each recording its own, or clear both
This ISRC is already used by another recordingThe code identifies a different recording in our catalogueClear it and let a new one be assigned
This ISRC is on another of your releases (flag)Correct only if this really is the same recording re-releasedLeave it if it is a re-release, and the reviewer confirms. Otherwise clear it

More on both: ISRCs and barcodes.

Audio

What you seeWhat it meansWhat to do
Audio must be WAV or FLACThe file is not lossless, or not in an accepted containerExport a WAV (16, 24 or 32-bit) or a 16-bit FLAC
FLAC masters must be 16-bitA higher-depth FLAC is not acceptedExport the same master as a WAV instead
The sample rate is too low or too highOutside 44.1 kHz to 192 kHzRe-export inside that range. Do not upsample a 32 kHz source
Masters must be stereoThe file is mono or multichannelExport a two-channel file
Audio must be at least 1 secondThe file is effectively emptyUpload the real master
Audio files are capped at 2 GBThe file is over the limitA 24-bit 48 kHz master of any normal length is far under it. Check the export settings
The file could not be readThe upload is corrupt or is not really audioRe-export and upload again
True peak above -1 dBTP (flag)Under 1 dB of headroom, so store transcodes can clipSet the limiter ceiling around -1 dBTP and re-export
Loudness far above -14 LUFS (flag)Stores turn it down anyway and you lose the dynamics for nothingMaster quieter, or leave it and accept how it lands
Silence at the start or end (flag)More than two seconds of nothingTrim it, unless it is part of the piece
Both channels are identical (flag)A mono recording inside a stereo fileFine if the recording is mono. Otherwise export the real stereo mix
The audio looks like it came from a lossy file (flag)The top of the spectrum is missing, as an MP3 or AAC source would beUpload the original lossless master

Artwork

What you seeWhat it meansWhat to do
Cover art must be squareThe image is not 1:1Crop it square before uploading
Cover art must be at least 3000 by 3000Below the store minimumExport the original artwork larger. Upscaling is not a fix
The cover has transparencyAlpha channels do not survive at storesFlatten it onto a background and export as JPG or PNG
The cover could not be readThe file is corrupt or is not an imageRe-export and upload again

Rights and content matching

What you seeWhat it meansWhat to do
A cover song needs a cover or mechanical licenseThe track is marked as a cover with no document attachedUpload the licence on that track
A public-domain work needs proofThe track is marked public domain with nothing to show for itUpload territory-specific proof
Licensed samples need the sample clearanceThe track declares commercial samples with no clearanceUpload the clearance for each sample
The recording matches a released track (flag)Content matching found the same recording already outIf it is your own earlier recording, or licensed, tell the reviewer in a request
This sounds like a cover of an existing track (flag)Content matching heard the same composition, performed differentlyMark the track as a cover and attach the licence
AI-generated audio with no voice consent on file (flag)Disclosed AI audio might render a real person’s voiceOriginal synthetic voices are fine. For a real person’s voice, send the consent in a request
The content scan did not run (flag)The match could not be completed for that trackNothing for you to do. The human rights check still happens

See covers, remixes and samples and the AI policy.

Rejected by a person

A rejection from review is not one of the findings above. It carries a written reason from the reviewer, shown on the release page, and it means nothing was sent to any store. Read the reason, fix what it names, and submit again. If the reason is not clear, open a support request and quote it.

Fixing and resubmitting

Findings and rejections both end the same way. On the release page, “Fix & edit” puts the release back to a draft and opens the editor with the previous verdict cleared. Change what was named, then submit again: it walks the same path as a first submission, and it does not spend a second release from your plan allowance.

The full loop, including what stays locked once a release has been delivered, is in editing, reopening and resubmitting.