Release Takedowns and Corrections

When a release is already live, start by identifying what is wrong and who controls the fix. A spelling error, incorrect artwork, wrong release date, track-order problem, missing credit, unauthorized upload, and complete removal are different problems. They may require different routes.

For ordinary metadata mistakes, contact the label or distributor that delivered the release. Spotify says it displays the metadata supplied to it and does not manually edit catalog entries; its documented correction route is through the label or distributor (Fixing problems with music metadata). Apple Music for Artists likewise directs artists to work with their label or distributor to submit corrections (Music metadata).

If music was uploaded without your permission, use the platform’s infringement-claim process rather than treating the situation as a routine typo. Spotify provides a route for reporting music uploaded without the rightsholder’s permission (Reporting music uploaded without your permission). If the correction requires a structural change that your distributor cannot make after delivery, you may need a takedown and a new delivery. That is a consequential choice, and the exact effects depend on the distributor and services involved.

This article explains the decision, the information to gather, the practical sequence, and the limits of what can be predicted. It is educational information, not individualized legal, financial, contract, royalty, or copyright advice. Platform and distributor policies can vary by territory, account, product, and date. The workflow evidence here was verified as of August 7, 2026.

First, classify the problem

A useful first question is whether the audio itself is correct and authorized.

If the audio is correct and the problem is descriptive or delivery metadata, begin with a correction request. Common examples include an artist name, title, artwork, release date, track order, availability setting, explicit-content tag, role, or credit. Spotify identifies these as fields that must be corrected through the label or distributor (Fixing problems with music metadata). Apple describes both descriptive and rights-related metadata and points artists to their label or distributor for corrections (Music metadata).

If the release contains music uploaded without your permission, classify it as an unauthorized-content or rights issue. A metadata correction does not establish who owns or controls the recording, and it does not replace a rights-clearance analysis. On Spotify, the relevant path is an infringement claim (Reporting music uploaded without your permission).

If the release must disappear, ask the distributor to submit a takedown or cancellation. This may be appropriate when the wrong recording was delivered, the release should not remain available, or a required change cannot be made in place. A takedown is not simply a larger metadata edit: it can affect availability, delivery history, and the possibility of continuity when a replacement is issued.

The decision map

Use this route as a starting framework:

1. The audio and rights are correct, but information is wrong: request a distributor or label metadata correction.
2. The music is unauthorized or uploaded without permission: use the affected platform’s infringement-reporting path and address rights separately.
3. A structural field cannot be changed through the distributor’s ordinary edit process: ask whether the distributor requires takedown and re-release.
4. The release should no longer be available: request a takedown or cancellation, then monitor the partner services.
5. A replacement is needed: ask the distributor and each relevant platform what continuity, identifiers, timing, and catalog consequences apply. Do not assume that one service’s behavior will apply everywhere.

This map does not create a universal industry rule. Distributor policies differ. For example, TuneCore says that after distribution its ordinary correction process cannot change adding, deleting, or reordering tracks, the UPC or ISRC, or original release-date information (How do I make changes to my release?). That is TuneCore’s documented service policy, not proof that every distributor has identical limitations.

What a metadata correction usually involves

A correction request should be precise. Identify the release, the exact field, the current value, and the replacement value. Include the artist or project name, release title, track title where relevant, UPC or other delivery identifier if available, and links to the affected store pages. Explain whether the correction applies to one track, the entire release, or multiple releases.

Keep evidence of the intended information. Depending on the field, that may include the final approved artwork, the correct spelling used in your release agreement or credits, the intended release date, or the role information supplied during delivery. The evidence packet does not establish a universal document checklist, so ask your distributor what it needs before submitting.

Do not ask Spotify or Apple to manually rewrite the listing when their documented workflows direct you to the label or distributor. Spotify’s model is to display the metadata delivered to it, while Apple tells artists to submit corrections through their label or distributor (Fixing problems with music metadata and Music metadata). Your distributor must send the corrected data through its delivery channel, after which the store must process it.

