> 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/menus/tabs-menu.md).
# Tabs Menu
The menu that stays fixed on every screen as a bottom navigation bar.
## 👉 **The Tag**
This tag, placed on a top-level app page, creates a fixed bottom navigation bar on every screen of the app.
**📍 Where to add the tag:** A top-level app page
```
[menu:tabs]
```
## 🏷️ **How to add the tag**
1. On a blank app page, create a tabs menu design (it can be any height).
2\. Create a 2nd-level container around the menu design.
3\. **Copy & paste** the tag into the layer name of the **top-level app page.**
4\. Link each menu item to the app page you want it to open.
{% hint style="warning" %}
Make sure there are at least 2 menu items linked. If you only have one menu item linked, the tabs menu will not show.
{% endhint %}
{% hint style="info" %}
Remember not to place the starting flow of the prototyping in the tab menu frame. Instead added in the page you want the user to land first. [Learn more ](/set-up-design/setting-up-your-design-file/app-navigation/setting-up-app-navigation-on-figma.md)
{% endhint %}
5\. Import to Bravo & preview on Bravo Vision 🚀
{% hint style="info" %}
In case you want to implement **active states** for the buttons in the tabs menu, check out [this example design file](https://www.figma.com/community/file/938484133762361804).
{% endhint %}
{% hint style="info" %}
You can also hide your tab menu on certain pages by adding the `[nomenu]` tag. *See the example file*
{% endhint %}
## 💾 Example files
Duplicate the files below to see how to set it up!
{% embed url="" %}
{% embed url="" %}
---
# 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/menus/tabs-menu.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.
