> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/en/userguide/upload.md).
# Upload videos
Using the Charlla player starts with uploading a video. Click the upload button to add videos of 60 seconds or less to your Library.
{% hint style="danger" %} **You can't upload videos longer than 60 seconds.**
{% endhint %}
{% hint style="danger" %} **Videos with a source resolution above 1080p are automatically converted to 1080p. (Some low-end Android phones can't play very high-resolution videos.)**
{% endhint %}
1. Click **\[Upload]** at the top.
2. Click **\[Select file]**, or drag and drop your video files into the pop-up.
1. There's no resolution limit, but videos above Full HD (1080 x 1920) are converted to Full HD during upload.
2. Videos must be 60 seconds or less.
3. You can upload up to 15 videos at a time.
3. Area 1 shows the progress and result of each upload (up to the 15 most recent). Click **\[Delete all]** (2) to clear your upload history.
{% hint style="info" %}
**While a video is uploading, it shows a loading bar in the list and no preview appears in the sidebar.**\
**You can still edit and save player settings while uploads are in progress.**
{% 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://support.charlla.io/en/userguide/upload.md?ask=&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.
