DistroKid Rejected My Release: Editorial Discretion in 2026

DistroKid sends three different emails that all read as "your release was rejected", and only one of them has no fix. The takeaways below say which is which. Built by searching all 421 articles in DistroKid's help centre at source, reading its Terms of Service and the AI rules at seven other distributors. The emails are artists' public posts, not DistroKid policy. Research page, not legal advice.

Filed 2026-09-30 Read 14 min Method How we work
In short
  • Three DistroKid rejection emails exist and two are fixable. The one saying "editorial discretion" adds that "stores are no longer accepting releases from you via DistroKid" and that DistroKid "cannot assist with reversing this." The short version: it is an account decision, made elsewhere.
  • "We've been notified by stores and streaming services" puts the decision at the services, not the distributor — DistroKid's own words are "We're just the messenger." Hence no appeals route.
  • We searched all 421 articles in DistroKid's help centre on 6 November 2026: "editorial discretion" appears zero times, "appeal" zero times, and no article covers losing an account.
  • An AI tag is not a rejection: DistroKid names ACRCloud as the detector behind it and says the tag "doesn't affect distribution." Its Terms make refunds "in Distrokid's sole discretion."
Flat vector illustration on white: a grey envelope-and-relay icon on the left sends a hot pink arrow toward three dark storefronts with pink awnings and shuttered fronts on the right, where a solid pink barrier bars all three entrances, while a grey dotted line runs back from the storefronts to the relay icon
The relay is not the decision. The refusal starts at the storefronts and arrives in your inbox from the company you pay.

DistroKid rejected your release, you opened the email expecting a formatting note, and instead read that stores will not take anything from you through DistroKid again. That is not the rejection DistroKid's help centre documents, which is why the search you just ran returned forum threads.

The email, quoted from an artist's public post on 20 September 2026 that drew 106 comments:

"We've been notified by stores and streaming services that one or more of your releases has been rejected due to editorial discretion. Unfortunately, stores are no longer accepting releases from you via DistroKid. You'll need to try another distributor for future releases. Please understand that DistroKid is unable to assist with reversing this and many DistroKid features have also been restricted as a result of this. We have no other information or context, and we are unable to get involved or take sides when this occurs. We're just the messenger, passing along this info to you in hopes you find it helpful."

Two things are at stake and only one is as bad as it looks. Future releases through this distributor are over. But the second worry — "if I just changed my distributor, DK would delete all my publishes e.g. reset counter to zero" — is mostly recoverable, on DistroKid's and Spotify's own documentation.

Every rule quoted below was read at source, on 30 September 2026 unless a later date is given.

Three rejection emails, three different problems

DistroKid's help centre documents two rejection types. The third is the one in the thread, and the only one with no remedy.

Formatting or artwork rejection Verification request Editorial-discretion lockout
What the email says Your upload was rejected; details are in the email Stores require you to verify your artist name "Stores are no longer accepting releases from you via DistroKid"
Who decided The store's automated review of that release The store, about the name on that release "Stores and streaming services", relayed by DistroKid
Scope One release One release Your account, plus restricted DistroKid features
Reversible Yes — fix and re-upload Yes — verify and it delivers DistroKid "is unable to assist with reversing this"
What you do Delete and re-upload with the fix, or use Replace Artwork DM @distrokid with the UPC, or send photo ID Nothing at DistroKid. Move, and protect what is live
Documented by DistroKid Article 10405555881619, updated 31 Jul 2026 Article 10405531090835, updated 5 Aug 2026 Nothing

That last row is why this page exists. The article Google ranks for a DistroKid rejection has one sentence for anything it does not cover: "If you think your release was rejected in error, just reply to that email for more information." Set that against a notice saying DistroKid cannot reverse it and will not take sides. The page that ranks is answering a different question, and no independent publisher has answered this one.

One detail before you act: the verification case explicitly tells you not to delete — "deletion and re-upload is not necessary if services require verification for your upload." Deleting a release that needed only a DM is the most common mistake in the threads.

