How long a takedown really takes, and what it does to your streams

54 · 2026-09-22 · 19 min read · Español

A takedown is a delivery your distributor sends to a store saying a release no longer has a deal; the store stops making the release available and deletes nothing. Spotify says it needs at least two business days once it has the message, Apple publishes no time at all, and distributors publish ranges from two days to four weeks because the message waits at the distributor before any store sees it. On the store the row stays, grey and unplayable; the all-time count is kept for ninety days; and whether the release can ever come back is your distributor’s rule, not the store’s.

• A takedown is a message from your distributor to a store, not a deletion: in DDEX terms a NewReleaseMessage with no deal in it, or a PurgeReleaseMessage; in Apple’s format a metadata update with the tracks left out and cleared_for_sale set to false, territory by territory.
• Spotify processes a takedown within two business days of receiving it and publishes that number; Apple publishes none. DistroKid, TuneCore and CD Baby publish ranges from two days to four weeks depending on the store, and up to thirty days for everything.
• The clock starts when the store receives the message. Spotify’s instruction to a distributor whose takedown has not landed is to check the XML and send it again.
• On Spotify the track stays reachable by direct link, grey and unplayable, and the profile cannot be deleted, only emptied. The all-time stream count is kept for ninety days after the recording goes unavailable and is not restored after that.
• At the store, availability is a delivery and can be reinstated by another one; TuneCore and CD Baby treat their takedown as final and require a new release with a new UPC. Read your distributor’s rule before you click.

What is a takedown, actually?

A takedown is your distributor’s message telling a store a release no longer has a deal; the store stops offering it and deletes nothing.

The standard the message travels in says it in one line. DDEX’s guidance on takedowns gives two ways to send one: “Sending a NewReleaseMessage without a Deal; or Sending a PurgeReleaseMessage.” The first is the ordinary one, and the rule under it is blunt to the point of a slogan — “No Deal = No deal”: if a message “does not provide a Deal for a specific Release for a specific territory for a specific use, then it means implicitly that that Release is not (or no longer) available to consumers in that territory for that use.” The active deals for a release are always whatever the latest message said. A takedown is the latest message saying nothing.

Apple’s own format is the same shape with Apple’s field names on it. The Apple Music Specification has a section headed Takedowns, and it describes one as a metadata update “except that all of the track-level metadata is omitted, and <cleared_for_sale> is set to ‘false’ for any territories in which the album is to be taken down.” Territory by territory, in its own example: “if both ‘WW’ and ‘CA’ are specified on an album and ‘WW’ is taken down, the album will be removed from sale in WW; however, it will remain live in Canada.”

Before it acts, the store checks that the sender is allowed to say it. The ERN standard puts it this way: the store “shall act by ceasing to make that release available if it can ascertain that the record company or distributor has the rights to ask for a release to be purged,” which “may be done by checking that the DSP has received the active deal(s) from the same record company or distributor.” That is why the button lives at your distributor and not at Spotify. The store trusts the party that delivered the release, and that party is not you. Afterwards, what a distributor can see in Spotify’s delivery log is three words — whether “a takedown, Delete, or End Date was delivered” — and what no message of any kind can carry is the two codes no delivery can change.

Nothing is deleted. The row, the codes, the count and the links all sit exactly where they were, and the store simply stops offering the thing. The most dramatic thing that will happen to your catalogue this year is an omission.

How long does a takedown take?

Spotify says within two business days of receiving it; Apple publishes no time; DistroKid, TuneCore and CD Baby publish two days to four weeks.

Only one store puts a number on its own page. Spotify’s help article for a takedown that has not landed — Music still live after a takedown? — opens with “We need at least 2 business days to process takedowns,” and its distributor half repeats the figure from the other side: “When we get your takedown, the music should be removed within 2 business days.” Apple’s specification describes the format and gives no time, and the Apple Music for Artists FAQ does not contain the word. That silence is the whole of what Apple publishes on the subject.

The distributors publish more, and their numbers are longer, because they are counting from a different place. DistroKid’s page lists an estimate per store, and it is the only per-store list any of the three publishes:

DistroKid frames the list with a rule of thumb — “It takes the same amount of time for releases to be removed from streaming services as it does for releases to go live” — and a total: “up to 1-2 weeks on average for the release to disappear from all services, sometimes sooner.” Its deletion page repeats the one figure that is the store’s and not an estimate: “Spotify deletions take at least 2 business days.” TuneCore gives one range for everything: “most stores will process takedown requests within 2-3 business days, but some may take up to three weeks.” CD Baby gives one ceiling: “Your content will be removed from partner sites within 30 days.”

