> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/experience-management/loading-a-saved-experience.md).
# Loading a saved experience
You can load any experience that's saved locally on your device. You can load an experience when you start the Experience Editor or from within the Experience Editor.
## Loading an experience when you start the Experience Editor
1. Open the ENGAGE app and log in.
2. On the menu screen, select **Create & Edit**.
3. On the **Creator Tools** page, select **Experience Editor**.
4. Select **Load Scene**.
5. Select the scene that you want to load.
6. On the file information page, select **Load**.
7. If you haven't accessed the selected location on your current device, select **Download**.
8. In the **Load Location** window, select **Confirm**.
## Loading an experience from within the Experience Editor
1. On the editor panel, select the menu icon (
).
2. Select **My Sequences**.
3. Select a scene to load.
4. Select **Load Content**.
---
# 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.engagevr.io/engage/experience-editor/experience-management/loading-a-saved-experience.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.