UI component libraryDropdown, Select, and Menu Components
Selection components

Dropdown components for clear option selection

Compare selection patterns for compact option sets, searchable choices, filters, navigation, and contextual product commands.

Form selectionDashboard filtersAccount menusCommand menusContext actionsNavigation

Match the selection control to the task

A dropdown saves space, but it also hides choices. Use it when options are familiar or secondary, and prefer visible controls when users need to compare a small set of important alternatives.

Searchable selects need keyboard navigation, clear selected state, empty results, and reliable dismissal. Menus for commands should use action language, while form selects should represent values.

Component FAQ

Questions about dropdown, select, and menu components

Practical answers about framework fit, responsive behavior, accessibility, source access, and implementation.

Should I use a select or radio buttons?

Use radio buttons when a small important set should remain visible. Use a select when options are numerous, familiar, or secondary to the main workflow.

What makes a dropdown accessible?

It needs an accessible name, correct keyboard behavior, visible focus, announced selection, predictable dismissal, and focus return to the trigger.

Can a dropdown contain navigation links?

Yes, account and product menus often contain links. Keep navigation links semantically distinct from buttons that perform immediate actions.