Read the table from the bottom. A takedown is finished when the last store has finished, and on every list any distributor publishes the last stores are the social platforms and Content ID, not the one you keep refreshing. You will watch Spotify, because Spotify is where the count is and where the two-day promise is. The takedown is done when Instagram says so.

Why is it still live after the window?

Because the store’s clock starts when the message arrives, and Spotify’s advice to a distributor whose takedown has not landed is to send it again.

Spotify’s page is written in two halves for two readers. The artist’s half ends: “If your music’s still live after 2 business days, contact your distributor for help.” The distributor’s half says what to do when the artist calls: “Check the Availability tab. If you see Available, check the XML and send the takedown again.” Read that once more. The store’s published remedy for a takedown that did not happen is the takedown. Not a ticket, not an escalation — the same message, sent so that this time it arrives.

Put the two numbers side by side and they stop contradicting each other. Two business days is the store’s promise, and it starts when the store has the message. Two to five days is the distributor’s estimate for the same store, and it starts when you click. The gap between them is the queue at your distributor — the message waiting to be generated, batched and sent — and it is the one part of a takedown for which nobody, store or distributor, publishes a number.

One check before you open a ticket about it. “Each version of a track has a unique Spotify URI,” the same page says, and it tells you how to copy one: the desktop app, right-click, Share, hold the Alt or Option key, Copy Spotify URI. A track can be down and its double still up — another delivery, another distributor, a version that was never part of this takedown — and if you report the wrong one, everybody spends a week confirming that the takedown you sent worked.

Why was it taken down when you did not ask?

Because your distributor sent one: a lapsed DistroKid subscription or an unpaid TuneCore renewal removes the release, and the store never sees why.

Spotify has a page for exactly this morning, and it hands you straight back: “If you didn’t request your music be taken down, reach out to your label or distributor for help as they’ll have more info.” The line under it is the store’s whole position: “If we receive a takedown request, we’ll remove the music.” The message does not carry a reason and the store does not ask for one. From the store’s side, a takedown you requested and one you never heard about are the same three words in the same delivery log.

The reasons are on the distributors’ own pages. DistroKid: “If you don’t renew your subscription to DistroKid, your music will be removed from services,” and the option that prevents it, Leave a Legacy, is bought per release — “it is not a one-time payment for all of your releases.” TuneCore: a release stays live past its first year only while the annual renewal is paid; the company emails before the date and twice after, allows a grace period, and then “your release will be taken down from stores” — after which it “is considered final and cannot be reversed.”

The same message, the same two business days, the same grey rows, sent because a calendar ran out rather than because anybody decided anything about the music. The audit checklist asks you to know your distribution agreement’s term and its takedown process, and that box is this section, a year early, as a checkbox.

What does a listener see after a takedown?

On Spotify the track stays reachable by link, grey and unplayable unless another version is live there, and the profile empties rather than disappears.

Spotify’s own description of the afterwards: “When you remove music from Spotify, you might still be able to see it with a direct link. The tracks will be gray and unplayable unless there’s another version of the track live in your country.” A saved track is that row. A playlist add is that row. Every listener who kept the song has a grey line in their library with your name on it, and no store publishes a separate rule for libraries because none is needed — the row was never theirs to keep, only to point at.

The links go the same way. DistroKid, on a release deleted and re-uploaded: “the new version of your release will have different links than the original. Services generate new links for each separate release.” The link in your bio, the pre-save page, the QR code on the poster still on the venue wall: every one of them points at the grey version.

And the profile stays. Spotify’s page on removing your music: “We can’t delete artist profiles entirely, but if you remove all your music your profile no longer shows in Spotify search results.” Then the note: “You may still be able to find your profile with an existing link, but it’ll appear empty. We also can’t affect search results from other services or websites.” You do not get deleted from Spotify. You get vacated.

What no store publishes is what a takedown does to an editorial or algorithmic placement. The ISRC piece already tells you the placement is gone, and this page has nothing to add to that except that nobody publishes a rule for it. The closest any document comes is DistroKid’s page on moving a catalogue between distributors, which says that with identical metadata and audio the services “(especially Spotify) try to maintain play counts or playlists that your music is on,” and then: “We can’t guarantee that these play counts and playlist placements are maintained because the process is out of our hands.” That is the most honest sentence in this whole subject, and it is a distributor admitting it cannot see inside the store either.

Do you lose your stream count?

Spotify keeps the all-time count for ninety days after a recording goes unavailable; after that a returning recording does not get it back.

The rule is one sentence on Spotify’s page on how streams are counted, under All-time streams: “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 same ninety days govern a release’s count and a music video’s. Day ninety-one is the library at Alexandria.

