> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/media-players/media-players-without-an-internet-connection.md).

# Media Players without an internet connection

Media Players are fully capable of offline playback of content

The Media Player will require an internet connection in the first instance to get connected to the Xibo CMS and to download any schedules and content.

{% hint style="info" %}
The amount of content that can be cached into the future is defined by settings in the Xibo CMS.
{% endhint %}

1. Go to the **Settings** page under the **Administration** section of the CMS
2. Click on the **General** tab
3. Locate the **Send files** in advance setting

This determines how many seconds in the future the calls to `RequiredFiles` should look.&#x20;

{% hint style="info" %}
By default this is set to 2 days
{% endhint %}

{% hint style="info" %}
Anything that is dependent on an internet connection, video streaming, embedded websites for example, will not show when the internet is down.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xibosignage.com/kb/media-players/media-players-without-an-internet-connection.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.
