> For the complete documentation index, see [llms.txt](https://docs.acestudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acestudio.ai/voice-cloning/cloning-a-voice-for-vocal-synth/publishing-cloned-voice.md).

# Publishing Cloned Voice

## What Is Voice Publishing?

If you want your voice to be seen by producers all over the world, you can publish your voice to the Creative Library.

## How to Publish My Voice?

To publish your voice, click on the <kbd>Share</kbd> button on your trained voice. After creating a profile of your voice, the application will be sent to the Creative Library team. For the quality of the creative library, the team will review your voice and decide wether to approve it.

{% hint style="warning" %}
Please note: all voices published to the creative library should be royalty-free.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.acestudio.ai/voice-cloning/cloning-a-voice-for-vocal-synth/publishing-cloned-voice.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.