> 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/containers/layer-sticky-element.md).
# Layer (sticky element)
A container that fixes its position on-screen and does not scroll with the rest of the screen.
## 👉 **The Tag**
This tag creates an element that fixes its position on-screen and does not scroll with the rest of the screen.
**📍 Where to add the tag:** A second-level container.
```
[layer]
```
{% hint style="warning" %}
Layers are positioned considering the full screen dimensions. They are not supported in modals and pop ups.
{% endhint %}
## 🏷️ **How to add the tag**
1. Create your layer element design.
2\. **Wrap it in a container.** Unlike normal containers, layer elements don't need to be the full width of the screen.
{% hint style="warning" %}
Make sure it's not inside another container. It should be a 2nd-level layer.
{% endhint %}
3\. **Paste** the tag into the layer name of this container.
4\. **Place it in the desired position** where you want it to stay fixed in the "default screen area." The default screen area is one app page at 100%. **If you have a splash screen in your design file, Bravo will use it as the default screen size**. If you place the layer element outside of this area (for example on a long page), it will not appear.
5\. Make sure the layer is not inside another container. It should be its own 2nd-level frame.
6\. Import to Bravo & preview on Bravo Vision 🚀
## 💾 Example files
Duplicate the files below to see how to set it up!
{% embed url="" %}
{% file src="/files/-Mg5UHAwVF7HJJ9IivHt" %}
Bravo Sample - Sticky Layer.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/containers/layer-sticky-element.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.