> For the complete documentation index, see [llms.txt](https://docs.rad.live/rad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rad.live/rad/getting-started-subscribers-viewers/rad-tv-for-meta-quest/sideloading.md).

# Sideloading

## Setup

1. Connect your Quest headset to your computer.
2. Turn on your headset. When prompted "Allow Access to Data: The connected device will be able to access files on this headset", select Allow.
   * On Windows, Quest will automatically appear as a drive on your computer.
   * On Mac, you'll need to install [Android File Transfer](https://www.android.com/filetransfer/?fbclid=IwAR3Ay7rndgLxz-bkl_5em_RHVyvLLY6eY2zxUce1_zpqncK-mrtTLEu2SV0) to successfully transfer videos to your headset.
   * On Chromebook/Chrome OS, you'll need to use the Files app to access your headset.
3. Make sure your video files follow the naming convention mentioned below, and drag the files into the default Movies folder. Note: If you need to rename your files, rename them before dragging them into the Movies folder. Quest may run into issues recognizing the new file name if you rename it after dragging it into the Movies folder.


---

# 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.rad.live/rad/getting-started-subscribers-viewers/rad-tv-for-meta-quest/sideloading.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.