Am I legally required to disclose that a track used AI?

There's no single rule that covers every case. Requirements come from the platform you're publishing to and, more and more, from regional transparency law — not from a universal music-industry standard. In practice, the disclosure that matters most is the answer you give your distributor at upload, since that field is what flows into store metadata.

Does disclosing AI involvement hurt a release?

It can affect how a track surfaces on services that classify AI uploads, but it rarely leads to removal. A false answer is the costlier path — metadata disputes and account-level penalties are far worse outcomes than a track that gets slightly less editorial push.

What actually counts as generative AI here?

Tools that produce new musical material or a synthetic voice. Pitch correction, stem separation, noise reduction, amp modelling and mastering assistants are processing, not generation — every platform treats them as ordinary production steps.

Is anything I type here saved anywhere?

No. The statement is built entirely in your browser as you type it. Nothing gets uploaded, logged or kept — same principle as the detector itself.

Can a detector verify that my disclosure is truthful?

No — and that's precisely why disclosure matters. Acoustic analysis gives you probabilistic evidence about a recording, never a record of how it was made. Accurate metadata and retained project files are the only lasting proof of that.

Free tool

Write your AI disclosure statement

Tell it what the AI did, who did what, and where it's going, and it hands back wording ready for a distributor field, a credits note, a YouTube description or a release page. Everything happens in your browser — nothing you type ever leaves the device.

Quick answer

How do you disclose AI-generated music?

Disclose right where the question comes up: the AI-involvement field in your distributor's upload flow, accurate credits for every human contributor, the altered-or-synthetic toggle on YouTube where it applies, and one plain sentence in the release description. State what the model produced and what a person did, and hold onto your project files.

How each platform asks →

1. What did the AI do?

No generative AIStandard production tools only — tuning, stem separation, mastering assistants, amp models.AI-assisted writing or productionA human performance and arrangement, with generative help on ideas, sounds or sections.AI or cloned vocals over human musicThe instrumental was produced by people; the voice is synthesised or converted.AI instrumental with human vocalsThe backing track came from a generator; the vocal is a real recorded performance.Fully AI-generated trackMusic and vocals both produced by a generator, with prompt and curation work by you.

2. Tool or model used (optional)

3. What did you do? (optional)

4. Where is it going?

Your disclosure

This recording is AI-assisted: generative tools contributed to parts of the writing and production, and the arrangement, performance and final mix decisions are human. All rights required for this release are held or licensed, and project files are retained in case the release is queried.

Paste this into the AI-involvement or notes field, and make sure the credit list itself stays accurate for everyone who contributed. This is the point where disclosure actually enters industry metadata.

The wording matters more than the label does

Nearly every platform dispute we hear about publicly isn't really about whether a generator was involved at all — it's about a mismatch, where metadata claims one thing and the audio, credits or artist name suggest another. Stating plainly what the model produced and what a person did removes that mismatch, and it costs you one sentence.

Keep in mind what a disclosure isn't. It isn't a detector result, and a detector result can't stand in for it. Our own analysis returns a probability from measurements of the audio — that's evidence, not a record of provenance. See what a result actually means and where the limits sit. The only lasting record of how a track was made is the one you keep yourself: session files, prompt history, stems, dated exports.

Where each platform asks the question

The distributor's upload flow is the field that actually matters, since that answer travels straight into store metadata. YouTube asks separately during upload and runs a distinct process for singing-voice likeness. Some services classify uploads on their own and quietly adjust discovery without asking you anything. The current shape of all this is covered on AI music rules by platform.

Questions about disclosure

Am I legally required to disclose that a track used AI?: There's no single rule that covers every case. Requirements come from the platform you're publishing to and, more and more, from regional transparency law — not from a universal music-industry standard. In practice, the disclosure that matters most is the answer you give your distributor at upload, since that field is what flows into store metadata.
Does disclosing AI involvement hurt a release?: It can affect how a track surfaces on services that classify AI uploads, but it rarely leads to removal. A false answer is the costlier path — metadata disputes and account-level penalties are far worse outcomes than a track that gets slightly less editorial push.
What actually counts as generative AI here?: Tools that produce new musical material or a synthetic voice. Pitch correction, stem separation, noise reduction, amp modelling and mastering assistants are processing, not generation — every platform treats them as ordinary production steps.
Is anything I type here saved anywhere?: No. The statement is built entirely in your browser as you type it. Nothing gets uploaded, logged or kept — same principle as the detector itself.
Can a detector verify that my disclosure is truthful?: No — and that's precisely why disclosure matters. Acoustic analysis gives you probabilistic evidence about a recording, never a record of how it was made. Accurate metadata and retained project files are the only lasting proof of that.

This page offers orientation, not legal advice. Platform terms shift over time — check the current version before a release you actually care about.