> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/3d-configurator/interactions/actions/sounds.md).

# Sounds

The **Sounds** action allows controlling the playback of audio files within a project.

{% hint style="danger" %}
**Note:** Audio playback for end users is only possible after an initial click on the scene. This limitation is enforced by browsers. More details: [Chrome Autoplay Policy](https://developer.chrome.com/blog/autoplay/).
{% endhint %}

<figure><img src="https://2973737105-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAXNLyKVZ2tvtyDr8sVES%2Fuploads%2FGpWOMAM5gd3qJGAIQeb3%2Fimage.png?alt=media&amp;token=78cc602c-4af2-4b12-8d29-42c630a42b70" alt="" width="563"><figcaption></figcaption></figure>

**Settings**

* **Control:**
  * **Play** — Starts audio playback from the beginning or resumes from a paused state.
  * **Pause** — Pauses audio playback at the current position.
  * **Stop** — Stops playback and resets the audio to the beginning.
* **Sound** — Upload an audio file from your computer (**.mp3, .wav, .ogg, .webm**). The file size limit is **5MB**.
  * Uploaded sounds can be reused multiple times in the project via the drop-down list.
  * If an uploaded sound is not used in any interaction, it is automatically removed after reloading the project.
* **Volume** — Adjust the playback volume.
* **Repeat** — Enables looping playback after the audio file finishes.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.vectary.com/documentation/3d-configurator/interactions/actions/sounds.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.