AI transparency
Every song here is AI-generated.
One prompt becomes a file you can keep — and that file was made by a model, not a studio session. This page says which models, how the output is labeled, what you may not do with them, and what happens to your credits when generation fails.
What generates your track
Full songs are made with YuE2-3B, self-hosted on IronSound-operated servers, when that engine is available; otherwise they fall back to Google Lyria 3.5. 30-second clips use Google Lyria 3 Clip, and studio WAV masters use Google Lyria 3.5. Lyria output carries an inaudible Google SynthID watermark; YuE2-3B output does not. Each song's license file names the engine that made it.
Watermarks
Tracks made with Google Lyria (Lyria 3.5 or Lyria 3 Clip) carry an inaudible Google SynthID watermark. Do not remove it. Tracks made with YuE2-3B don't carry SynthID, and they are still labeled AI-generated everywhere below.
How output is labeled
- An AI-generated badge sits on the player, the song page, and next to the download buttons.
- Exported streaming masters and stems carry embedded AI-generated provenance in the WAV metadata, naming the engine (Lyria or YuE2-3B self-hosted).
- Every song ships a license.txt that states how the track was generated and who it is licensed to.
- You get stems and a streaming master on full songs and studio WAVs (not 30-second clips). Stems are an honest split: vocals and drums are separated from the mix, while bass and other are derived reference tracks, not separated stems. The README in the stems zip explains each file.
What you may not do
- Do not clone a specific artist's voice.
- Do not submit copyrighted lyrics you do not own.
- Commercial use follows the per-song license file — not this page.
See how licensing works for the full terms.
Credits and failed runs
Generation costs credits up front. If a run fails, your credits go back to your balance (not a cash refund), so a failed song never spends your pack. See pricing for the credit math.