> For the complete documentation index, see [llms.txt](https://docs.gmetri.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gmetri.com/metaverse/build/elements/audio.md).
# Audio
## Can I add audio to my experience?
{% hint style="info" %}
To play your audio at any desired time, make use of "Rules". Ensure that you apply the "should play" rule, when any event occurs.
{% endhint %}
### Step 1: Add an Audio Element
You can add an Audio file by clicking on the '**+**' icon in the top bar and selecting ‘Audio’.
Adding Audio element
### Step 2: Upload / Choose file
On the right panel, go to properties and select 'Click to Upload'.
You can choose the audio file from your computer or select from the available templates.
Read below to know how to select a file to upload an audio element.
{% content-ref url="/pages/89Dj2jFYZ5UbZ0t6i2fd" %}
[Selecting a file](/metaverse/build/editor/file-manager/3rd-person-scenes.md)
{% endcontent-ref %}
Selecting an audio file
### Step 3: Adjust the Audio element
From the Properties Panel, you can preview the audio element, control the volume, silence it, or set it to loop.
Adjusting the audio element
## Example Experience
{% embed url="" %}
Example Experience - Audio
{% endembed %}
The rules applied in the above experience are shown below
Rules applied in the example experience
---
# 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://docs.gmetri.com/metaverse/build/elements/audio.md?ask=&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.
