Spotify turned on AI Credits in beta on April 16, 2026. The feature shows listeners, inside a track’s Song Credits on mobile, exactly which parts of a record involved artificial intelligence.
It is not a warning label. Spotify has said it does not down-rank or remove music for being AI-assisted, per Billboard’s launch coverage.
The catch is upstream. You cannot type a disclosure into Spotify. The signal has to arrive as metadata, delivered by whoever ships your release.
What DDEX actually standardized
DDEX means Digital Data Exchange, the standards body that defines how labels, distributors, and streaming services pass files and metadata to each other.
In September 2025, DDEX published an extension that adds structured fields for AI involvement. Spotify built its Credits feature on top of it, as the company laid out in its AI protections announcement.
DDEX rejected a single AI-or-not checkbox. Instead the standard lets a rights holder declare AI use per creative element:
- AI-generated vocals
- AI instrumentation
- AI composition
- AI post-production
- AI-written lyrics
That granularity matters. A producer who ran an AI stem separator is not making the same disclosure as an account uploading fully synthetic tracks.
The part nobody upstream is saying loudly
Here is the sentence buried in the rollout: the absence of a credit does not mean AI was not used.
Disclosure only appears if your distributor supports the DDEX AI fields and passes them through. On launch day, one distributor could. DistroKid was the first and only delivery partner, with TuneCore and CD Baby described as preparing to follow, according to reporting compiled around the April launch.
So for most of the catalog on Spotify, the disclosure field is not a clean “no AI.” It is blank. The pipe was never connected.
Why this is a distribution-layer story
The streaming service built the display. DDEX built the vocabulary. But the delivery layer decides whether your honest disclosure ever reaches a listener.
That puts three quiet obligations on your distributor:
- It has to implement the DDEX AI fields, not just the legacy delivery spec.
- It has to expose those fields in the upload flow so you can actually fill them.
- It has to map them cleanly to each service that accepts them, without dropping the data in transit.
Miss any one, and your disclosure dies at the border. You look non-compliant on a track where you did nothing wrong.
The enforcement context makes this urgent
Spotify is not adding disclosure in a vacuum. In the twelve months before its September 2025 announcement, it removed more than 75 million tracks it judged spammy.
It also shipped a music spam filter and an impersonation policy aimed at AI voice clones, and it is testing upload-blocking with distributors to stop fraudulent drops onto other artists’ profiles.
Read together, the message is that clean, complete metadata is becoming the price of admission. Tens of thousands of AI credits are already submitted daily. Sam Duboff, who leads Spotify policy on this, framed it plainly to Billboard: “the starting point has to be shared language through the existing supply chain of music.” The supply chain is your distributor.
What an indie artist or label should do now
- Ask your distributor, in writing, whether it delivers the DDEX AI disclosure fields to Spotify and which other services.
- If you used AI anywhere, disclose per element rather than guessing at a blanket answer.
- Keep your own record of what was AI-assisted, so you can correct a release later.
A DDEX-native distributor that already maps the full delivery spec, including the AI extension, is the difference between disclosure that travels and disclosure that evaporates. That is the pipe InterSpace Distribution and ToneGrid were built to run.
