DistroBolt home

RELEASE OPERATIONS AND ARTIST TOOLS

How to remove music from stores: prepare a takedown request

Request removal through the distributor or label responsible for the delivery, after checking your authority and the exact releases involved. A takedown, an account cancellation and a catalogue transfer are different actions.

Decide what you are trying to achieve

  • Remove one incorrect or unauthorised delivery.
  • Withdraw an authorised recording from selected destinations.
  • End a distribution arrangement while coordinating a transfer.
  • Resolve a rights dispute that needs evidence and a separate review.

These situations do not have interchangeable instructions. If your aim is to move music, start with the catalogue transfer guide rather than asking for immediate removal.

Check authority and existing obligations

Confirm who controls the relevant recording and who can instruct its distributor. Review the applicable agreement and any commitments to artists, collaborators or licensees. Keep the master-rights record separate from account login access: access to a dashboard is not a legal ruling on the right to withdraw music. Seek appropriate advice if authority is contested.

Make the scope unmistakable

  • Identify release titles, artist names, delivery references and UPCs.
  • List affected tracks and ISRCs if the request concerns part of a release.
  • Specify the destinations or territories involved and explain the reason accurately.
  • State whether this is a transfer and whether a replacement delivery has been verified.
  • Include the requester’s relationship to the rightsholder and any existing case reference.
  • Ask the team to confirm the scope and applicable process before consequential changes are made.

What a platform removal means

Spotify tells artists to request a takedown from the delivering label or distributor. Its guidance also explains that removing music does not necessarily erase every existing artist-profile link. Do not equate “no longer in search” with removal of all copies, references or results elsewhere on the web. Other destinations can follow different processes.

An example of a scoped request

A label needs one mistakenly delivered edition withdrawn while the correct album remains available. It lists the two distinct UPCs, links both editions and names only the incorrect one for review. “Delete our album” would leave the team guessing. This example is about precision, not permission to remove someone else’s material or a promise of track-level takedown support in every case.

Preserve reports and confirm the result

Keep relevant delivery records and royalty statements before changing arrangements. Ask how reports and later payments for earlier use will remain accessible under your actual agreement. A removal request is not proof that every destination has completed it, nor proof that all outstanding royalties have been settled. Use the reporting guide for a specific financial discrepancy.

If the music was uploaded without permission

Preserve links, identifiers and evidence of your authority. Explain whether you are reporting infringement or requesting an ordinary authorised takedown; do not make a false claim to resolve an unrelated commercial disagreement. Use the relevant official reporting process or ask DistroBolt which evidence is needed. This guide does not determine ownership, prescribe a legal remedy or promise a removal deadline.

Common questions

Does cancelling an account automatically remove every release?

Do not assume that. Confirm cancellation, renewal, delivery and takedown consequences under the actual agreement before acting.

Should I remove old music before transferring it?

Normally coordinate and check the new delivery first. Review your agreement and the specific transition; uninterrupted availability cannot be guaranteed.

Related DistroBolt guides

Ask about your release

Bring the release reference and the specific question. We confirm the appropriate process and any separately scoped work before you commit.

Talk to the DistroBolt team · Email DistroBolt

Reviewed 3 November 2026. Platform tools and requirements can vary by release, rights, account and territory. No approval, release date, earnings, playlist placement or audience result is guaranteed.