Why your release was rejected for “artist name mismatch”
30 · · 13 min read · Español
A mismatch rejection is a comparison that failed, and the message tells you which one. Two copies of your artist name were held against each other — display against main, fields against artwork, this release against every release before it — and they were not identical. Four of the five comparisons happen inside your own submission, before anything reaches a store at all. Nobody read your name and decided it was wrong.
- “Artist name mismatch” is a distributor’s label for a failed comparison. Neither Apple nor Spotify publishes a rejection reason by that name.
- Four comparisons run inside your submission: display artist against main artist, display artist against the featured fields, one artist field against the one-name rule, and the fields against the cover art.
- The fifth compares the name you delivered against every name you delivered before, character for character, including punctuation, accents and casing.
- A deliberate name change is not a field edit. On Spotify it is a request your label or distributor files, followed by a redelivery of every release.
- A mismatch that passes the checks costs more than one that fails them, because the same comparison decides which artist page the release lands on.
What does “artist name mismatch” actually mean?
It means two copies of your artist name were compared and did not match. The rejection names which two, and that pair is the entire fix.
Start with the part nobody says out loud: no store publishes a rejection reason called “artist name mismatch.” It is your distributor’s summary. The rules being enforced belong to the stores, and they are public, but the sentence in your inbox was written by the company that ran the check.
Which means the useful ones publish their own wording. MusicGateway lists every rejection message it sends, and six of them are this problem wearing six different sentences:
- “Please ensure the Main Artist field matches the Display Artist field.”
- “The Display Artist field must be in line with the data provided.”
- “The Featured Artist field is empty. Please assign a featured artist to match the data provided for Display artist.”
- “If there is only one artist, please ensure the Display artist name is not duplicated in the Featured artist field.”
- “Please ensure there are no duplicated names within the same field.”
- “The Display artist does not match the artist(s) shown on artwork.”
Every one of them is a comparison between two things you supplied. Not one is an opinion about your name.
Somewhere between the rejection email and the forum thread, this turns into a story about a store looking at an independent artist and deciding they were not worth the shelf space. That story is bullshit. A validator ran a string comparison, and a string comparison has nothing to decide with.
Which fields does the distributor compare first?
The display artist against the artist fields beneath it — main artist first, then the featured fields — inside your own submission, before delivery.
Four of the six messages above are this single comparison. A submission form usually has a display line, which is the credit as a listener will read it, and a set of role fields underneath, which is the same credit taken apart. The check is that the pieces reassemble into the whole.
They come apart in ordinary ways. You type the display line last and put an ampersand where the fields have the word and. You add a guest to the display line and forget the featured field, which is the third message. You add the guest to both the display line and the featured field when there is no guest, which is the fourth. Apple’s guide sets the anchor for all of it: “The main performing artist must be listed as Primary at the album and track level” — both levels, which is how an album passes carrying a track that did not.
What none of these fields decide is what the credit means. Featured, “with,” and side artist are three different deals with three different prices, and the form will happily let you pick the wrong one and then validate it perfectly.
Why does one artist field with two names in it fail?
Because two names in one field is a compound artist, and the stores cannot identify either person inside it.
Spotify states the consequence rather than just the rule, which is rarer than it should be: “Each artist field must contain only one artist name. If two or more artists (individuals or groups) are listed in one artist field, it is called a compound artist. In such cases, individual artists will not be identified, and content will not appear on the correct artist pages.” Apple’s version is four words shorter and says the same thing: “Each artist field must only contain one artist name.”
So Jessie J & Ariana Grande & Nicki Minaj in one field is not three artists with a formatting problem. Two names in one box, and the store files the record under a band that does not exist.
Then the exception, which catches real bands and is the reason people distrust the rule. Apple: “Artists who are generally listed together as a band are not considered compound artists and must be listed together” — Simon & Garfunkel, Brooks & Dunn, Katrina & The Waves. Spotify agrees, naming Ike & Tina Turner and Peter Bjorn and John, and adds the case that trips up backing bands: Neil Young & Crazy Horse goes in as the only main artist at product level, not as two.
The test is not the ampersand. It is whether the thing on the left of it releases records on its own.
Why was it rejected when the name is spelled the way it always is?
Because it is compared against what you delivered before, character for character, and punctuation, accents and casing are characters.
Both stores make this a rule rather than a preference. Spotify: “Spelling of an artist’s name must be consistently applied to all content related to that artist.” Apple: “Full, standard name spellings must be used for all artists and other credits on all content. The spelling of names must be correct and remain consistent across the entire recording and all content for that artist.”
Spotify’s own example table is the one to look at, because it is not a hypothetical. The Radio Dept. is correct. The Radio Dept is incorrect, and the stated reason is “Incorrect spelling.” The difference is a full stop. Two further rules in the same document are the same shape: accents and casing “must be delivered accurately in the xml, or the title will create or appear on a wrong artist page (ie: always enter ‘Beyoncé, not Beyonce),” and a leading The is capitalised unless the artist says otherwise.
Nothing about you changed; a character did. Pluto is exactly the size it always was, and it is still not a planet.
This is also why the fix is never “the correct spelling.” The fix is the spelling already on file, which may not be the one you would choose today. If you want the other one, that is a name change, and it is a different job.
Why does the artwork get a correct name rejected?
Because one comparison is not between two strings: your fields are read against the cover art, and artwork cannot be diffed.
The message is plain enough — “The Display artist does not match the artist(s) shown on artwork. Please update the display artist or artwork and resubmit” — and Apple carries the store-side rule behind it, requiring the original cover art rather than “art that doesn’t match the album you’re delivering,” and adding that “the art must not be misleading.”
This is the one that arrives feeling arbitrary, because every other check on the list is mechanical and this one is somebody reading a picture. It catches the sleeve set in a display face with no accented characters, so the name on the front is missing the one it has everywhere else, and the cover credited to the duo when the fields are credited to one of them.
Both halves are yours, so change the cheaper one. The artwork is a file. The name is on every release you have.
What if the name changed on purpose?
A new artist name is not a field edit. On Spotify, your label or distributor requests the change from Content Operations, and every release is redelivered afterwards.
Spotify says it in three sentences and each one costs somebody a week when it is skipped. “You can’t manually change your artist name on Spotify. Your artist name comes from the metadata your label or distributor sends us.” Then: “Ask your label or distributor to request a name change with Spotify’s Content Operations team.” And then, the part people find out last: “After Content Operations confirm the request, your label or distributor should redeliver the metadata for each release with your new name.”
Read the order. The request comes first and the delivery comes second, so a new release carrying the new name before the request has cleared is a delivery that disagrees with every release behind it. That is not a rebrand. That is the mismatch you are here about, filed by you, on purpose, at the worst possible moment in a campaign.
Do the request first. Then redeliver the back catalogue. Then ship the new record.
When is a mismatch worse than a rejection?
When it passes. The same comparison one step later decides which artist page the release lands on, and inconsistency alone does not stop a delivery.
Spotify draws the line itself: the accents-and-casing rule exists because a name delivered inaccurately “will create or appear on a wrong artist page,” and a compound artist means “content will not appear on the correct artist pages.” Neither of those is a rejection. Both are releases that go live, on a page, and the page is the question. A rejection costs you a resubmission; a pass costs you a page, and then a repair with two filers and its own order of operations. Between the two, the rejection is the good outcome, and it is the only one that arrives with an email.
There is a third tier, and it is the one worth reading twice. Spotify’s style guide opens by saying that content owners “will be notified of any errors, compliance failure or deceptive metadata,” and that “repeat instances will result in delivery delays and, possibly, termination of delivery rights.” Apple lists “misleading content (sound-alike artists or performers)” among the kinds of content that may be rejected outright. Nobody loses delivery rights over a full stop. They lose them over the twelfth submission that ignored the last eleven messages.
How do you stop it happening again?
Decide the exact string once, keep it where the next person will copy it, and sweep the catalogue rather than the release.
- Write your artist name down once, somewhere you can paste from. Not in your head, and not in the last release’s form — somewhere a manager, a label contact or a session engineer copies it without asking you.
- Record the punctuation as part of the name. The full stop in The Radio Dept. is not typography. It is the name.
- One name per field, always, and let the roles do the rest.
- Check the display line against the role fields before you submit, in that direction. The display line is the one you typed fastest.
- Open the cover art and read it next to the form. Thirty seconds, and it is the only check here a machine will not run for you.
- Deliver an artist identifier with every release, so the name is not the whole address.
- Fix the catalogue, not the release. If you would rather do the whole thing in one pass, there is a checklist for it — whatever produced one mismatch produced it more than once.
FAQ
Will a mismatch rejection cost me my release date?
No store guide and no distributor rejection list read for this page publishes a turnaround for a corrected resubmission, so this page states none. Plan on the release going back through the same review it failed, and set the date after the resubmission clears rather than before.
My band name has two people in it. Is that a compound artist?
No, if the band is generally listed that way. Apple states that artists who are generally listed together as a band are not considered compound artists and must be listed together, giving Simon & Garfunkel and Brooks & Dunn as examples, and Spotify says the same of Ike & Tina Turner and Peter Bjorn and John.
Can I style my artist name differently on one release?
Only if that styling is the name. Spotify requires the name in the form dictated by the artist or its most widely known form, applied consistently to all content, and separately rules out all capitals, all lowercase and random casing unless the artist specifies it.
Will fixing the name move a release that is already on the wrong artist page?
No. Correcting the field changes what is delivered next; a release already sitting on the wrong profile is a separate repair, with a form you can file yourself and a metadata update only your distributor can send.
Sources
- Apple, Apple Music Style Guide — that artist accuracy and formatting is among the most critical delivery guidelines and that misleading content, including sound-alike artists, may be rejected (§1); that full standard spellings must be used and must remain consistent across all content for that artist, and that names carry no role, date, instrument, former band or website (§2.1); that each artist field must only contain one artist name (§2.3); that artists generally listed together as a band must be listed together (§2.4); that the main performing artist must be Primary at album and track level (§2.6); and that cover art must not be art that does not match the album delivered, nor be misleading (§7.1).
- Spotify, Metadata Style Guide (v2.3) — that the standard full name and proper spelling are required and must follow the form the artist dictates or the most widely known one (§1.1, §1.2); that spelling must be consistently applied to all content related to that artist, with The Radio Dept. against The Radio Dept as its own example (§1.3); that a compound artist means individual artists will not be identified and content will not appear on the correct artist pages (§6.2); the band exception and the backing-band case (§6.3, §6.5); that accents and casing must be delivered accurately or the title will create or appear on a wrong artist page (§26.2); the capitalised leading The and the ban on all-caps, all-lowercase and random casing (§26.3, §26.4); and, in its overview, that repeat instances will result in delivery delays and possibly termination of delivery rights.
- Spotify, Changing your artist name — that an artist name cannot be changed manually and comes from the metadata a label or distributor sends; that the change is requested from Spotify’s Content Operations team by that label or distributor; and that every release is redelivered with the new name after the request is confirmed.
- MusicGateway, Distribution Rejections — the six artist-name rejection messages quoted above, in a distributor’s own published wording, including the artwork comparison.
Store rules change and are quoted here as of the date at the top of this piece; the linked guides are the living documents, and every one of them was read on that date. Distributor wording varies, and the six messages above are one company’s — the comparisons behind them are the same everywhere, the sentences are not. Five other distributor help centres refuse non-browser requests entirely, so nothing here rests on a page that could not be opened and read.
Keeping the register
Every rule on this page reduces to one question you should not have to answer from memory: what exactly did we deliver last time. CatalogTracker holds each person and organisation once, as a party with a name structure and identifiers of its own rather than as text retyped into every release, and its History tab records who changed what, old value to new value, so the string you delivered in March is readable in September without opening a distributor dashboard. It does not check anybody’s style guide and does not deliver anything. It just stops the answer from living in four forms. In development for iPhone.