> For the complete documentation index, see [llms.txt](https://tivimate-player.gitbook.io/tivimate-player-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tivimate-player.gitbook.io/tivimate-player-docs/tivimate-player/how-to/add-an-m3u-playlist-to-tivimate-player.md).

# Add an M3U Playlist to TiviMate Player

### Add a playlist

1. Open TiviMate and select **Add playlist**.
2. Select **M3U playlist**.
3. Choose **Enter URL** or **Select local file**.
4. Paste the M3U URL, or select the playlist file.
5. Give the playlist a name and select **Next**.
6. Confirm the channel list and select **Done**.

### Add guide data

Choose **EPG source** during setup if your provider supplies one. Paste the EPG URL and finish the import.

### Update the playlist

Open **Settings** → **Playlists**. Select the playlist, then choose **Update playlist**.

{% hint style="info" %}
Use the complete URL from your provider. Do not remove query parameters.
{% endhint %}


---

# 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://tivimate-player.gitbook.io/tivimate-player-docs/tivimate-player/how-to/add-an-m3u-playlist-to-tivimate-player.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.