> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/advanced-settings/settings-parameters/transcribe.md).

# \&transcribe

Enables transcription and closed captioning

Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))

## Aliases

* `&trans`
* `&transcript`

## Options

Example: `&transcribe=de-DE`

| Value                     | Description                                                                                              |
| ------------------------- | -------------------------------------------------------------------------------------------------------- |
| `en-US`                   | American English                                                                                         |
| `de-DE`                   | German                                                                                                   |
| `pt-PT`                   | Portuguese                                                                                               |
| (any xx-XX language code) | You can check for additional language codes [here](https://www.science.co.il/language/Locale-codes.php). |

## Details

The transcription service uses default browser/system mic as a source and cannot be muted.

Generally needs to be used in conjunction with [`&closedcaptions`](/advanced-settings/settings-parameters/and-closedcaptions.md).

{% hint style="warning" %}

* The transcription audio source will be the default microphone of the browser, which often is the same as the system's default input source.
* It is not necessary the microphone that has been selected in VDO.Ninja. Please double check this if the transcription isn't working.
* The mute button of VDO.Ninja will not work with this feature; at the moment anyways.
* Only one transcription service can run at a time.
* Chrome or other browsers will prevent the user from running multiple transcription services at a time. Since the transcription services of most browsers requires the Internet.
  {% endhint %}

You will normally need Internet access for this to work and be willing to tolerate the occasional hiccup that the browser's transcription service may cause. Service may stop for seconds at a time as a result.

Certain Android devices may not require internet for the transcription to work.

{% embed url="<https://www.youtube.com/embed/3eo85WAXeuk>" %}

{% hint style="danger" %}
Does not work in Safari!
{% endhint %}

## Related

{% content-ref url="/pages/-MZdu6iErcfXbfPCHVU7" %}
[\&closedcaptions](/advanced-settings/settings-parameters/and-closedcaptions.md)
{% endcontent-ref %}

{% content-ref url="/pages/YccJrw5NRcvRZzk141Bs" %}
[Caption.Ninja](/steves-helper-apps/caption.ninja.md)
{% endcontent-ref %}


---

# 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.vdo.ninja/advanced-settings/settings-parameters/transcribe.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.