> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/reference/working-with-components/tabs.md). # Tabs ## Overview A series of tabs. The component supports *manual* (for a static options list) and *dynamic* options configuration.

### Properties

Name	Type	Description
`name`	`string`	Component name
`length`	`number`	Total number of tabs
`selectedTab`	`tab`	The selected tab (alternative property to index)
`selectedIndex`	`number`	Index of the currently selected tab

### Methods

Name	Parameters	Returns	Description
`selectTab`	`index: number`	`void`	Select tab by its index

### Triggers

Name	Description
On Init	Triggered when the component is initialized
On Tab Change	Triggered when a tab is switched

## Working with the component In the right side panel, under the *Appearance* section, you can set up how your component will look like. You can configure such settings as: * Height * Margin * Tabs overflow style * Tab text wrap * Tabs style *Tabs overflow* and *text wrap* allow you to control the layout: you can switch between **Arrows** and **Scroll** and enable text wrapping for longer tabs to keep things readable.

--- # 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.uibakery.io/reference/working-with-components/tabs.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.