Table comparing DistroKid's three rejection emails across five rows - who decided, scope, reversible, what you do, and what DistroKid documents - showing that only the editorial-discretion lockout is account-wide, irreversible and documented nowhere
Guessing wrong costs days re-uploading a release that was never the problem. Only the third column has no remedy.
Screenshot of DistroKid help article 10405555881619, Handling a Rejected DistroKid Release, showing the paragraph ending “just reply to that email for more information” and the note that “deletion and re-upload is not necessary if services require verification for your upload, or if your artwork was rejected”
The help article Google ranks for this query. Its whole remedy for anything it does not cover is one sentence — and the account-level case is not in it.

What "editorial discretion" actually means

Two clauses of that email relocate the decision: "We've been notified by stores and streaming services", and "We're just the messenger." Editorial discretion is not DistroKid judging your music — it is DistroKid relaying a refusal from the delivery destinations.

Which is why searching for a DistroKid appeals process returns nothing useful. There is no published appeals route because the party you pay is not the party that decided. The distributor has a support inbox and no authority; the decision-maker has authority and no relationship with you.

Other distributors put the same arrangement in their own documentation, which makes it structural rather than a DistroKid quirk. LANDR warns that "certain platforms may reject content that was previously accepted."

What is not knowable, whatever any page claims: which store objected, which release triggered it, what rule it fell under, and whether the restriction covers every service or some.

The AI tag, and the detector DistroKid now names

Something changed while this page was live: for the first time, a major distributor has named the thing doing the detecting. On 2 November 2026 DistroKid published Why does my track have an AI tag?, edited again on 6 November. A tag appears, it says, "when an independent service called ACRCloud flags a track as potentially AI-generated."

Read the rest carefully — it is narrower than it sounds:

What DistroKid documents In its own words
What the tag is for "Some streaming platforms now require distributors to identify AI-generated music"
What it does to your release "The tag is informational. It doesn't affect distribution through DistroKid"
Who decides what listeners see "Each streaming platform decides how it displays and handles AI-generated music"
If you did use AI "Nope, and there's nothing you need to do. We pass the info along"
If the flag is wrong "Third-party detection tools aren't perfect" — a correction form, reviewed "typically within 24-48 hours"

So a tag is not a rejection, and it is not the email this page is about. The correction route is for a track flagged incorrectly — not a way to take a tag off music that is in fact AI-generated. No audio tool changes how a platform labels a release.

The dates are worth laying out. On 14 October 2026 UMG and Sony asked a Manhattan federal court to compel DistroKid to produce records about its AI screening, including, per Music Business Worldwide's reading of the motion, "the name and vendor of the model" and "any analysis DistroKid has of its accuracy." DistroKid's 9 October response had described a third-party "prediction model" without naming it; on 2 November the help centre named ACRCloud. Whether the service in the help article and the model described to the court are the same thing is not established anywhere public, and the order of these dates is a sequence, not a cause — but the vendor question the labels went to court over now has a published answer in DistroKid's own support hub. TuneCore, separately, now says it has "implemented AI detection technologies across the catalogue we administer."

What this establishes is that screening exists, is outsourced, and is admitted to be imperfect by the company running it.

What can trigger it, and what almost certainly did not

DistroKid's published AI rules are short and worth reading before you build a theory. From article 41182362733715, updated 19 August 2026, which opens "Yes—DistroKid accepts music created with AI tools, but there are some rules":

DistroKid's published rule In its own words What it rules out
You must own the rights "You must own 100% of the rights, including the legal right to distribute music created with any AI tools, samples, lyrics, etc." Uncleared samples, and generator terms that do not grant you distribution rights
No impersonation "Your music cannot mimic or copy someone else's voice, likeness, or identity without permission" Voice clones, and near-matches to an existing act's name
No mass-generated spam Music "created solely to game streaming algorithms or flood platforms with generic content" Bulk drops of interchangeable tracks
No infringement "Your release cannot infringe on anyone else's rights" Everything the first three miss

The clearest published description of the behaviour that gets accounts flagged comes from a different distributor. UnitedMasters' spam guidance (15 September 2026) names "rapid-fire uploads", duplicate content under slightly different titles, and "ultra-short tracks", and puts the consequence with the platform: "streaming services reserve the right to remove flagged tracks or entire releases from their platforms completely."

