Tabs

Overview

Tabs organize dense product content into a tablist, tabs, and tabpanels that stay readable before animation enters.

Use Tabs when related content has equal standing and the first screen would become too heavy if every panel appeared at once. The page job is organized depth: users should understand the available panels and move between them with pointer or keyboard.

In production, the risk is hidden content that cannot be reached predictably. Implement tablist, tab, tabpanel, selected state, and arrow-key behavior before adding panel motion.

Install

Usage

Component Code

Example Production Use Case

A SaaS product page can use Tabs to organize use cases, integrations, feature groups, or implementation options while keeping each panel crawlable or represented in server-rendered copy.

Best Used For

• Product sections where dense information needs clear grouping.
• Integration, pricing-detail, or use-case sections where each panel has equal weight.
• Pages where keyboard navigation and selected state are part of trust.

Not For

Not for content that must be compared side by side, discovered through search snippets, or read in one continuous flow.

Performance Budget

Avoid remounting heavy panels on every tab change unless necessary, pre-size panel space where possible, and keep transitions short.

Accessibility and Mobile

Expose tablist, tab, selected state, and tabpanel relationships where appropriate. On mobile, switch to stacked sections when horizontal tabs become cramped.

Common Mistakes

• Using tabs for unrelated content.
• Hiding important SEO copy in client-only inactive panels.
• Skipping keyboard movement between tabs.