Context Menu vs. Dropdown
A context menu shows actions for the item you click or press. A dropdown opens from a visible button with a clear purpose.
Use a context menu as an extra shortcut, not the only path. Use a dropdown when people need to see where the menu opens.
See what each pattern does
Try each example. Then read about the job it is made to do.
macOS Context Menu
A macOS Context Menu is a short list of actions for the item under the pointer. It opens with a secondary click, such as a right-click.
Right-clicking a selected file shows Rename, Duplicate, Share, and Move to Trash without leaving the list.
- Use it when
- Use it for a short set of less common actions that depend on the item or selection under the pointer.
- Do not use it when
- Never make a context menu the only path to an important command. Keep app-wide commands away from actions for one item.
- Name used in code
AppKit NSMenu / SwiftUI contextMenu
Dropdown & Context Menu — Learning Bundle
This learning bundle compares menus by how they open. A dropdown opens from a control. A context menu belongs to one object and often opens at the pointer. The bundle is not one standard menu term.
DropdownMenu / ContextMenuThe More button opens general actions. Right-clicking a file opens actions only for that file.
- Use it when
- Choose a menu whose trigger and object fit the task. Then build its keyboard behavior.
- Do not use it when
- Never put form fields or the main site navigation inside a command menu.
- Name used in code
DropdownMenu / ContextMenu
Quick comparison
| UI pattern | Best for | Not for | Name used in code |
|---|---|---|---|
| macOS Context Menu | Use it for a short set of less common actions that depend on the item or selection under the pointer. | Never make a context menu the only path to an important command. Keep app-wide commands away from actions for one item. | AppKit NSMenu / SwiftUI contextMenu |
| Dropdown & Context Menu — Learning Bundle | Choose a menu whose trigger and object fit the task. Then build its keyboard behavior. | Never put form fields or the main site navigation inside a command menu. | DropdownMenu / ContextMenu |
Before you ship
- 01
Write down what the person needs to do.
- 02
Test the keyboard, focus, touch, zoom, loading, empty, and error states.
- 03
Make sure people can get the same information without hover or motion.
- 04
Test with real content on both small and large screens.
Comparison request you can copy
Copy this when your team needs help choosing between the patterns.
Choose the best pattern from macOS Context Menu, Dropdown & Context Menu — Learning Bundle for our real user flow. Use this rule: A context menu shows actions for the item you click or press. A dropdown opens from a visible button with a clear purpose. Write down the task, amount of content, and cost of stopping the flow. Check keyboard, touch, loading, error, and reduced-motion behavior. Explain your choice, then build the smallest accessible version with the project's design system.