The way back inside the window is on the store’s page too, and it is not a request. Spotify’s page on re-uploading music: “You can re-upload music without losing your play count through a process called track-linking. Make sure the audio and metadata of the old and new versions is the same (including duration, title, and artist name).” The check is on the desktop app, on your artist profile, at the count beside the song: “If the play counts match, the tracks have linked.” Spotify describes linking as a property of the delivery — the same audio, the same fields — and not as something anybody files for.

Apple publishes nothing read for this piece about a count after a takedown, and the one distributor that speaks of counts at all says “can’t guarantee.” One more thing about the ninety days: they start at unavailability, not at your replacement. A fix that spends the distributor’s four weeks has burned a third of the window before the store sees the new delivery, which is the arithmetic behind the ISRC piece’s rule that the corrected version goes live before the old one comes down.

Can a takedown be undone?

At the store, yes: Spotify reinstates a release on an update restoring its rights; at TuneCore and CD Baby the takedown is final.

The store’s mechanism runs both ways, in Spotify’s own words to distributors: “If you sent a takedown, send an update reinstating track-level rights to make the release available. Once we get them, your music should be live within 2 business days.” Availability is a deal in the latest message. Send a message with the deal back in it and the store puts the release back, on the same clock it took it down. Some distributor tooling matches the store: at DistroKid, a release removed from one service can be added back from the album page, and a service-specific removal takes the same “1-2 weeks” the rest of them do.

Other tooling does not. TuneCore: “We can’t reverse takedowns, as stores consider this action permanent.” The route back is a new release, and “the new release would need a new UPC” — though “you can reuse previous ISRCs as long as the audio file and track details are the exact same.” The same company’s page on what cannot be changed adds the cost: “Stores will treat the resubmission as a new product, and your release will go through their review process again.” CD Baby says “cancellations are final” on its takedown page, and its page on re-releasing sets the condition for the same audio coming back: identical artist name, title, ISRC and version, and “this applies even if the original release has been cancelled,” because “partners like Apple Music identify audio by its content, not just its metadata.”

Read the three side by side and the word “permanent” resolves. It is a fact about your distributor’s tooling — what its dashboard will and will not send — and at the store the mechanism is a delivery either way. The same tooling is why “take it down and put it back up fixed” is the advice DistroKid warns against in as many words: “Stores don’t let you upload a release, delete it, and re-upload it with different metadata (like a new artist name or title).” Different metadata is a new product, with a new UPC, on a new page, at zero. The same metadata is the only thing that ties it to the old one: the same ISRCs, or a fresh one by accident and a duplicate for life; the same version field; and the original release date, which a re-release keeps.

What to do before you click

Write down the codes, the links and the count, read your distributor’s reversal rule, and if it is a repair put the fix live first.

• The count. Spotify keeps the all-time count for ninety days after the recording goes unavailable, and nothing else keeps it at all. Screenshot the fucker.
• The links. Copy the URI of every version, by the method above, and every store link you have posted anywhere. The new release gets new ones, and every old one will point at a grey row.
• The codes. The UPC, every ISRC, every version field, the original release date. A re-release that links to the old one carries the same ISRCs and the same track details; one that fixes anything is a new product with a new UPC. The two codes no delivery can change are the field-by-field piece’s, and they are the two to have written down before anything moves.
• The reversal rule. Your distributor’s page, not the store’s. At TuneCore and CD Baby the button is final; at DistroKid a per-service removal can be undone from the dashboard. Know which one you are holding before you press it.
• The order, if it is a repair. Corrected version live first, then the takedown. The ISRC piece owns the sequence and the waiting time, and nothing on this page changes a word of it.
• The date it is done. Not Spotify’s. The slowest store on your distributor’s list is the day the takedown is finished, and that is the day to open every link you kept and look at what colour it is.

FAQ

Do you still get paid for the streams before the takedown?

At DistroKid, yes: its page states that any earnings due for a deleted release, for the time it was live on streaming services, are still passed through to the account. The TuneCore and CD Baby pages read for this piece do not address the question, so ask yours before you click rather than after.

Can you take down one track from an album?

Not at TuneCore, whose page states that individual tracks cannot be taken down and the whole album comes down instead. Apple’s takedown format works on the album, territory by territory, with the track list left out. Whether your distributor exposes anything finer than the release is its own page’s question, not the store’s.

Can you take a release down in one country only?

Yes in the store formats: Apple’s takedown is set territory by territory, and a DDEX deal is stated per territory, so a message can withdraw one and leave the rest. DistroKid routes a removal from certain countries through its support team; CD Baby’s self-service option is per partner, not per country.

Does a takedown free up the UPC or the ISRC?

No. TuneCore and CD Baby both state that a re-release is a new product with a new UPC, and that the ISRCs may be reused only when the audio and the track details are exactly the same as before. A rebuilt product that changes anything takes a new UPC; a recording that changes nothing keeps its code.

