Technology

Spotify Gives Every Artist a Tool to Control What Appears Under Their Name

Martin HollowayPublished 6m ago4 min readBased on 1 source
Reading level
Spotify Gives Every Artist a Tool to Control What Appears Under Their Name
Photo by Castorly Stock on Pexels

Spotify has rolled out Artist Profile Protection to all artists, giving them control over which music appears under their name. The full launch follows eight months of beta testing with select artists, according to TechCrunch, which reported the rollout on 17 November 2026.

Spotify says the tool is designed to address music landing on the wrong artist profile. It identifies three causes: deliberate impersonation, metadata errors, and shared artist names. Each produces the same symptom, a release attributed to someone who did not make it, but each starts at a different point in the ingestion pipeline, the route a file takes from distributor to streaming catalogue. The profile-level control addresses the attribution outcome. It does not change how a misattributed file reaches the service in the first place.

Mechanically, artists turn the protection on through Spotify for Artists, which sends alerts when new music is submitted under their name. If a release is not theirs, they can remove their association with it, which stops it appearing on their profile. By default, releases go live as scheduled unless the artist intervenes. That makes the baseline a notify-and-remove model, with the artist acting after publication.

An advanced setting reverses that sequence. Artists must manually approve or reject each release before it appears on their profile, so the default becomes a hold-until-approved gate rather than publish-then-remove. Spotify says it worked with thousands of artists during the beta phase to refine the feature.

Billboard reported that Sony Music had requested the removal of more than 260,000 deepfake songs from digital platforms, nearly double the number disclosed in March. That figure gives a sense of the scale the tool is meant to address from the artist side.

In my view, the design puts the operational burden on the artist. Alerts only help if someone reads them, and removal or approval depends on the artist noticing a release in time. A major label with dedicated staff can manage that. An independent artist with a shared name or limited time is only as protected as their alert habits. The broader context here is that attribution errors cost more than one track. They distort royalty accounting, recommendation signals and listeners' sense of who made what.

The manual approval setting is the more interesting piece for engineers. It trades latency for control. Scheduled releases that would normally publish automatically now wait for a human decision, which creates a queue that distributors and labels must plan around ahead of release dates. Whether that trade suits a catalogue depends on how exposed the artist's output is to impersonation or naming collisions.

Still, the tool gives artists a documented, first-party mechanism that did not exist in a general form before, and it works inside the platform rather than through takedown requests filed after the fact. The open questions are how quickly alerts reach the right person and how often the removal path gets used. Those numbers will show whether notify-and-remove holds up as synthetic uploads grow.