Explicit, clean, and the lyrics flag

39 · 2026-09-06 · 15 min read · Español

Three different things get called the explicit setting, and only one of them is a checkbox. The flag is a declaration the rights holder makes and every store repeats. A clean version is a second recording with its own identity. The lyrics are a third delivery with rules of their own. All three can disagree with each other, and each one is fixed somewhere else.

• The explicit flag is a metadata field delivered with a recording. Only the label or artist that owns the recording decides its value, and the stores repeat that decision.
• Marking a track explicit adds a badge and removes the track for any listener who has switched explicit content off. Nothing published ties the flag to a territory or to playlist eligibility.
• A clean version is a separate recording that has been edited, not a different setting on the same one. Apple and Spotify both allow the Clean tag only where the explicit version of that track also exists.
• Displayed lyrics are delivered separately from the recording and follow the audio rather than the flag. Censored words are starred out because the audio censors them.
• A flag that is wrong on a released track cannot be changed by the artist. The label or distributor sends a metadata update, and the store shows what was delivered.

Who decides that a song is explicit?

The label or artist that owns the recording decides, and every store downstream repeats that decision rather than making one of its own.

The Parental Advisory Label is a programme run by the Recording Industry Association of America, and its Standards — the current version effective 6 August 2025 — put the decision in exactly one pair of hands:

Only the record label or artist that owns and/or distributes the particular sound recording may determine whether the sound recording contains PAL Content and warrants the use of a PAL Notice.

A page later, for the avoidance of any doubt downstream: everyone else “shall abide by the applicable record label or artist’s determination.”

PAL Content is the Standards’ own term for “strong language or depictions of violence, sex, or substance abuse to such an extent as to merit parental notification.” Note what that definition does not contain: a list of words. The Standards decline to supply one — it is “obviously not possible to define each individual situation” — and offer seven considerations instead, of which the seventh is worth reading twice. A recording “may contain strong language or depictions of violence, sex, or substance abuse, yet, due to other factors involved, may not merit a designation as containing PAL Content.”

Two restraints come with the same document, and both cut against how the badge is usually read. The determination “is not a statement as to whether the sound recording is or is not suitable for particular listeners.” And the absence of one is not a statement that a record is clean.

The stores say the same thing from the other end. Spotify’s explicit content page is one sentence on the subject of authorship: “We tag explicit content depending on information we receive from rights-holders.” The DDEX guidance that the delivery formats are built on says why it has to work this way: “What is deemed to be explicit varies between countries, cultures and even individual people.”

So there is no adjudication and there is no review. The value in that field is a claim you make about your own record, and every filter between you and a listener is built on it. No one on the other end of the delivery gives a damn what is on the track until you tell them.

What does marking a track explicit actually change?

An explicit track carries a badge and will not play for a listener who has switched explicit content off. The published list of consequences ends there.

Spotify’s metadata guidelines for artists describe the first half in the plainest possible terms: “Mark your explicit tracks as explicit. We display an E icon next to explicit tracks - you shouldn’t add it to your track title.” The second half is on the listener’s side of the same product. When explicit content is switched off, “anything with an explicit tag is grayed out,” and “you can’t play it, and it’s automatically skipped.”

Greyed out is worth sitting with for a second. The track is still on the album, still in the artist’s catalogue, still returned by the store’s own systems. It simply will not start.

The Apple Music Style Guide gives the commercial half, in §6.2, and it is the sentence that explains why the pair matters more than the label. Clean versions of audio content with an available explicit version “must be flagged Clean to prevent customers from accidentally purchasing the clean version.” The flag is a shopping instruction as much as a warning.

Now the part that gets assumed and is not published anywhere. The delivery standard itself is explicit that the value is guidance and not a switch:

The values in the ParentalWarningType tag are not intended to be used by the receiving DSP to determine whether to make available the relevant releases or resources to a specific audience.

Neither Apple nor Spotify publishes a rule tying the flag to a territory, to editorial playlisting, or to any kind of eligibility. That is not the same as saying no such rule exists inside either company. It is saying that if you have been told your record will be buried for carrying an E, nobody has published the document that says so, and you are being sold somebody’s theory as a fact.

What makes a version “clean”?

A clean version is a separate, edited recording, and the Clean tag is permitted only where an explicit version of the track exists.

Three documents say so, which is how you know it is a rule rather than a preference. Apple’s style guide, §6.2: “Only flag tracks as Clean if there is a corresponding explicit version of the track.” The Spotify Music Metadata Style Guide, at v2.3, §23.2: “Tracks should only be flagged Clean if there is an explicit version of the track.” And the Apple Music Specification, in the field definition itself: “A track must only be marked clean if it is an edited version of the original explicit form of the track.”

That specification is also where the field stops being a yes-or-no question. <explicit_content> takes three values, and the default is not the one anybody expects:

