> For the complete documentation index, see [llms.txt](https://docs.lootlocker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lootlocker.com/players/files.md).

# Files

The Files feature in LootLocker allows you to store files within a player’s profile, ideal for larger files that benefit from the speed and scalability of a content delivery network (CDN). For smaller data storage needs, we recommend using [Player Metadata](/shared-systems/metadata.md).

With Files, you can upload, update, download, and delete files via API or through the LootLocker Web Console. Each file requires a specified purpose upon upload, and files can be marked as private to restrict visibility from other players. The Files feature also supports up to five revisions per file, with the option to revert to previous versions via the Web Console.

### Use Cases

* Player Profile Picture
* Cloud Saves
* Screenshots

### How-to

* [Configure Files in Web Console](/players/files/how-to/manage-player-files.md)
* [Work with Files In-Game](/players/files/how-to/work-with-files.md)


---

# 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.lootlocker.com/players/files.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.