Am I Still an Artist If I Use AI? What the Credits Actually Say
Seven threads in eight days, 529 upvotes and comments between them, all circling one question: if a model made the sound, does the person who made the song still count. Nobody wins that argument, because nobody in it has the authority to settle it. What almost nobody arguing has noticed is that the platforms settled a version of it months ago, in fields you fill in at upload — four audio declarations at DistroKid, five transparency values at Apple, and a Spotify badge with a published eligibility rule. We read all of it at source this week, with the update dates, because three of those documents changed in the last fortnight.
- The short version: the platforms do not ask whether you are an artist. They ask which parts of the record were generated, and there are separate fields for the audio, the lyrics, the composition, the artwork, the video and whether your artist name is a real person. You are already in one of those categories.
- AI credits are narrower than most people fear: DistroKid says you need none for "Pitch correction, auto-tune", "AI-assisted mixing or mastering" or "AI-assisted workflows".
- Apple's specification added a Persona transparency value in October 2026, for an artist who presents as a photorealistic human "who does not exist" — and says the tag "is not dependent on AI use in the artist's music". Identity and production are two different fields.
- If you wrote the words and generated the audio, the one credit that is mandatory on the release is the one you earned. DistroKid: "you must first credit a songwriter, as this is mandatory for all songs." Apple requires a Composition and Lyrics role on every album and every track.
- Disclosing does not cost you placement. Spotify's own announcement says it is "not about punishing artists who use AI responsibly or down-ranking tracks for disclosing information about how they were made", and that "all music is treated equally, regardless of the tools used to make it".
Is AI music real music? The question has been asked seven different ways in r/SunoAI and r/aiMusic in the last eight days, and the threads have taken 57 upvotes and 472 comments between them without resolving anything, because resolving it was never available. "Lyricists have always been considered to be artists in their own right," runs the second-highest reply in one of them (r/aiMusic, 6 November 2026, 86 comments). "You're a lyricist if you do that, you objectively did not make the music," runs another, three points below it. Both have upvotes. Neither is going to persuade the other.
The cost of that stalemate is real, and it is not hurt feelings. A producer in the same window wrote that he works in Pro Tools and FL Studio, does his own drum programming, records his own vocals on an AT2040, and that putting his lyrics into Suno "discourages me to even create anymore" (r/SunoAI, 3 November 2026). He is deciding whether to keep making records on the basis of an argument with no referee.
There is a referee, though, and it has been quietly filling in the answer since April. Every major platform now has metadata fields that describe exactly what AI did on your record, who the artist is, and whether that artist is a real person — and those fields have consequences attached. We read DistroKid's help centre, Apple's delivery specification and Spotify's own policy announcements at source over 10 and 11 November 2026, with the update dates, because three of those documents changed in the last fortnight. Here is what they actually say.
The short answer, and why the argument never ends
The reason the thread never lands is that "artist" is doing two jobs in one word. One job is aesthetic: did you make something good, and was it hard. The other is administrative: whose name is on the record, which contributions are credited, and who gets paid. The first has no answer. The second has a published one, and it is specific.
Spotify named this problem itself, which is more than any page arguing about it has managed. From its AI policy announcement: "We know the use of AI tools is increasingly a spectrum, not a binary, where artists and producers may choose to use AI to help with some parts of their productions and not others. The industry needs a nuanced approach to AI transparency, not to be forced to classify every song as either 'is AI' or 'not AI'" (Spotify newsroom, 25 September 2025, updated after the April 2026 beta).
That is a company with 700 million users declining to answer the question the comment sections keep demanding a yes or no on. What it did instead was build fields. So the useful move, if you are the Pro Tools producer, is to stop asking whether you are an artist and ask which of those fields you are in — because the answer is checkable, it takes about a minute, and in most cases it is far less dramatic than the thread implies.
The platforms already answered this, in four declarations
Start with the distributor, because that is where the declaration actually happens. DistroKid's upload form asks whether any of the track was generated by AI, and if you say yes it makes you pick from four options. Two more questions cover the artwork and the video. This is the whole of what you are being asked:
| What the form asks | DistroKid's own wording | What it declares |
|---|---|---|
| The lyrics | "AI wrote the words" | A model produced the text. Your melody, your audio |
| The music | "AI composed the melody" | A model produced the composition. Your words |
| All of the audio | "everything the listener hears is AI-generated" | Triggers one further question — see below |
| Part of the audio | "some of it is AI, some is human" | The hybrid case. Most Suno-plus-DAW workflows land here |
| The artwork | Yes for "an image created from a text prompt"; no for "editing or touching up an image" | Separate field, separate asset |
| The video | Yes for "footage, scenes, or animation created with AI", including "people or performers created with AI" | DistroVid only |
Sources: How to Fill Out AI Credits, updated 25 August 2026; What Counts as AI-Generated Artwork? and What Counts as an AI-Generated Video?, both created 15 October 2026 and updated on 3 and 2 November 2026 respectively.
Read the list again and notice what is missing. There is no box for "are you an artist", no box for how much effort you put in, and no box for whether you can play anything. The questions are about assets. And the "All of the audio" branch asks the one genuinely interesting follow-up: DistroKid says it "will also ask whether your artist name is a human or an AI persona", because "streaming services need this to display your artist credit correctly on the track". Which means a real person releasing fully generated audio under their own name is not an AI act in the metadata. They are a human artist whose recording was generated — two separate facts, recorded separately.
Apple built a field for exactly this question in October 2026
Apple goes further, and this is the part nobody writing about AI music has caught up with. Its delivery specification carries an <ai_transparency> tag, and in version 5.3.27.1, dated October 2026, Apple added a fifth value to it for the specific purpose of describing an artist who is not a real person.
| Value | What Apple says it discloses | Level |
|---|---|---|
Composition |
"AI was used to generate a material portion of any music compositions embodied in a track" — including "a material portion of the lyrics" | Track or album |
Track |
"AI was used to generate a material portion of a sound recording" | Track only, all territories |
Artwork |
AI-generated album artwork, static or motion graphic | Album |
Music Video |
"AI was used to generate a material portion of the visual elements" | Video |
Persona |
"AI was used to generate a photorealistic human-appearing persona that could be mistaken for a real person" | Artist |
Source: Apple Music Specification 5.3.27.1, October 2026; the tag is optional and "if omitted, none is assumed."
The sentence that matters is attached to Persona, and Apple puts it plainly: "This tag is not dependent on AI use in the artist's music." It then sets three qualifications — the public identity has to centre on a human being "not a robot, mascot, illustrated character, logo, or abstract mark"; the depicted human must not correspond to "any real, living person"; and the depiction must be photorealistic enough "that it can be mistaken for a real person", with "obviously stylized, animated, illustrated, or intentionally non-human representations" explicitly below the threshold.
So Apple has formally separated the two things the Reddit threads keep fusing. Whether a model made your audio is one tag. Whether the artist is a person who exists is another, and it can be true of someone who records with a live band. If you are a real human being who generates tracks, none of the Persona conditions describes you — which is the clearest answer to the question in this article's title that any platform has published.
What counts as AI-assisted music, and what does not
The second thing worth knowing is how small the declaration actually is. AI assisted music — software working on material you made — is not what the credit fields are about at all. DistroKid's What Are AI Credits?, updated 2 November 2026, splits it explicitly:
| Needs an AI credit | Does not need an AI credit |
|---|---|
| "AI-generated audio (vocals, instrumental tracks, etc.)" | "Pitch correction, auto-tune, etc." |
| "AI-generated lyrics (not written by a human)" | "AI-assisted mixing or mastering" |
| "AI-generated compositions (melody or arrangement not composed by a human)" | "AI-assisted workflows" |
That right-hand column covers most of what a working producer does, and none of it is a disclosure event, because none of it generated creative content. The line is not "how much software did you use" but "did a model write or perform a material part of this". The conflicted Pro Tools producer from 3 November is, for almost everything he described, declaring nothing.
One limit worth stating: the same document names Spotify, Apple Music and YouTube as the services currently displaying these credits, and Spotify is candid that the system depends on honesty — "because we depend on artist disclosure, the absence of a credit doesn't mean AI wasn't used."
The one credit that is mandatory is the one you earned
Now the part that resolves the r/aiMusic thread outright. Seventeen of its 87 replies reach for the word "lyricist", and the argument underneath them is whether a lyricist is a songwriter. "While I agree that lyricists are artists, I don't consider lyricists to be songwriters," runs one. That distinction does not exist in the metadata, and the metadata is what pays.
The word "lyricist" appears zero times across all 421 of DistroKid's published help articles — we pulled the full corpus on 11 November 2026 and searched it. The role the system names is Songwriter, and it is the one credit you cannot skip: "When adding credits to a song for the first time, you must first credit a songwriter, as this is mandatory for all songs" (DistroKid, updated 29 June 2026). Apple is the same: a Composition and Lyrics role — "such as Songwriter, Lyrics, Composer" — is "required for albums and tracks", and should be "given to the artists that created the original written work, both the music and the words, if applicable".
Stack that up for the person who writes words and generates audio. The performance credit is the one they cannot claim. The composition credit is compulsory, theirs, and the only one that must be filled in before the release moves. And it is the credit most likely to be visible: DistroKid notes that services vary in what they display and that "most are starting with songwriters and producers". Two more practical details — credits "may take 1-2 weeks to appear", and the songwriter field wants a legal name rather than a stage name, which is a different rule from the artist name on the front of the release.
Is there skill in it? What actually transfers
The skill question deserves a straight answer rather than a defence. Some of what a musician spends years acquiring does not transfer, and pretending otherwise is why these threads go badly. Here is our reckoning, column by column.
| What a musician has | Transfers to AI work? | What the work becomes |
|---|---|---|
| Instrumental technique | No | Nothing replaces it. This is a real loss and the sorest point in every thread |
| Ear for arrangement | Yes, directly | Choosing between generations, cutting sections, deciding what the record needs |
| Tracking and comping | Partly | Comping across takes becomes comping across generations and stems |
| Mix and master decisions | Yes | Unchanged work on a different source file, and not a disclosure event |
| Lyric writing | Yes, entirely | The one contribution that is credited as a matter of course |
| Quality control at volume | Becomes the main job | Auditioning dozens of outputs and rejecting almost all of them |
| Session and room craft | No | Replaced by prompt and reference discipline, which is a narrower skill |
The highest-scoring reply in the 7 November skill thread put the surviving requirement in one line: "Music skills could certainly help but I think what's most important when it comes to creating ai music is taste" (r/SunoAI, 110 comments). That is less of a concession than it sounds. Taste at volume is a discipline, it is measurable in output, and it is exactly the thing an undiscriminating user does not have — which is the honest form of "yes, you can be bad at this".
Why openly AI music gets judged harder than AI that hides
One thread in the window asked why openly AI-created music draws more hostility than AI content that actually deceives people, and it is a fair question with an uncomfortable answer: disclosure makes you findable. The declared track carries a label; the undeclared one does not, because the system depends on self-reporting. People arguing in good faith end up arguing with the only people who put their hand up.
Some of the objection is also well founded, and conceding that is what makes the rest of this page worth reading. A reply in the skill thread said it cleanly: "the effort version and the low effort version sound the same to me… I can't tell from a blind test." That is the real complaint behind most of the hostility — not that a tool was used, but that volume has made listening expensive, and that the ratio of considered records to generated filler has moved against the listener. Spotify's own number gives the scale: over 75 million spammy tracks removed from the platform in twelve months. Our own figures on what that does to the audience problem are worse than most people expect.
Two cautions on sentiment, because it is routinely misreported in both directions. In the forums the dominant line this month is acceptance — people are comfortable being labelled if the release goes out. On short-form video the opposite framing is what travels, with "beat the AI music detectors" hooks taking hundreds of thousands of plays. Neither is "what creators think"; they are two different rooms, and quoting one as the consensus is how most coverage of this gets it wrong.
Where this leaves you commercially
Credit is not a market. The thing that actually determines whether any of this pays is whether anyone hears the record, and on that the threads are unanimous in a way they never are about identity: distribution is solved and discovery is not. A credit does not fix that. Neither does a badge.
Which is worth saying plainly about Spotify's new one. The Verified by Spotify badge, announced 30 April 2026, is assessed on sustained listener engagement, platform compliance and "signals of a real artist represented in the profile" — and Spotify's own wording is that "at launch, profiles that appear to primarily represent AI-generated or AI-persona artists are not eligible for verification", with the company conceding in the same post that "the concept of artist authenticity is complex and quickly evolving". DistroKid's summary of the same rule adds a reassurance Spotify does not put in those words: that artists using AI tools "as part of their creative process are still eligible, as long as they present themselves authentically". Attribute each half to whoever said it. The exclusion is Spotify's; the reassurance is DistroKid's reading.
| Your contribution | How it gets credited | What you can sell |
|---|---|---|
| Lyrics, AI audio | Songwriter credit, mandatory; AI credit on the audio | The recording, direct to listeners; the song for sync |
| Composition, AI performance | Songwriter and composer credit; AI credit on the audio | Both, plus a stronger sync case on the composition |
| Fully generated, your name | AI credit "all of the audio", artist name declared human | The recording. Not Spotify verification, at launch |
| Fully generated, persona act | Same, plus Apple's Persona tag if photorealistic |
The recording. Treat platform-level perks as unavailable |
| Human recording, AI mixing | No AI credit required | Everything, on normal terms |
So the practical move is to own the credit you earned and then put the record somewhere it can be bought and pitched rather than only streamed. Paid placement is where the money conversation in this niche actually is — sync deals in TV, film, games and advertising pay per use rather than per play, and they are judged on whether the cue fits the scene. A direct storefront is the other half: you keep the full amount and you own the relationship, which matters precisely because algorithmic discovery is the part nobody has solved. Worth noting the comparison people reach for first does not apply — Bandcamp bans AI-generated music outright, so it is not an option here.
What a credit does not do
Three limits, stated flatly, because overreading this page would be easy.
A credit does not change a label. The AI credits travel with your delivery, your distributor sends them, and each service decides what to show; nothing you do to the audio file afterwards alters that. Any tool claiming to stop a platform tagging your track as AI is describing something that does not exist.
A credit does not make you non-screenable. DistroKid's AI tag, documented since 2 November 2026, appears "when an independent service called ACRCloud flags a track as potentially AI-generated" — and DistroKid is clear that "the tag is informational. It doesn't affect distribution". What a file's own condition does affect is whether screening systems and listeners find audible generation artifacts in it, which is the narrow thing a cleanup pass like Undetectr addresses: release-readiness, not labelling. The distributor side is in declaring AI on a DistroKid release and who owns an AI song, and what your plan tier licenses is the one most people get wrong.
And a credit does not win the argument. It just means that when somebody in a comment section tells you your record does not count, you can answer with the specific line on the specific release that says what you did — which is a better position than having an opinion. The virtual acts in our rundown of the AI artists currently charting have been in that position for two years, and the one thing their metadata has never done is settle anyone's taste.
Questions readers ask.
As a question about the audio it is not in dispute: it is a sound recording, it is licensed, it is distributed, and it is paid on the same terms as everything else. What people are usually asking is whether the person behind it counts as an artist — a different question, answered differently on every platform, and the one this page works through.
On the release, yes, and it is the only credit that is compulsory. DistroKid's credits documentation says "you must first credit a songwriter, as this is mandatory for all songs", and Apple's specification requires a Composition and Lyrics role on every album and track, given to "the artists that created the original written work, both the music and the words, if applicable". The word "lyricist" does not appear anywhere in DistroKid's 421 help articles.
If AI generated the audio, the lyrics or the composition, that is what the AI credit fields are for, and DistroKid says the services currently displaying them are Spotify, Apple Music and YouTube. Apple's transparency tag is optional in its specification and "if omitted, none is assumed". Whether your distributor forces the question depends on the distributor.
No. DistroKid's "What Are AI Credits?" article, updated 2 November 2026, lists "Pitch correction, auto-tune, etc.", "AI-assisted mixing or mastering" and "AI-assisted workflows" under things you do not need to credit. The declaration is about generated creative content, not about software having been involved.
Yes, and that is a separate question the form asks you. DistroKid says that if you declare "All of the audio", it then asks "whether your artist name is a human or an AI persona", because "streaming services need this to display your artist credit correctly". A real person releasing fully generated audio under their own name is a human artist with a generated recording.
Spotify says it does not. Its September 2025 announcement, updated after the April 2026 beta, states the disclosure standard is "not about punishing artists who use AI responsibly or down-ranking tracks for disclosing information about how they were made". What does carry consequences is spam: Spotify says it removed over 75 million spammy tracks in twelve months.
The verdict, in one sentence: Undetectr.
One boundary first, because this page is about credits and it would be easy to over-read. Nothing you process changes how a platform labels your release: the AI credits go up with the delivery, your distributor sends them, and each service decides what to display. No audio tool touches that, and anyone telling you otherwise is selling you something that does not exist. What a tool can address sits at the other end of the job — whether the file itself is clean enough to ship, with the generation artifacts gone before a screening system or a listener finds them. That is the whole of what Undetectr is for, and it is the only reason it appears on a page about metadata.