Denotes whether or not a track contains explicit content. May be clean, explicit, or none. If omitted, none (that is, a track for which neither a clean or explicit version exists) is assumed.

Read that carefully, because it reframes the whole field. none does not mean “this record has no swearing on it.” It means “this track is not one of a pair.” The field is answering which member of a set you are delivering, and the delivery standards underneath it agree — ParentalWarningType carries Explicit, ExplicitContentEdited, NotExplicit, Unknown, and UserDefined, and the value for a clean edit is literally named after the thing that was done to it.

Which is why you cannot make a clean version by changing a value. The edit is an audio job, it produces a recording that is not the one you started with, and a new recording takes its own code, on the standard’s own rules. Tick the box on the explicit master and you have not made a clean version; you have made a false claim about a file.

How much has to come out is a smaller question than it sounds, and the Standards answer it with unusual candour. An Edited Version is “recommended, although not required,” and it “need not remove all potentially objectionable content from the sound recording” — some may be kept, in the document’s own words, “in order not to compromise artistic expression.” The same compromise has been hanging in museums for centuries, and it is the size of a fig leaf.

Why can’t you write “(Clean)” or “(Explicit)” in the title?

Apple and Spotify both forbid the words Clean and Explicit in a title, because the flag already produces the badge.

Apple’s guide, §6.1: explicit content “must be flagged Explicit with a parental advisory tag,” and terms like “(Explicit),” “(Explicit Version),” “(Dirty),” or “(Dirty Version)” must not appear in album, ringtone, or track titles. The clean equivalents are banned in the same breath. Spotify’s §23.3 is the same rule with the mechanism spelled out: “Explicit and Clean must be entered using the proper tag, which is a separate field in metadata format, and not part of the track title.” The rest of what a title may not carry is the rejection piece’s subject, not this one’s.

There is a second instinct to unlearn, and Apple addresses it in §6.3. Titles go in “in the original form that was intended by the artist,” because “explicit words are automatically censored on Apple Music and the iTunes Store (for example, F**k). Do not insert the asterisks yourself.” Self-censored titles, Apple adds, affect “listeners’ ability to search for and find the content they’re looking for.” Type the word. Somewhere inside that company there is a machine whose entire working life is the asterisk.

And then there is the word itself, which is where two published documents point in different directions. The stores’ tag value is Clean. The RIAA’s Standards, governing what a digital platform may display, say a platform “shall not label an Edited Version of a sound recording distributed through a Covered Digital Platform as ‘Clean’ or ‘Non-explicit,’” and may use only “the words ‘Edited Version’ or ‘Edited’ to communicate the availability of an Edited Version.” Two texts, two surfaces: one governs a field in a delivery, the other governs what a shop puts on the page. Neither publishes a reading of the other, and this page is not going to invent one. What matters to you is the smaller half — the field takes Clean, and the title takes nothing.

What do the lyrics have to do with the flag?

Displayed lyrics are a separate delivery with their own rules, and neither the lyrics nor the flag sets the other.

The confusion here is built into the vocabulary rather than into anybody’s carelessness. Spotify’s own artist-facing name for this field is the “explicit lyric tag,” which reads as though the tag is attached to a lyric sheet. It is not. It rides the recording, it is delivered with the recording, and a track with no lyrics on file carries it exactly the same way.

The lyric sheet is a second delivery, and Apple’s lyrics guidelines govern it on its own terms. On an explicit track, “all explicit language must be transcribed as it is heard in the audio.” Where the audio itself censors a word, “partially or fully censored words must be completely starred out with asterisks.”

Put those two rules side by side and the principle falls out: the asterisks follow the audio, not the flag. A clean edit gets starred lyrics because you can hear the bleep. An explicit master gets the word in full because you can hear the word. Nobody is applying a policy to your writing; somebody is transcribing what is actually on the file.

So there are three surfaces, not one — the recording, the flag on it, and the lyric sheet beside it. Delivered separately, correctable separately, and perfectly capable of contradicting each other. Most of the “why is this song censored on one app and not the other” confusion in this business is two of those three disagreeing.

How do you fix a flag that is wrong on a live release?

An artist cannot change the flag on a released track: the label or distributor sends a metadata update, and the store shows what was delivered.

Spotify says both halves on its own page for fixing music that is already live: “We can’t change this manually on our end because we show music according to the metadata sent to us,” and “Your label or distributor needs to send a metadata update to us with the right info.” Explicit lyric tags sit on that page’s list of what needs one, beside artist name, artwork, dates, and credits. No setting in the app, no form for the artist, and an afternoon spent looking for either is an afternoon.

Before you file anything, work out which of two problems you have, because only one of them is metadata.

