Tabs
Last Updated on Dec 15, 2022
Tabs are used to navigate between related content on the page.
Component Variants
Design Principles
- Use tabs to switch between content that is mutually exclusive. Only one tab can be selected at a time.
- Tabs should not be used to filter or show different contexts of a data set. Use a Context Switcher instead.
- Tabs should be aligned to the top, left (or right with RTL languages) of the page or container.
- Tab labels should be very concise. Try to use no more than 2 words. Optionally, tabs can have icons. Every tab should have an icon, not just one tab. Chips are also available.
- Use icons only when they add essential value to the label. Do not use them for pure decoration.
- Do not mix different variants of tabs, e.g. using with & without icons in the same tab group.
- On mobile designs, tabs should not be used. Use a Context Switcher instead. They emulate tabs in iOS. They should be used instead of the tabs component on mobile because they look more like the conventions for mobile tabs.
- For more complex pages, you can add up to two levels of secondary tabs. They are only to be used as a supplement under the primary tab component.
Do's and Don'ts
Related Components