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 reading the five DistroKid help articles at source on 30 September 2026, the published AI and spam rules at seven other distributors, and Spotify's own documentation on what happens to a stream count when a release goes away. The email is quoted from one artist's public post, not DistroKid policy. Research page, not legal advice.

Filed 2026-09-30 Read 12 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."
  • "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: you have no contract with whoever decided.
  • The help article that ranks for this — 10405555881619, updated 31 July 2026 — covers formatting, verification and artwork, and its remedy is "just reply to that email." It never describes the account-level case.
  • Your stream counts are least at risk. Spotify retains a release's all-time count for 90 days of unavailability, and DistroKid's own switching guide says to deliver through the new distributor first, reusing the same ISRCs and audio.
  • The thread's top-voted theory was volume. The poster's own figures — under 100 songs in over two years across two artist names — are nowhere near the accounts UMG alleges released 4,562, 1,901 and 1,615 tracks in twelve months.

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

Here is 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 poster's second worry — "if I just changed my distributor, DK would delete all my publishes e.g. reset counter to zero" — is mostly recoverable, and the documentation proving it comes from DistroKid and Spotify themselves.

Below: telling the three emails apart, where "editorial discretion" locates the decision, what plausibly triggered it, how to move a catalogue without zeroing it, and which distributors are realistic afterwards. Every rule quoted was read at source on 30 September 2026.

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. Guessing wrong costs days re-uploading a release that was never the problem.

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.

What "editorial discretion" actually means

Read the email's first clause again — "We've been notified by stores and streaming services" — and then its fourth: "We're just the messenger." Those two sentences relocate the decision. Editorial discretion is not DistroKid judging your music — it is DistroKid relaying a refusal from the delivery destinations. One commenter read it correctly: "That wording matters. It says stores notified them, so the call came from the DSP side and DistroKid is passing it on."

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. No store publishes a form for an artist whose deliveries a distributor says they no longer accept. The distributor has a support inbox and no authority; the decision-maker has authority and no relationship with you.

Two other distributors put the same arrangement in their own documentation, which makes it structural rather than a DistroKid quirk. Symphonic (22 September 2026): "Acceptance by Symphonic does not guarantee acceptance by every DSP or partner." LANDR (30 September 2026): "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 only some.

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

Note what is not on that list: using a generator. AI-assisted music is accepted in writing, and has been since May 2025. The rules prohibit behaviours — and the clearest published description of the behaviour that gets accounts flagged comes from a different distributor. UnitedMasters' spam guidance (15 September 2026) names three patterns — "rapid-fire uploads: distributing a high volume of releases within a short timeframe", duplicate content under slightly different titles, and "ultra-short tracks" — and puts the consequences with the platform: suppressed recommendations, or "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 — "one song per week is a lot", "you must be dropping an absolute mountain of AI slop". The poster's own figures, given later in the thread, 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

Those are allegations in a live case, not findings. As a yardstick they still help: 380 releases a month is a different activity from three, so if your catalogue looks like the reader's rather than the filing's, volume does not explain your email. The cause is unknown — though one detail in the reader's description is worth a second look, because distributors publish rules about it: two distinct artist projects on one account. Downtown, as a published example, requires that "the artist's true identity must be verifiable through official documentation or a clear and consistent digital footprint."

Can you appeal, and what to actually send

The honest answer first: there is no appeals process for this, and DistroKid has told you it cannot reverse it. What follows is worth doing for what it protects, not because it will restore your account.

What to send Realistically achieves Why bother
Reply asking which store and which release Probably nothing; the notice pre-empts it One email, and a specific answer changes everything
Ask whether the restriction is store-specific or all destinations Occasionally answerable The one answer that 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: at minimum the ISRC, UPC, exact release title, exact artist name and release date per track.

Moving distributor without losing your streams

Streams attach to the recording and the release, not to the company that delivered them, 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. If the recording or release becomes available again in the future after 90 days, it will not retain or reflect its previous stream count." The window is 90 days, and it only opens 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". To keep play counts and playlists, "make sure to use the exact same metadata (song titles, album title, ISRCs, etc.) and audio files you used with your old distributor." Its own caveat: "We can't guarantee that these play counts and playlist placements are maintained because the process is out of our hands."

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 new delivery is treated as new Your DistroKid HyperFollow links
The artist profile and its followers iTunes and Amazon reviews, which DistroKid says "you may lose" Whatever caused a store-level restriction — see below
Earnings already accrued — DistroKid pays out on deleted releases too Track-linking, which is the store's call, not yours

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; the history stays on the version you deleted. 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 — and three of these policies changed in the last nine days. Every row was 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

Two things follow. The distributors that test the model rather than your paperwork are the ones a Suno or Udio catalogue struggles with: TuneCore names exactly one eligible partner and it is not a consumer generator. And 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, so the "10 AI releases per week" figure appears nowhere on its own page. More in how distributors screen for AI and DistroKid's AI music policy.

Reducing the chance it happens again

None of this is a guarantee, because the decision sits with the stores. It is what you control.

That last point is where a cleanup step earns its place, and its scope is worth stating exactly. Processing a generated track so it clears automated screening fixes the upload gate. It does nothing about an account-level restriction a store has imposed, nothing about a rights claim, and nothing about whether a platform labels a release as AI, which comes from disclosure metadata you supply. 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.

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 through this route.

Which reframes the problem. For most people making music with these tools, distribution was never the wall — an audience was. Three threads in the last month, hundreds of comments between them, say the same thing: getting onto Spotify is solved and nobody can find listeners. We wrote about that in 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 — which pays a fee per placement and does not depend 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 also runs a direct storefront where you sell to listeners and keep 100%. The order matters: the storefront earns its place 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 30 September 2026. Policies were read at each vendor's own help centre that day; the rejection email is one artist's public post, 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 tells you DistroKid cannot lift it, not that no route exists anywhere. Since the notice attributes the decision to stores, any reversal would come from whichever service objected, and none publishes an appeals process for a distributor-relayed restriction. Treat it as durable and plan around it.

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

The ISRC identifies the recording, so it stays with the track rather than the distributor, and DistroKid's help centre explains how to bring existing ISRCs in for a new upload. Copy every one out of your release pages before you cancel anything: they are what let a new delivery be recognised as the same recording.

Not if you sequence it properly. Spotify's documentation says an unavailable recording or release retains its all-time stream count for 90 days, and only stops reflecting it if the release returns after that window. Deliver through the new distributor first, confirm it is live and matched, and only then take the old delivery down. Monthly listeners is a rolling 28-day figure, so it tracks your actual plays either way.

Do not treat that as the plan. The notice says the restriction came from stores, so a fresh DistroKid account does not address whatever they flagged — and Downtown's published rules, as one example, reserve "closure of specific user accounts, or even termination of your entire deal and all associated accounts" for trust-and-safety violations. A new account under a new name also collides with the authenticity rules most distributors publish.

It can, by a separate route. Several distributors exclude AI-generated music from fingerprinting regardless of account standing: LANDR lists YouTube Content ID, Meta, TikTok, Deezer, Lissen, Pandora and Tencent, Amuse lists Qobuz, Meta and YouTube Content ID, and RouteNote excludes its Content Recognition options, Amazon and the Korean stores. A track can be distributed and still be ineligible for Content ID.

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-generated music under four published rules, and every distributor publishing anti-spam guidance describes release patterns rather than the tool used — UnitedMasters names "rapid-fire uploads", duplicate content and ultra-short tracks. AI makes those patterns easier to produce, which is not the same as being the trigger.

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.