Now the calibration, because the thread got it wrong. The top replies assumed volume: "you must be dropping an absolute mountain of AI slop". The poster's own figures are two artist names, two to four releases a month, under 100 songs in more than two years. Compare the scale in UMG's complaint against DistroKid, filed September 2026 and reported by Variety, where UMG alleges:

Account UMG names Tracks alleged Alleged AI share
Lofi Chill 4,562 in a single 12-month period —
Chill Flow Radio 1,901 More than 97% identified as Suno output
Mellow Vibes Radio 1,615 More than 98% identified as Suno output

A second lockout on 26 October 2026, 64 comments, makes that sharper. This artist was blocked a week after paying for a year; support cited "editorial discretion" on 12 October and answered which store and which rule with "we have no other information." Their own guesses — moving songs to a new artist name and re-releasing them, several releases in one week, "some had sped up versions" — are guesses, not confirmed triggers, and they added the line that matters: "but nobody told me any of that was a problem." Two readers, two profiles, the same silence. One detail recurs in both, and distributors publish rules about it: two artist projects on one account. Downtown requires "a clear and consistent digital footprint" behind a verifiable identity.

Table of DistroKid's four published AI rules from article 41182362733715 - you must own 100% of the rights, no impersonation of a voice, likeness or identity, no music made solely to game streaming algorithms, and no infringement - each paired with what it rules out
Using a generator is not on the list. The rules prohibit behaviours, and DistroKid has accepted AI-assisted music in writing since May 2025.
Table setting the three accounts named in UMG's September 2026 complaint - Lofi Chill at 4,562 tracks in a single 12-month period, Chill Flow Radio at 1,901 with more than 97% identified as Suno output, and Mellow Vibes Radio at 1,615 with more than 98% - against the reader in the thread, who released under 100 songs in more than two years across two artist names
The thread's top-voted theory was volume. These are allegations, not findings, but as a yardstick they settle it: three releases a month is not the activity in the filing.

What DistroKid documents, and the three things it never has

The gap between the email you got and the help centre you searched can be measured. We pulled all 421 articles from DistroKid's help centre through its own API on 6 November 2026 and searched every one.

What you searched for Occurrences in 421 articles What is documented instead
"editorial discretion" 0 Nothing. The phrase support sends you appears nowhere in DistroKid's own documentation
"appeal" 0 One remedy, for release-level rejections: "just reply to that email" (article 10405555881619, itself updated 29 Oct 2026)
Account termination 0 articles The only "terminate" hit in the corpus is a network-timeout error page
AI upload rules 1 article, updated 19 Aug 2026 Four rules: rights, impersonation, spam, infringement
AI disclosure 4 articles, updated 25 Aug to 6 Nov 2026 AI Credits, artwork, video, and the AI tag

DistroKid has written four articles about AI disclosure in eleven weeks and none about losing your account.

The line it now draws for the music itself is new since 30 September, and it is the part you can act on. What Are AI Credits? (updated 2 November 2026) separates generating from assisting for the audio, not just the artwork: disclose "AI-generated audio (vocals, instrumental tracks, etc.)", lyrics "not written by a human", or AI-generated compositions. You do not need AI credits "if you just used AI as a tool" — pitch correction, auto-tune, "AI-assisted mixing or mastering", "AI-assisted workflows." Spotify, Apple Music and YouTube show the field to listeners.

And the money. DistroKid's Terms of Service, as of 24 September 2026, answer the annual-plan question in six words: "Any refunds are in Distrokid's sole discretion." The same document reserves the right to "terminate the Accounts of any users for any reason, in DistroKid's sole discretion" — any reason, with no obligation to state one. The contract permits exactly what the thread describes and the help centre explains none of it. Treat the rest of a prepaid year as money you may not get back, and ask for it in writing anyway.

So what do you actually send? There is no appeals process, but four things are worth doing for what they protect.

What to send Realistically achieves Why bother
Reply asking which store and which release Probably nothing One email, and a specific answer changes everything
Ask if the restriction is store-specific or all destinations Occasionally answerable It decides whether moving helps
Export every ISRC and UPC before you touch the account Fully in your control The codes let a new delivery inherit your stream history
Save the notice, dates and any reply Fully in your control Your new distributor will ask why you left

