> 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/player-app/managing-player-storage.md).
# Managing Player storage
Players will automatically manage stored files on the local library and remove files that are no longer needed.
### Rules for keeping or deleting a file
The CMS tells the Player which files it needs for the next “N” days of playback (where “N” days is defined in the CMS settings). All of the files in this list will be kept in the local library.\
\
Once a file is removed from this list it will remain in the local library for 30 days after which it will be automatically deleted.\
\
Change the "N" parameter from the CMS:
1. Navigate to CMS Settings located under the Administration section of the main CMS
2. From the General tab, enter a time in seconds for the Send files in advance field
3. Save
The default value is set at 172800 which is 2 days. This setting should be adjusted carefully as it directly affects the size of the Local Player Library and the amount of work the CMS has to do with each collection interval.
{% hint style="info" %}
We recommend keeping the default setting unless there is a specific reason to change it.
{% 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://docs.xibosignage.com/kb/player-app/managing-player-storage.md?ask=&goal=
```
`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.