> For the complete documentation index, see [llms.txt](https://docs.plumvoice.com/fuse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plumvoice.com/fuse/application-editor/audio-manager/audio-formats.md).

# Audio Formats

The following links provide users with detailed information about the types of audio files and compression compatible with Fuse.

* For details about the MP3 format: <https://en.wikipedia.org/wiki/MP3>
* For details about the WAV format: <https://en.wikipedia.org/wiki/WAV>
* More info on audio terminology: <http://www.stirlingaudioservices.com/gloss.htm>
* More info about mu-law or (µ-law): <https://en.wikipedia.org/wiki/%CE%9C-law_algorithm>

Plum recommends using the free Audacity application to record audio. Audacity is free and easy to use, but it also has in-depth tools and plugins for more advanced audio manipulation.

Follow this link and select the proper operating system download Audacity: <http://www.audacityteam.org/download/>

## **Supported Audio Formats**

When deciding on the audio format for an application, keep in mind that the Fuse engine automatically runs the files through a compression µ-law algorithm. This downsamples all files to 8-bit, 8kHz.

There are three audio formats for development that are always recommended:

* 8 kHz, 16-bit, linear PCM WAV
* 8 kHz, 8-bit, µ-law WAV
* 32 kbps, 16khz, MP3 (*Note: Anything larger is unnecessary. Poorly recorded MP3 files might not work with Fuse.*)

{% hint style="warning" %}
**Important Note**: All audio files must be recorded in mono, not stereo.
{% 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.plumvoice.com/fuse/application-editor/audio-manager/audio-formats.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.