• The right audio, the wrong value. The explicit master is up and the flag says otherwise, or the reverse. This is a metadata update: one message from your distributor, and the badge follows.
• The wrong audio. The clean edit went out carrying the explicit version’s identity, or the other way round. No value fixes that, because the file is a different recording — which is a question about codes and versions, and a much longer afternoon.

Neither store publishes how long an update takes to appear, so nobody honest will give you a number for it. If the delivery has not gone out yet, none of this applies and the store guides are worth twenty minutes before you upload. And if what you are actually holding is a rejection rather than a live record, a flag is almost never the cause — the comparisons that stop a delivery are about names.

What to do before the next delivery

Set the flag from the audio, one track at a time, and know which of your tracks have clean counterparts and which do not.

Three things, none of which takes an afternoon:

• Play the track and set the value from what you hear, not from what the album feels like. The field is per track, and a record where one song swears is a record with one explicit track.
• Only mark something Clean if the explicit version is going out too. Where there is no pair, the value is the neutral one, and Apple’s specification says so in its own definition.
• Write down which track is which. A clean edit and its explicit original are two recordings with two identities, and six months later nobody remembers which file went where.

Then, for the back catalogue, the audit checklist finds the releases whose metadata nobody has ever read back and tells you which failures actually cost you something. A flag you guessed at is repeated by every system downstream, without argument, for as long as the record is up. It is the cheapest field on the form to get right and one of the slowest to correct.

FAQ

Can a store mark my song explicit if I didn’t?

Nothing either store publishes says it will. Spotify states that it tags explicit content from information received from rights-holders, and the RIAA’s Standards put the determination with the label or artist that owns the recording. What a store does publish is a route for a listener to report content, and what happens after a report is not published.

Does one explicit track make the whole release explicit?

The flag is set per track. Apple’s specification carries the value on the track and publishes no rule for deriving a release-level value from the tracks under it, and Spotify’s guide publishes none either. The RIAA’s Standards say only that they apply to a single track released commercially as well as to a full album.

Can I put the Parental Advisory logo on my own cover art?

Not without a written agreement with the RIAA. The Standards state that the RIAA owns all right, title, and interest in and to the Logo, and that a Participant shall not use, reproduce, display, or distribute it absent the execution of a separate written agreement. The explicit flag is a metadata field and needs no licence; the logo is somebody else’s mark.

Does an explicit flag keep a track off playlists or out of certain countries?

Nothing published says so. DDEX states that the parental warning values are not intended to be used by a service to decide whether to make a release available to a specific audience, and neither Apple nor Spotify publishes a rule tying the flag to a territory or to playlist eligibility. The one published effect is the listener’s own filter.

Sources

• RIAA, Parental Advisory Label Program Standards (PDF, effective 6 August 2025) — who makes the determination and that everyone else abides by it, the definition of PAL Content and the refusal to publish a word list, the Edited Version rule, the digital-platform display rules, and the licence position on the logo.
• Apple, Apple Music Style Guide — §6.1 the banned title terms, §6.2 why the Clean flag exists and when it may be used, §6.3 automatic censoring and the instruction not to type asterisks yourself.
• Apple, Apple Music Specification — the explicit_content field, its three values, what the default actually means, and the rule that only an edited version of the explicit form may be marked clean.
• Apple Music for Artists, Review guidelines for submitting lyrics — explicit language transcribed as heard, censored words starred out. The rule that makes the asterisks a fact about the audio.
• Spotify, Music Metadata Style Guide (v2.3) — §23.2 and §23.3: tag Clean only where the explicit version exists, and never in the title.
• Spotify, Explicit content settings — that the tag comes from rights-holders, and what the listener’s filter does to a tagged track.
• Spotify, Music metadata guidelines — the E icon, the instruction to keep it out of the title, and that metadata is set before delivery.
• Spotify, Fixing problems with music — that Spotify shows what was delivered, that the distributor sends the update, and that explicit lyric tags need one.
• DDEX Knowledge Base, Parental advice labels — the allowed values of ParentalWarningType, that they are not intended to decide availability, and that what counts as explicit varies by country and culture.

Store rules change, and the ones here are quoted as at the date at the top of this piece; the linked guides are the living documents and every one of them was read that day. The RIAA Standards are a US programme and bind the companies that sign its licence, not artists generally — where this page describes them, it is describing what the programme requires of its participants. Your own distributor’s form may name these fields differently; the values underneath are the ones above.

Keeping the register

The flag, the version, and the pair they belong to are three facts about one release, and the place they usually go missing is between an upload form you filled in once and a memory of doing it. CatalogTracker keeps parental advisory on the release beside the dates, the UPC, the territories, and the P-line, with version and recording type on each track, and a completeness meter that reports how many of a release’s fields are actually filled in rather than assumed. Knowing which of your tracks has a clean counterpart is the sort of thing that is obvious for about a month. In development for iPhone.