Can you sell AI music on Bandcamp, or will it be removed?

At the time of writing, Bandcamp's own policy says music generated wholly or in substantial part by AI is not permitted, and tracks can be removed on suspicion. What that means for a generated track, an AI-drafted lyric, and a song you played yourself.


Release A: "Neon Harbour" (EP, 5 tracks)
  Audio:   generated end to end in an AI music generator
  Lyrics:  generated in the same session
  Prompt:  "synthwave in the style of <a well-known act>"

Release B: "Night Bus Home" (single)
  Audio:   guitar and piano played and recorded by you
  Vocals:  your voice
  Lyrics:  first draft from an AI lyric generator, every line then rewritten by you

Put those two releases next to Bandcamp's rules and they get very different answers. At the time of writing, Bandcamp's own pages say that music and audio generated wholly or in substantial part by AI is not permitted on the platform, that using AI tools to impersonate other artists or styles is prohibited, and that Bandcamp may remove music on suspicion of being AI-generated. Release A matches that wording on every line. If you upload it, you are betting against the published policy, and what is at stake can be more than one EP: the policy lists losing access to the site among possible actions.

Release B lands in the part Bandcamp has not drawn a line through. The policy does not say how much AI help counts as "substantial", and nobody outside Bandcamp can tell you where that line sits. So the honest answer to the headline has two halves. A track a generator made for you is, going by Bandcamp's own wording, something you should not try to sell there. A song you played and sang yourself, with AI somewhere in the drafting, is a judgment call that belongs to Bandcamp, and the safe move is to ask before you upload, not after a report comes in. None of this is legal advice, and Bandcamp can change the rules; read the current pages yourself before you decide.

What Bandcamp's own pages say, at the time of writing

Two places matter, and both are Bandcamp's, not a news write-up of them.

The first is the blog post of 13 January 2026 titled "Keeping Bandcamp Human", on blog.bandcamp.com. It sets out the generative AI policy in a few sentences: the ban on music generated "wholly or in substantial part by AI", the ban on using AI to impersonate other artists or styles, an invitation to fans to report tracks through the site's reporting tools, and the reservation of the right to remove music on suspicion. It also says Bandcamp will communicate updates as the field moves, which is a plain warning that the text you read today may not be the text next year.

The second is the Acceptable Use and Moderation Policy in the Bandcamp help centre. It carries a similar prohibition in its own words, covering content wholly or in substantial part created, composed or generated by AI, and it describes the machinery around a removal: that decisions come with a statement of reasons, that there are appeal steps (written, at the time of writing, for EU citizens), and that enforcement can reach as far as account suspension. The page shows a "last updated" date. Look at it every time you check, because that date is the quickest way to know whether anything moved since you last read it.

Three things in that wording are worth reading slowly.

  • "Composed" sits next to "generated". The help centre sentence is about music and audio, but it names composing as well as generating, and a lyric and a melody are part of what gets composed. That is why Release B is not automatically in the clear just because you sang it.
  • "Substantial" has no number attached. No percentage, no list of allowed tools. A mastering plugin with machine learning inside, a chord suggestion, a lyric draft you rewrote: the policy does not sort these for you.
  • Removal works on suspicion, and reports come from people. There is no upload test you pass once and forget. A listener can flag a release months after it went live.

Where the lyric generator fits, and where it does not

This is the part where we have something to sell, so it is fair to say exactly how far it goes.

The lyrics generator at /generators takes a short brief and returns a title and a full lyric with [Verse] and [Chorus] tags. One generation uses 20 credits, which is $0.20 inside a plan (plans start at $5 a month). It does not sing and never makes audio. That is still AI-written text, and for Bandcamp that matters: a lyric pasted in unchanged is AI content in the plain sense of the word, whatever you do with the music around it.

So for a Bandcamp release, treat the generator as a sketchbook, not a supplier. It is good at the blank-page problem: it hands you a structure, a title, a set of images tied to your brief, and a chorus you can argue with. Then you take it apart and write your own lines on top. Whether the result counts as substantially AI under Bandcamp's wording is still Bandcamp's call, not ours and not yours. What the rewrite gives you is a lyric in which you wrote every line, with a draft file that shows where you started and where you ended up.

If your music is generated and you simply want somewhere to sell it, Bandcamp is the wrong door, and there are others with different rules. The wider map of where AI-made tracks can go, from sync libraries to commissions, is in where you can actually sell AI-made music. If you are going to streaming instead, the questions to ask a distributor about AI songs is the page for that. This article stays on one store and one question.

Three kinds of track, three honest answers

Generated end to end. A full track from Suno, Udio or any other generator that makes the vocals and the backing. This is the case the policy was written for. It does not matter how good the prompt was, how many takes you rolled, or whether you trimmed the intro in an editor afterwards. Uploading it means relying on nobody noticing, and the policy invites people to notice.

Generated, then worked on. You exported stems, replaced the drums, re-recorded the vocal, added a guitar part. Now the question is how much of the finished recording started life in a generator. If the harmony, melody and arrangement came out of the model and you dressed them, that still reads a lot like "substantial part". If you kept only a texture and rebuilt the song around it, it reads less so. Neither reading is a ruling. Write to Bandcamp support with a plain description and keep the answer.

Made by you, with AI in the drafting. You played it, you sang it, and somewhere in the writing a tool helped: a lyric draft, a rhyme list, a title idea. This is the grey zone, and the only people who can make it less grey are at Bandcamp. The less of the generator's text survives into the final lyric, the less there is to argue about.

The word "styles" and why it catches people

Most readers skim past the second half of the policy sentence. It prohibits using AI tools to impersonate other artists or styles, and it ties that to the existing rules on impersonation and intellectual property.