Do the third one today — "many DistroKid features have also been restricted" is in the email, and you do not want to discover next month that you cannot read your own metadata. Our guide to what an ISRC is and why it stays with you covers what to copy: ISRC, UPC, exact release title, artist name and release date, per track.

Moving distributor without losing your streams

Streams attach to the recording, not to the company that delivered it, and both parties publish the mechanics.

Spotify, in how your streams are counted: "If a recording or release becomes unavailable on Spotify, we retain its all-time stream count for 90 days." After that window it "will not retain or reflect its previous stream count." The clock only starts if the release goes away.

DistroKid publishes the procedure itself, written for artists arriving — the same sequence works leaving. From its switching guide, updated 30 August 2026: upload to the new distributor first, "the next day, go to your old distributor and remove those releases", and the brief overlap "is okay". Use "the exact same metadata (song titles, album title, ISRCs, etc.) and audio files", with DistroKid's own caveat that it "can't guarantee that these play counts and playlist placements are maintained."

What moves with you What is at risk What does not transfer
ISRCs — yours to reuse on the new delivery Playlist placements, editorial and algorithmic The DistroKid-issued UPC (each distributor mints its own)
Stream history, if the gap stays inside Spotify's 90 days The original release date, if the delivery reads as new Your DistroKid HyperFollow links
The artist profile and its followers iTunes and Amazon reviews, which DistroKid says "you may lose" Whatever caused the store-level restriction
Earnings already accrued — DistroKid pays out on deleted releases Track-linking, which is the store's call

Two traps. First, do not cancel the subscription as step one. DistroKid states that if you do not renew, "your music will be removed from services" unless each release carries the optional Leave a Legacy extra — per release, not per account. Deliver elsewhere, confirm, then cancel. Second, let the new distributor auto-generate fresh ISRCs and you have published a different recording as far as the stores are concerned. Our comparison of music distribution services covers who lets you specify your own ISRC on which plan.

And the caveat no page wants to print: because the decision came from stores, it may follow you. One commenter reported the same outcome at a different distributor — "same answer, nothing but it's over and don't ask why."

Which distributors are realistic after a lockout

A list of "distributors that allow AI music" is not the useful question. What each one tests is, because that decides whether your catalogue is eligible. Rows read at source on 30 September 2026.

Distributor The test it applies Published restrictions Policy dated
DistroKid Your rights and behaviour. No model test Four rules: 100% rights, no impersonation, no mass-generated spam, no infringement 19 Aug 2026
UnitedMasters Rights and release patterns. No model test Unlimited submissions, but high-volume AI uploads "may be flagged for spam"; warnings, then holds 28 Sep 2026
RouteNote Rights, and may ask where the audio came from No Content Recognition options, no Amazon, no Melon, Genie, Bugs, Flo or Vibe 17 Aug 2026
LANDR Detection technology, then a monthly cap by plan 20 AI tracks a month on entry tiers, 60 on Pro; no AI covers; excluded from YouTube Content ID, Meta, TikTok, Deezer, Lissen, Pandora, Tencent 30 Sep 2026
Amuse Rights and impersonation. No model test Excludes Qobuz, Meta and YouTube Content ID; AI covers rejected 18 May 2026
Symphonic The model's licensing, plus mandatory disclosure at upload Acceptance "does not guarantee acceptance by every DSP or partner" 22 Sep 2026
TuneCore / Believe The model's training data, strictly — "only distributes music created using GenAI models trained on fully licensed datasets", applying "if GenAI is used at any point" One approved partner named: Google Flow Music 30 Sep 2026
Downtown / CD Baby The model's training data Prohibits content "created wholly or primarily by AI models trained on copyright protected sound recordings without a license"; penalties include account termination 4 Sep 2026

Re-checked 6 November 2026: LANDR's article and TuneCore's framework were both edited on 5 November, and both rows are unchanged in substance.

Two caps that circulate on comparison pages are wrong at source: LANDR's is no longer a flat 12 or 30 but a tier table topping out at 60, and Amuse publishes no AI volume limit at all. More in how distributors screen for AI and DistroKid's AI music policy.

