> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/bravo-tags/loading-experience/state-custom-loading-page.md).
# Loading page
The app page will display in place of the default Bravo loading screen.
The screen with this tag replaces the default Bravo loading screen with a custom design app page.
**📍 Where to add the tag:** A top-level app page
```
[state:loading]
```
## 🏷️ **How to add the tag**
1\. Create a standalone loading screen design.
{% hint style="info" %}
**Pro tip:** use the [Lottie component](/bravo-tags/components/component-lottie.md) to easily add a Lottie animation in your intro.
{% endhint %}
2\. Add a container around the design.
3\. **Paste** the tag into the layer name of the **top-level app page**.
4.Import the design file into Bravo.
5\. Set up your [binding](broken://pages/-Mflj2uo5W_jthsMwnSm) as usual.
6\. Preview the custom loading screen on Bravo Vision. 🚀
{% hint style="info" %}
Tip: If you want to show the loading animation on top of the screen that is being loaded, add a **transparent background** to the screen with the `[state:loading]` tag.
{% endhint %}
## 💾 Example files
Duplicate the files below to see how to set it up!
{% embed url="" %}
{% @figma/embed fileId="dedkxpF23DnniDkjZnqehd" nodeId="453:36" url="" %}
{% file src="/files/-MhwogYPw9o4MEY6z1Gq" %}
Custom Loading.xd
{% endfile %}
---
# 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.bravostudio.app/bravo-tags/loading-experience/state-custom-loading-page.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.
