> For the complete documentation index, see [llms.txt](https://docs.vntranslator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vntranslator.com/features/extensions/text-to-speech/pocket-tts.md).

# Pocket TTS

{% hint style="info" %}
**Pocket TTS** is an offline, CPU-based TTS engine developed by [Kyutai](https://kyutai.org). It supports English only and does not require a GPU to run.
{% endhint %}

### Installation

There are two ways to install Pocket TTS: using **UV** (recommended) or **PIP**.

<details>

<summary><strong>Install via UV (Recommended)</strong></summary>

UV is a fast Python package manager that handles all dependencies automatically in an isolated environment.

**Step 1 - Install UV**

Open **PowerShell** and run the following command:

```powershell
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
```

For alternative installation methods, refer to the [UV Installation Guide](https://docs.astral.sh/uv/getting-started/installation/).

**Step 2 - Verify the Installation**

After the installation is complete, restart PowerShell and verify that UV is installed correctly by running:

```powershell
uv --version
```

You should see the installed UV version printed in the terminal.

**Step 3 - Run Pocket TTS**

With UV installed, you do not need to install Pocket TTS separately. You can run it directly using the `uvx` command:

```powershell
uvx pocket-tts serve
```

UV will automatically download and install all required dependencies on the first run.

</details>

<details>

<summary><strong>Install via PIP</strong></summary>

If you prefer to install Pocket TTS manually using PIP, follow these steps.

**Step 1 - Install Pocket TTS**

Open a terminal or command prompt and run:

```powershell
pip install pocket-tts
```

**Step 2 - Verify the Installation**

Confirm the installation was successful by running:

```powershell
pocket-tts --version
```

**Step 3 - Run Pocket TTS**

Once installed, start the Pocket TTS server with:

```powershell
pocket-tts serve
```

</details>

***

### Running the Pocket TTS Server

Once the server is running, you can access the web interface at:

```
http://localhost:8000
```

***

### Integrating with VNTranslator

After the Pocket TTS server is running, follow these steps to connect it with VNTranslator:

* Go to **Settings -> Extensions -> Text to Speech**
* Scroll to the **Pocket TTS** settings section
* Enter the **Host** and **Port** of your running Pocket TTS server. By default, these are already set to:
  * **Host:** `http://localhost`
  * **Port:** `8000`

{% hint style="warning" %}
Make sure the Pocket TTS server is running **before** launching a game in VNTranslator. If the server is not running, TTS playback will not work.
{% endhint %}

***

### References

* [Pocket TTS GitHub Repository](https://github.com/kyutai-labs/pocket-tts)
* [Kyutai Blog - Pocket TTS Announcement](https://kyutai.org/blog/2026-01-13-pocket-tts)
* [UV Installation Guide](https://docs.astral.sh/uv/getting-started/installation/)


---

# 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.vntranslator.com/features/extensions/text-to-speech/pocket-tts.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.