A correction can take time to appear. DistroKid says most edits are processed by services within a few days, may take one to two weeks to show everywhere, and may take several months for artist-name rebrands (Editing a Release After It's Uploaded). Those are DistroKid’s operational estimates, not a guaranteed service-level agreement and not a timetable for every distributor or store.

When a re-upload may be necessary

Some changes are not ordinary edits. A distributor may restrict changes to the track list, identifiers, or original release information after delivery. In that situation, the distributor may tell you to remove the original release and deliver a new version. Spotify also says re-uploading may be necessary for metadata problems when music was delivered through a distributor (Re-uploading music). Spotify’s guidance does not require a takedown for every metadata issue, so confirm the required path before removing anything.

TuneCore recommends takedown and distribution of a new version when a change must be guaranteed across stores. TuneCore documents that the new product receives a new UPC and says exact same tracks may reuse prior ISRCs; it also says reviews, comments, and store playlists tied to the original UPC are removed (How do I make changes to my release?). These are TuneCore-specific consequences. Do not present a new UPC, ISRC reuse, playlist removal, review loss, stream reset, follower reset, or algorithmic penalty as a universal result of every takedown and re-release.

Before approving this route, ask the distributor, in writing if possible, which fields require a new delivery; whether the old release must be taken down first; which identifiers can be reused; how the replacement will be delivered; and what happens to the original store page. Ask separately about each priority service. A successful outcome on Spotify does not establish the same outcome on Apple Music or another partner.

Takedown timing and permanence

A takedown moves through more than one system: your request, the distributor’s processing, delivery to partner services, and each partner’s removal process. Timing is therefore service-specific.

Spotify says it needs at least two business days to process a takedown after receiving it (Music still live after a takedown?). Spotify also notes that a direct-link version may remain visible but unplayable during the process, and says to escalate to the distributor if the music is still live afterward (Music still live after a takedown?).

CD Baby documents a different workflow: it says an all-platform cancellation is final and that content will be removed from partner sites within 30 days (How do I take down or cancel a release?). The finality and timing are CD Baby’s service policy, while partner behavior can vary. Do not generalize that 30-day window to every distributor.

The practical lesson is to treat cancellation as a serious, potentially irreversible action. Save the release details, store links, identifiers, credits, and delivery records before submitting it. Confirm whether you are requesting one-store removal or an all-platform cancellation. After submission, record the date, ticket number, and services affected. Check the original links and search results during the stated processing window, and escalate through the distributor when a service remains playable beyond the applicable guidance.

Preserving continuity on a replacement

A replacement release may or may not connect to the original catalog history. Spotify documents track-linking for re-uploaded music when the old and new audio and metadata are the same. Its guidance specifically includes matching duration, title, and artist name, and says matching play counts indicate that the tracks were linked (Re-uploading music).

That is a conditional Spotify feature, not a promise of universal continuity. Do not promise preservation of streams, followers, playlists, release totals, or URLs across platforms. A distributor’s identifier policy may also differ from a platform’s matching behavior. If the audio or relevant metadata changes, the conditions described by Spotify may no longer be met.

For a replacement, compare the old and new delivery carefully. Confirm the audio file, duration, title, artist name, roles, and other required metadata before submission. If the objective is continuity, ask the distributor and the platform what matching conditions apply. Keep copies of the old and new delivery confirmations so you can document what changed if the replacement is not connected as expected.

Rights, samples, and unauthorized uploads

A rights problem is not merely a metadata problem. U.S. Copyright Office guidance distinguishes the sound recording from the underlying musical work and explains that derivative sound recordings can incorporate preexisting sounds (Copyright Registration for Sound Recordings (Circular 56)). Title 17 is the current U.S. copyright-law compilation and includes provisions addressing copyright subject matter, ownership, infringement remedies, and sound recordings (Copyright Law of the United States (Title 17)).

This distinction matters when a release includes a sample, an interpolation, another person’s composition, or an audio recording supplied by someone else. Clearance questions may involve separate rights in the recording and in the underlying music or lyrics. The evidence here supports that general U.S. context, but it does not decide whether any particular use is authorized, infringing, licensed, or permitted in a specific territory.

If someone uploaded your music without permission to Spotify, use Spotify’s infringement-claim route (Reporting music uploaded without your permission). Gather the facts requested by the platform and preserve proof of your rights or authorization. Because platform reporting is not a substitute for legal advice or complete rights clearance, obtain qualified advice when the dispute is contested, commercially significant, or cross-border.

A worked example

Suppose an album is live with the correct recordings, but one track has the wrong title and the artwork contains a spelling error. The first route is a distributor correction. Send the exact replacement title and artwork, identify the release, and ask the distributor to submit the update to Spotify and Apple. Do not request a takedown simply because Spotify will not manually edit the listing.

Now suppose the album also has the wrong track order, and the distributor says that order cannot be changed after distribution. Ask whether its documented solution is takedown and re-release. If the distributor is TuneCore, its published policy treats adding, deleting, or reordering tracks as unavailable through the ordinary correction process and describes the new-UPC and playlist/review consequences of a new version (How do I make changes to my release?). Treat those effects as TuneCore-specific and confirm current instructions before acting.

Finally, suppose a third party uploaded one of the recordings without permission. That is a separate unauthorized-content route. Report it through the platform’s infringement process and address the rights question independently. A distributor metadata ticket alone is not the correct explanation for an unauthorized upload.

Final checklist

Before submitting a correction, verify the exact field, replacement value, affected stores, release identifiers, and supporting records. Ask whether the field is editable in place and how long propagation may take.

Before requesting a takedown, confirm its scope, whether it is final, whether the release can be restored, whether a replacement is required, and what identifiers or catalog connections may be affected. Save all delivery information first.

Before re-releasing, compare the audio and metadata against the continuity conditions documented by the relevant platform. Ask what can be preserved and what cannot be promised. Treat any distributor-specific UPC, ISRC, playlist, review, or timing statement as that distributor’s policy, not as a universal rule.

After submission, monitor the affected store pages, document dates and ticket numbers, and escalate through the distributor when the service-specific processing window has passed. Keep expectations platform-specific and current.

Open Music Business provides educational information only. This article does not provide individualized legal, financial, tax, contract, royalty, or copyright advice.