Sources

• Spotify for Artists, Music still live after a takedown? — the two business days, stated to artists and again to distributors; the grey, unplayable row reachable by direct link; one URI per version and how to copy it; the instruction to check the Availability tab and send the takedown again.
• Spotify for Artists, Removing your music from Spotify — a takedown is requested through the label or distributor; the profile cannot be deleted, only emptied, and may still be reached by an existing link.
• Spotify for Artists, Music unexpectedly removed? — a takedown you did not request is the distributor’s to explain; the delivery log’s takedown, Delete and End Date; reinstatement by an update restoring track-level rights, live within two business days.
• Spotify for Artists, How your streams are counted — the all-time count kept for ninety days after a recording or release becomes unavailable, and not restored after.
• Spotify for Artists, Re-uploading music — track-linking: the same audio and metadata, including duration, title and artist name; matching play counts as the check.
• Apple, Apple Music Specification, 5.3.26, Takedowns — a metadata-only update with the track-level metadata omitted and cleared_for_sale set to false per territory; the WW and CA example. The specification gives no processing time.
• DDEX Knowledge Base, Takedowns — the two ways: a NewReleaseMessage without a Deal, or a PurgeReleaseMessage.
• DDEX Knowledge Base, No takedown in initial deal — the active deals are those in the latest message received; no deal for a release, territory and use means not available there; the one exception for a release that was live and is being pulled.
• DDEX, ERN Part 1, 6.19.6 Purging/removing a release — the store ceases to make the release available if it can ascertain the sender has the rights, by checking it received the active deals from the same party.
• DistroKid, How Long Does It Take for My Release to Be Removed from Streaming Services? — the per-store estimates in the table, the rule of thumb that removal takes as long as going live, and the one-to-two-week total.
• DistroKid, Deleting a Release from Streaming Services — the dashboard steps, and that Spotify deletions take at least two business days.
• DistroKid, Removing Your Release From a Specific Streaming Service — one to two weeks for a service-specific removal, and that a release can be added back to a service afterwards.
• DistroKid, I Deleted a Release … Will the Original Links in Services Still Work? — a re-uploaded release gets new links.
• DistroKid, Switching from a Different Distribution Company to DistroKid — identical metadata and audio so that services try to maintain play counts and playlists; that this cannot be guaranteed; that reviews may be lost.
• DistroKid, If I Don’t Renew My DistroKid Subscription, Will My Music Stay Live in Streaming Services? — an unrenewed subscription removes the music; Leave a Legacy is per release.
• DistroKid, Editing a Release After It’s Uploaded — that stores do not let a release be deleted and re-uploaded with different metadata.
• DistroKid, When I Delete a Release, Do I Still Get My Earnings? — earnings for the time a deleted release was live are still paid.
• TuneCore, How do I take down my music from stores? — two to three business days for most stores, up to three weeks for some; individual tracks cannot be taken down.
• TuneCore, Can I make my music live in stores again if it has been taken down? — takedowns are not reversed; a new release with a new UPC; ISRCs reusable when audio and track details are identical.
• TuneCore, Why has my music been removed from stores? — an unpaid renewal takes a release down after notices and a grace period, and the removal is final.
• TuneCore, What changes cannot be made after distribution? — a resubmission is a new product that goes through the stores’ review again.
• CD Baby, How do I take down or cancel a release? — removal from partner sites within thirty days; cancellations are final.
• CD Baby, How do I cancel my release on a specific platform? — per-partner cancellation, permanent, up to thirty days.
• CD Baby, Can I re-release music I’ve already distributed? — identical artist, title, ISRC and version for the same recording to return, even after a cancellation; partners identify audio by its content.

Every page cited here was read on the date at the top of this piece. The three distributors’ help centres refuse requests that do not come from a browser, so each article was read through the help centre’s own public article feed, which carries the same text with a last-updated date; the links above lead to the pages a reader can open. Only Spotify’s and Apple’s own pages were read for a store-side number, so every other store’s figure in the table is DistroKid’s estimate and is printed as such. Processing times, retention windows and finality rules are the companies’ at the date read; confirm them on the pages before you act on them.

Keeping the register

The fields a store compares when it decides whether a new delivery is the old recording — artist name, title, ISRC, version — are per-track fields a catalogue already holds if it was kept properly, beside the UPC the rebuilt product cannot reuse and the original release date it has to keep. CatalogTracker keeps a release’s UPC, its release date and its original release date, and each track’s ISRC and version, with a completeness meter that reports how many of a release’s fields are actually filled in. It sends nothing to any store and takes nothing down. It means that the day a takedown is done, the codes the replacement has to carry are a thing you look up rather than a thing you reconstruct from a grey row. In development for iPhone.