> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/screen-recorder/record-and-capture/screen-recording/microphone-and-audio.md).

# Microphone and audio

Use your microphone to narrate a screen recording.

## Enable your microphone

1. Open the Screendesk extension and expand **Recording settings**.
2. Grant microphone permission when Chrome asks.
3. Choose the microphone you want to use.
4. Turn the microphone toggle on before starting your recording.

Permission and device selection are separate from the microphone toggle. Check that the microphone is enabled before you begin.

## Screen and tab audio

Audio from the shared tab, window, or screen depends on Chrome, your operating system, and the surface selected in the sharing picker. Where Chrome offers a share-audio option, choose it if you want that audio included.

Microphone narration and audio from the shared surface are different sources. Enabling the microphone does not guarantee that system or tab audio is included.

Play back your recording before uploading to check that the expected audio is present.

## Troubleshooting

If your voice is missing, check that the microphone toggle is on, the correct device is selected, and Chrome and your operating system allow microphone access. If another application is using the device, close it and try again.

Instant Replay reconstructs page activity; it does not record microphone audio. Use a screen recording when you need narration.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/screen-recorder/record-and-capture/screen-recording/microphone-and-audio.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 `build a script that syncs our docs to a CMS` 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.