Requesting Takedowns
Remove your release from DSPs — understand takedown types, timelines, and what happens to your royalties and ISRCs
Remove a release from one DSP or from every DSP
Request a takedown when you need to remove a release from Spotify, Apple Music, Amazon Music, Deezer, TIDAL, YouTube Music, YouTube Content ID, or other DSPs that DIMBER delivers to. Before you submit the request, make sure you understand what changes immediately, what royalties still pay out, and how the release can be delivered again later using the same recording identifiers.
Types of takedowns
Choose the takedown type that matches why the release is coming down. The reason matters because it affects how DIMBER reviews the request and whether the removal starts with you, with a rights claim, or with a DSP.
- Voluntary takedown — You choose to remove the release. Common reasons include re-recording, a rights dispute you want to resolve before re-delivery, strategic removal, or preparing a re-delivery with updated content.
- Rights-based takedown — A third party claims ownership or other rights in the release, and the release must be removed. DIMBER may initiate this takedown after verifying a valid claim.
- DSP-initiated takedown — A DSP removes the release on its own because of a policy violation, legal complaint, or platform-specific enforcement action. DIMBER notifies you when this happens.
A takedown removes the release from DSP storefronts and streaming services. It does not delete the release record from your DIMBER dashboard.
How to request a takedown
Use the release page in your DIMBER dashboard to submit the request. Once you confirm it, the release status changes so you can track that the removal is in progress.
Open the Release
Open the release in your DIMBER dashboard. Make sure you selected the correct release version before you continue.
Select DSPs
Click Request Takedown and choose the DSPs you want to remove the release from. Select all DSPs if you want a full takedown across the entire distribution network.
Provide a Reason
Enter the reason for the takedown. Clear context helps DIMBER route the request correctly, especially for rights issues, metadata corrections, or planned re-delivery.
Confirm
Confirm the request to submit it. After submission, the release status changes to Takedown Requested.
Takedown timelines by DSP
Processing times vary by platform because each DSP removes content on its own schedule. Most takedowns start processing as soon as DIMBER submits them, but the release may remain visible until the DSP completes removal.
- Spotify — Typically 2–5 business days
- Apple Music — Typically 1–3 business days
- Amazon Music — Typically 2–5 business days
- Deezer — Typically 3–7 business days
- TIDAL — Typically 3–7 business days
- YouTube Music / YouTube Content ID — Typically 2–5 business days
- Other DSPs — Varies; most process within 7–14 business days
Takedowns are not processed on weekends. Requests submitted Friday through Sunday begin processing Monday.
What happens to royalties
Royalties earned up to the takedown date still belong to the rights holder. DIMBER pays royalties monthly, so streams and downloads that happened before the takedown are reported and paid in the next applicable royalty cycle.
After the takedown completes, no new royalties accrue on the affected DSPs for that release. If you removed the release from only some DSPs, royalties can still continue from any DSPs where the release remains live until those platforms are also taken down.
What happens to ISRCs
ISRCs stay registered to the original recording. A takedown does not delete them, remove them from history, or make them invalid.
If you re-deliver the same recording, you can reuse the same ISRCs. Do not reuse a UPC for a different release because the UPC identifies the release package, not the recording itself.
Takedown vs. deletion
A takedown removes the release from DSPs, but the release record stays in DIMBER. That record remains available for royalty accounting, reporting, and audit purposes.
Deletion is not a standard action. If you need to send the release out again, submit a new release and reuse the same ISRCs for the same recordings.