> 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/troubleshooting/solving-recording-problems/audacity-is-only-recording-silence.md).

# Audacity is only recording silence

## Causes

* Your microphone gain may be reduced. To fix this, see: [Setting recording and playback levels](/au3/basics/recording-your-voice-and-microphone/setting-recording-levels-and-playback-levels.md)
* You may be attempting to record a Bluetooth device at an unsupported sample rate. To fix this, see [Audacity records silence when using a Bluetooth headset as a recording device](/au3/troubleshooting/solving-recording-problems/audacity-records-silence-when-using-a-bluetooth-headset-as-a-recording-device.md)
* You may be attempting to record a device which doesn't produce any sound. To fix this,
  * ensure that all parts of the device are connected properly (cables, microphone, interface, etc),
  * that microphones in need of phantom power are provided with that,
  * that no mute switches on any devices are turned on,
  * that no faders are turned down, and
  * that an input signal is being produced by the source.


---

# 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/troubleshooting/solving-recording-problems/audacity-is-only-recording-silence.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.