All use cases

Music for Content & Brands

Use a generated song in a commercial project

Confirm the output permission and the rights to the inputs before delivery. Platform acceptance and commercial permission from the generation service are separate checks.

Confirm the output permission and the rights to the inputs before delivery. Platform acceptance and commercial permission from the generation service are separate checks.

1. Choose a version worth finishing

Listen to the whole song in Library with the lyric in front of you. Check the first vocal entrance, the central hook, every section transition, and the ending. A strong chorus does not compensate for a broken word in the verse or a cut-off final note.

Keep the title, source song identifier, model, generation date, lyric, and any reference names together. If you need a change, make it before distributing rather than treating an upload as a listening test. Keep the original and the final candidate separately.

Two completed generated versions in Library, ready for comparison.
Library

2. Check the song’s commercial permission

ACE-Step v1.5 outputs, including v1.5 XL, may be used commercially on Free and paid plans under the Terms. For other models, an active paid subscription at generation is required for commercial use. Upgrading later does not retroactively change a Free-plan output; canceling later does not revoke permission already granted.

Then check the underlying lyric, composition, recordings, and any voice or likeness you used. A Cover or Mashup does not clear a copyrighted reference. If a collaborator supplied material, document the permissions and the agreed credits. See commercial-use rules and Terms of Service.

3. Export the files your destination actually accepts

Open the chosen song’s Download menu. ACE-Step offers MP3 on Free and paid plans, but no WAV. Other models require paid audio-download access and offer the formats shown for the song. A WAV converted from MP3 does not recover lost detail.

Check the destination’s current technical requirements before choosing the file. If it requires a format or quality you do not have, resolve that in production first; renaming a file or putting MP3 audio in a WAV container is not a quality upgrade. Keep the listening copy, the available source export, artwork, and lyric in a clearly named release folder.

The download dialog shows the formats available for this example song.
Library → Download

4. Choose the right publishing route

For Spotify, Spotify’s guidance says to work with a distributor. Compare the distributor’s current AI-content rules, costs, metadata requirements, and delivery process. Do not assume ACE Music sends the song to stores or collects royalties for you.

For example, DistroKid’s AI policy requires the necessary rights and prohibits unauthorized impersonation, infringement, and mass-generated spam. Acceptance is not guaranteed by using a particular music tool.

For a YouTube video, check the current AI disclosure guidance during upload. It identifies AI-generated music as a disclosure example. Disclosure, music permission, and monetization eligibility remain separate checks.

5. Review metadata and archive the release

  • Use consistent song and artist names across your audio file, artwork, and submission.
  • Enter contributors and rights information accurately. Follow the distributor’s current fields rather than inventing credits for a model.
  • Listen to the exact file being delivered, including its final tail. Check that it is the intended version.
  • Keep the delivered file, permission records, and submission details so a later correction can be traced.

This workflow prepares a release package; it does not promise chart placement, revenue, exclusive copyright, or acceptance by every service.