A cleanup step, where it fits, fixes the upload gate only: processing a generated track so it clears automated screening does nothing about an account-level restriction a store has imposed, nothing about a rights claim, and nothing about how a platform labels a release. If your last release bounced on screening rather than account standing, the tool below is relevant. If you got the editorial-discretion email, it is not.

Table of eight distributors and the test each applies: DistroKid, UnitedMasters, RouteNote and Amuse test your rights and behaviour with no model test, while LANDR applies detection plus a monthly cap, and Symphonic, TuneCore/Believe and Downtown/CD Baby test the model's own licensing or training data, each row carrying its published restrictions and policy date
The distributors that test the model rather than your paperwork are the ones a Suno or Udio catalogue struggles with. Every row read at source on 30 September 2026.
Screenshot of TuneCore's GenAI Music Content Framework stating that music created using GenAI models that rely on fully licensed datasets is eligible for distribution while music generated using models that rely on unlicensed datasets is not eligible, and naming Google Flow Music as its partner platform
TuneCore in its own words. One approved partner is named on the page, and it is not a consumer generator.

Where the money goes while you are locked out

The unglamorous good news: what is already live keeps earning, and DistroKid confirms even a deleted release pays out — "you will still receive any due earnings for a deleted release for the time it was live." What you lost is the ability to ship anything new.

Which reframes the problem. For most people making music with these tools, distribution was never the wall — an audience was, which is the argument of why nobody listens to AI music.

So stop treating the DSPs as the only destination. The route with real money attached is paid sync placement — a track licensed into a TV show, a game, an ad or a video, paying a fee per placement and not depending on algorithmic discovery; our sync licensing guide covers how the briefs work. Played.fm is the platform we cover for pitching finished tracks at those placements, and it runs a direct storefront where you keep 100% — worth it because you own the customer, not because the percentage beats streaming maths that starts from a fraction of a penny.

A finished catalogue and no distributor is worse than last week. It is not the same as having nothing to sell.

Last updated 6 November 2026: DistroKid's help centre searched in full through its API, its Terms re-read, the LANDR and TuneCore rows re-checked. Other distributor policies were read at source on 30 September 2026. The rejection emails are artists' public posts, not DistroKid policy. Research page, not legal advice.

Frequently asked

Questions readers ask.

DistroKid's email says it "is unable to assist with reversing this" — which means DistroKid cannot lift it, not that no route exists anywhere. Any reversal would come from whichever store objected, and none publishes an appeals process for a distributor-relayed restriction. Treat it as durable.

The email is about future releases and says nothing about existing ones; the artists reporting it describe live catalogues that stayed up. What definitely removes them is letting the subscription lapse — if you do not renew, DistroKid states, "your music will be removed from services" unless each release carries the Leave a Legacy extra.

Do not treat that as the plan. The restriction came from stores, so a fresh account does not address whatever they flagged, and a new name collides with the authenticity rules most distributors publish. Downtown reserves "closure of specific user accounts, or even termination of your entire deal" for trust-and-safety violations.

No. Per DistroKid's article of 2 November 2026, a tag appears when "an independent service called ACRCloud flags a track as potentially AI-generated", and "the tag is informational. It doesn't affect distribution through DistroKid." Each platform decides how it displays AI music. If the flag is wrong, DistroKid links a correction form reviewed "typically within 24-48 hours".

Ask, but do not count on it. DistroKid's Terms, as of 24 September 2026, say "any refunds are in Distrokid's sole discretion", and reserve the right to "terminate the Accounts of any users for any reason." No help-centre article covers refunds after a restriction. Put the request in writing anyway.

The email gives no reason and DistroKid says it has "no other information or context", so anyone naming the cause is guessing. What is documented: DistroKid accepts AI music under four published rules, and its own AI tag is "informational" and does not affect distribution. Anti-spam policies describe release patterns, not the tool used.

The verdict, in one sentence: Undetectr.

If the thing standing between you and a release is automated AI screening at the distributor, or audible generation artifacts you can hear in the master, Undetectr is the tool we cover for that step — it processes a generated track so it clears distributors' automated checks. Its limits matter more than usual on this page: it does nothing about an account-level restriction that a store has already imposed, nothing about a rights claim, and nothing about how a platform labels or credits a release. It addresses the screening gate on a new upload. It does not reopen a closed door.