That clause matters for the kind of prompt people love most: "in the style of" a named act. A generated track built to sound like a specific band is the exact thing the sentence describes, even before the question of how much AI is in it. Our own catalogue has nearly 2 000 styles and more than 1 000 artist-style prompts, and the artist ones are written for Suno as descriptions of a sound rather than a name to copy. They are a tool for tracks you release elsewhere. They are not a way to get a Bandcamp release past this clause, and we would not suggest using them that way.

A rewrite that leaves the draft behind

Here is what "sketchbook, not supplier" looks like in practice. The brief uses only values the form actually offers:

theme:     night bus home after my father's shop closed for good;
           the sign still lit in the dark window, keys in my pocket
           I don't need anymore
language:  en
POV:       first
emotion:   longing
structure: classic
hook:      title-line
vocal:     male
age:       25-34

An illustrative draft chorus of the kind that comes back from a brief like that:

[Chorus]
The sign is still lit on the corner tonight
Keys in my pocket I don't need anymore
I ride the last bus through the city lights
Leaving behind what we were working for

It is serviceable and it is not yours. Almost every image in it is one you put in the brief, arranged by the model, and the rest is filler. Now the rewrite:

[Chorus]
Dad's sign still burning for nobody at all
Thirty-one years and a padlock on the door
I've got his keys and nowhere they belong
Night bus shaking me home past the store

Count what survived: the lit sign, the keys, the night bus. Not one line survived word for word. The thirty-one years and the padlock are facts the brief never contained, which is the point. A generator can only give back what you put into the brief. The details that make a lyric specific come from the person who knows them, and those are also the details that make it a lyric you wrote.

Keep both files. If a question ever comes up, the draft next to the final version is a clearer answer than any explanation.

Keep a provenance note for every release

Bandcamp's process involves reports, human review and a statement of reasons. If your release is ever questioned, you want to answer in two minutes with facts, not reconstruct the album's history from memory. A short note per release does that:

Release:   Night Bus Home (single)
Music:     guitar and piano, played and recorded by me, August 2026
Vocals:    me
Lyrics:    first draft from an AI lyric generator (saved as draft-v1.txt),
           every line rewritten by me (final-v3.txt)
Audio generators used:   none
Artists named in any prompt:   none
Checked Bandcamp AI policy on:  [date]  (help centre page "last updated": [date])

The last line earns its place. Policies in this area change, and the note shows that you checked the version in force when you released, not a version from a year before.

This note is also honest by design. It says where AI was used, not only where it was not. Hiding the lyric draft would not change what the policy says; it would only change when you find out how Bandcamp reads your release, and under worse conditions.

If a release is removed

According to Bandcamp's moderation page, a removal comes with a statement of reasons. The appeal steps the page sets out, with an email address and time frames, are written for EU citizens at the time of writing, so check whether they apply to you and, if they do not, ask Bandcamp support what route you have. Follow the page itself, not a summary here. Answer the reason you were given, attach the provenance note and the drafts, and describe the process plainly. Do not argue that the policy is wrong in an appeal about whether you broke it.

If the release really was generated, the practical answer is to take it somewhere whose rules allow it, and keep your Bandcamp page for the human-made catalogue. Losing one EP is recoverable. The policy also names account suspension among possible actions, and that would take your other releases, your fan list and your sales page with it.

Ownership is a different question from Bandcamp's rules

Bandcamp's policy decides what the store accepts. It does not decide who owns the song. Those are separate questions, and people who mix them up get surprised twice. Copyright offices in some countries, the US Copyright Office among them, have taken the position that output produced from a prompt alone, without meaningful human creative contribution, is not protectable. Our own disclaimer says the same about our generator: commercial use is allowed, we claim no rights in the output, but the rights you get are non-exclusive, similar briefs can produce similar text for different users, and we do not clear anything against anyone else's rights.

For the longer version, who owns AI-generated music separates the licence from copyright, and whether you can sell Suno songs covers the generator's own terms. Neither of those pages is legal advice, and neither is this one. Where money or a dispute is involved, ask a lawyer in the country where you live and publish.

FAQ

Does Bandcamp scan uploads for AI? Bandcamp's pages describe reports from users and human review, and the moderation page says decisions are made by people. Whatever tools may exist behind that, the working rule for you is the same: assume a track can be questioned at any time after it goes live.

Is a song with AI-written lyrics allowed if I play and sing everything? The policy does not answer that directly. Lyrics are part of what gets composed, and "substantial part" has no definition. Rewriting the lyric thoroughly shrinks the question; asking Bandcamp support settles it for your case.

Can I label my track as AI-assisted and upload it anyway? Going by the policy as currently worded, a label does not change what is prohibited. If the audio is generated, saying so is honest, but the wording gives no sign that disclosure makes the track allowed.

What about AI mastering or noise removal? The policy does not list tools. If you are unsure whether a processing step counts, ask Bandcamp rather than guessing, and note what you used in your provenance file.

Where can a fully generated track go instead? That depends on the store, the distributor and the licence of the generator you used. Start with where AI-made music actually sells and the broader money side of AI music.

The move that makes sense before you upload

If the song is yours and only the words are stuck, start from a draft and rewrite it until every line is one you would defend. One lyric draft on the lyrics generator uses 20 credits, which is $0.20 inside a plan. New accounts start with no credits, so the cheapest way in is $5 a month: 500 credits every month (25 lyric drafts) plus the catalogue and prompt generator. $19 once keeps the catalogue and prompt generator for good and comes with 1 500 credits, which is 75 lyric drafts, once. Write the brief, take the draft apart, keep the files, and check Bandcamp's policy page on the day you release.

Keep reading