> For the complete documentation index, see [llms.txt](https://support.audacityteam.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.audacityteam.org/au3/basics/recording-your-voice-and-microphone/setting-recording-levels-and-playback-levels.md).

# Setting recording and playback levels

The recording and playback levels can be set using the sliders in the Recording and Playback meter toolbars:

![Recording meter toolbar and Playback meter toolbar with level sliders](https://2387260374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhmBVzGzh8SctWQ6jPR%2Fuploads%2FHKzH5xcuQtiewMtlBquV%2FRecording%20and%20Playback%20Meter%20Toolbar.png?alt=media\&token=70ff4b46-b49e-44d4-82c1-bbf4834a2d19)

* The slider with the microphone icon sets the recording volume on a system level. If the operating system is prohibiting this action, this slider will be inactive.

![The Recording Level slider will change the level of your recording device on a system level](https://2387260374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhmBVzGzh8SctWQ6jPR%2Fuploads%2F5ZUECdCIl9SqyZfTWTcb%2FLevel%20slider%20Audacity%20and%20system.png?alt=media\&token=ac44e605-7895-45e9-9c32-b7bf466f14ad)

* The slider with the speaker icon sets the playback volume relative to the system volume. It does not affect the volume of exported files, use the gain sliders on each track to edit those.

{% hint style="success" %}
**Best practice:** Before starting to record, click on the microphone icon and select **Start Monitoring** to activate the recording level meter.\
If it enters the yellow or red area (-9 dB to 0 dB) when testing with a normal volume, lower the recording level to prevent clipping and distortions in the real recording.
{% endhint %}

![Activate the recording level meter before starting to record](https://2387260374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhmBVzGzh8SctWQ6jPR%2Fuploads%2FYtYYPHXAUlg4XiJqS6wI%2FSingle%20Line%20Start%20Monitoring.png?alt=media\&token=bce8c200-de5c-4d1b-801f-72a7b839dd93)

![Use the recording level slider to reduce the level when it is too high](https://2387260374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhmBVzGzh8SctWQ6jPR%2Fuploads%2F4k237kxmQLPTe2xbK9CN%2FRecording%20Level%20Slider%20Adjustment.png?alt=media\&token=8aeb9c89-bb76-4bc5-b8f0-450c3bb3e07a)

{% hint style="info" %}
If you selected **1 (Mono) Recording Channel** on the **Audio Setup > Recording Channels** the meter will only display the level on the **L**eft channel
{% endhint %}

![Monitoring 1 (Mono) Recording Channel level](https://2387260374-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhmBVzGzh8SctWQ6jPR%2Fuploads%2FOo7YW3s7Dhs5A8UkPSJj%2FMono%20channel%20recording%20level%20meter.png?alt=media\&token=45f61097-e94a-41f6-9ce1-94e0fe99e695)


---

# 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://support.audacityteam.org/au3/basics/recording-your-voice-and-microphone/setting-recording-levels-and-playback-levels.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.