Every Common UI Menu Icon: A Complete Guide

Master the essential navigation icons that power modern web and application interfaces

Menu icons are the silent signposts of digital interfaces. Every day, millions of users tap, click, and interact with these small graphical elements to navigate websites, use applications, and complete tasks. Despite their small size, menu icons carry tremendous weight in user experience design--they guide users, communicate functionality, and often determine whether someone can find what they need or abandons out of frustration.

This guide provides a comprehensive reference for every common UI menu icon used in modern web and application design. We'll explore each icon's purpose, ideal use cases, recognition patterns, and implementation best practices to help you create intuitive, accessible navigation experiences. Whether you're building a new application or refining an existing interface, understanding these navigation patterns is essential for delivering exceptional user experiences through thoughtful web development practices.

The Hamburger Menu

The hamburger menu--named for its resemblance to a stacked burger with its three horizontal lines--is arguably the most recognizable menu icon in digital interface design. Originally created by interaction designer Norm Cox for the Xerox Star in 1981, this icon has become ubiquitous across mobile applications and responsive websites worldwide.

What It Represents

The hamburger menu icon signals that additional navigation options are hidden behind it, waiting to be revealed when the user interacts with the control. Its core function is to apply progressive disclosure--showing only what's necessary at first and revealing additional options on demand. This makes it especially effective on mobile interfaces where screen real estate is precious.

When to Use the Hamburger Menu

According to research from the Nielsen Norman Group, hamburger menus are most effective in specific contexts:

  • Mobile screens with limited space: Mobile interfaces benefit significantly from hamburger menus because they keep the primary viewport clean while still providing full navigation access. Users have come to expect this pattern on smartphones and tablets.

  • Low-frequency features: Secondary actions such as settings, account options, preferences, or advanced tools work well behind hamburger menus. These aren't features users need constantly, so hiding them reduces visual clutter without impeding common workflows.

  • Complex navigation structures: When you have many navigation items (typically more than five primary sections), the hamburger menu provides a clean way to organize and hide options that don't need constant visibility.

When to Use the Hamburger Menu

Mobile Screens with Limited Space

Mobile interfaces benefit significantly from hamburger menus because they keep the primary viewport clean while still providing full navigation access.

Low-Frequency Features

Secondary actions such as settings, account options, preferences, or advanced tools work well behind hamburger menus.

Complex Navigation Structures

When you have many navigation items, the hamburger menu provides a clean way to organize and hide options.

Best Practices for Hamburger Menu Implementation

Based on current UX research, follow these guidelines for effective hamburger menu design:

  1. Standard three-line icon: Use the universally recognized three horizontal lines. While variations exist, the standard form ensures immediate recognition across user populations.

  2. Consistent placement: Position the hamburger icon where users expect it--typically the top-left or top-right corner of the interface. Consistent placement reduces cognitive effort.

  3. Add text labels: Consider pairing the hamburger icon with a "Menu" label, especially for products targeting less tech-savvy audiences.

  4. Clear animation: Smooth transitions when opening and closing the menu help users understand spatial relationships.

  5. Accessible touch targets: Ensure the tap target meets minimum size requirements (at least 44×44 pixels) to accommodate users with varying motor abilities.

  6. Prioritize content inside: Only place items inside the hamburger menu that users don't need constantly. Keep high-frequency actions visible elsewhere.

The Kebab Menu

The kebab menu takes its name from its vertical arrangement of three dots, resembling a shish kebab on a skewer. Unlike the hamburger menu's horizontal orientation, the kebab's vertical stacking makes it immediately distinguishable while serving a different primary purpose.

What It Represents

The kebab menu typically indicates a set of contextual actions related to a specific item or content element. It's commonly used for item-specific operations such as edit, delete, share, archive, or duplicate actions.

Ideal Use Cases

  • List item actions: In tables, feeds, or item collections, the kebab menu provides space for secondary actions without cluttering each row with multiple buttons.

  • Content card operations: Blog posts, product cards, or user profiles often use kebab menus for options like bookmark, share, report, or more details.

  • Inline editing controls: When users need to modify specific content elements, the kebab menu offers access to edit functions without dedicated buttons for every possible action.

Design Considerations

Position the kebab menu consistently--usually at the end of the row, card, or content block it controls. Ensure the three dots are large enough to be tappable and provide adequate spacing from surrounding elements to prevent accidental taps.

Ideal Use Cases for Kebab Menu

List Item Actions

In tables, feeds, or item collections, the kebab menu provides space for secondary actions without cluttering each row.

Content Card Operations

Blog posts, product cards, or user profiles use kebab menus for options like bookmark, share, or report.

Inline Editing Controls

The kebab menu offers access to edit functions without dedicated buttons for every possible action.

The Meatball Menu

The meatball menu features three horizontal dots, named for its resemblance to meatballs on a plate. This variation serves similar purposes to the kebab but with a horizontal orientation that creates visual distinction.

What It Represents

The meatball menu traditionally indicates global or application-level settings and preferences, though usage varies across platforms and applications. It's commonly found in header areas or navigation bars where users expect to find configuration options.

Common Applications

  • Account settings: Many applications use the meatball menu to access user profiles, preferences, billing, and account management features.

  • Application preferences: Global app settings, themes, notifications configuration, and help sections often live behind meatball menus.

  • Platform-level navigation: Some applications use meatball menus for switching between views, accounts, or organizational units within a larger system.

Distinguishing from Hamburger

The key difference lies in position and scope. While hamburger menus typically appear in header corners and control global navigation, meatball menus often appear inline with content or in header areas controlling application-level functions.

Common Applications for Meatball Menu

Account Settings

Many applications use the meatball menu to access user profiles, preferences, billing, and account management.

Application Preferences

Global app settings, themes, notifications configuration, and help sections often live behind meatball menus.

Platform-Level Navigation

Some applications use meatball menus for switching between views, accounts, or organizational units.

Essential Menu Icons

Beyond the navigation-focused icons, several additional menu icons serve critical functions in modern web and application interfaces. Understanding these patterns helps you create comprehensive, intuitive navigation systems.

Plus/Add Icon

The plus symbol, representing addition or creation, serves as one of the most action-oriented menu icons in interface design. It commonly triggers content creation flows and frequently appears within Floating Action Buttons (FAB) on mobile interfaces.

Gear/Settings Icon

The gear or cogwheel is universally recognized as the symbol for settings, preferences, and configuration options. Its mechanical origins translate effectively to digital interfaces where users adjust how applications behave.

Search Icon

The magnifying glass represents one of the most universally recognized interface elements. Research shows that search icon placement in the upper-right corner of interfaces aligns with user expectations.

User/Profile Icon

User icons represent account access, personal profiles, and individual users within multi-user systems. Common representations include simple silhouettes, avatar placeholders, and initial-based icons.

Cart Icon

For e-commerce applications, the shopping cart icon represents one of the most critical functional elements. Its recognition extends beyond web contexts into physical retail, making it instantly intuitive for most users.

Bell/Notification Icon

The bell icon has become the standard representation for alerts, notifications, and updates requiring user attention. Clear visual distinction between read and unread states helps users understand their notification status.

Plus/Add Icon

The plus symbol represents addition or creation. It commonly triggers content creation flows and frequently appears within Floating Action Buttons (FAB) on mobile interfaces.

Gear/Settings Icon

The gear or cogwheel is universally recognized as the symbol for settings, preferences, and configuration options. Should always be accompanied by text labels for accessibility.

Search Icon

The magnifying glass represents one of the most universally recognized interface elements. Best placed in the upper-right corner following established conventions.

User/Profile Icon

User icons represent account access and personal profiles. Common representations include simple silhouettes, avatar placeholders, and initial-based icons.

Cart Icon

For e-commerce, the shopping cart icon is critical for conversion. Should remain consistently visible throughout the shopping experience with quantity indicators.

Bell/Notification Icon

The bell icon represents alerts and updates. Should include clear visual distinction between read and unread states through badges or color changes.

Icon Accessibility Considerations

Creating accessible menu icons requires attention to multiple factors beyond basic visibility. Inclusive design ensures all users can effectively navigate your interface regardless of ability. When designing navigation systems, accessibility should be a primary consideration from the start, not an afterthought. Our web development approach prioritizes inclusive design principles that ensure your applications work for everyone.

Size and Touch Targets

Minimum touch target sizes ensure usability across user populations:

  • Web interfaces: At least 44×44 pixels for interactive elements
  • Mobile applications: 44×44 points (iOS) or 48 density-independent pixels (Android)
  • Motor impairments: Larger targets benefit users with reduced dexterity

Color and Contrast

Menu icons must meet contrast ratio requirements for users with visual impairments:

  • WCAG 2.1 Level AA: 4.5:1 contrast ratio for normal text, 3:1 for large text
  • State indication: Interactive states (hover, active, disabled) should be visually distinct
  • Dark mode compatibility: Icons should remain visible across theme variations

Screen Reader Support

Every menu icon requires appropriate accessibility markup:

  • ARIA labels: Descriptive labels explaining icon function
  • Role attributes: Identifying interactive elements correctly
  • Focus indicators: Visible focus states for keyboard navigation
Accessibility Requirements for Menu Icons
RequirementSpecificationNotes
Minimum Touch Target44×44 pixels (web) / 44pt (iOS) / 48dp (Android)Accommodates users with motor impairments
WCAG Contrast Ratio4.5:1 for normal text, 3:1 for large textEnsures visibility for users with visual impairments
ARIA LabelsDescriptive labels explaining icon functionRequired for screen reader support
Focus IndicatorsVisible focus states for keyboard navigationEssential for keyboard users
Color IndependenceIcons should be recognizable without colorSupports color blindness
Accessible Icon Implementation
1<button aria-label="Open navigation menu" aria-expanded="false" aria-controls="main-menu">2 <svg aria-hidden="true" focusable="false">3 <use href="#icon-hamburger"></use>4 </svg>5</button>

Menu Icon Best Practices Summary

Based on comprehensive research from LogRocket, Nielsen Norman Group, and Lollypop Design, these principles guide effective menu icon implementation:

1. Consistency Within Your Interface

Use the same icon for the same function throughout your application. Inconsistent icon usage creates confusion and undermines learned behaviors.

2. Follow Established Conventions

Users bring expectations from other applications. Deviations from conventions require additional cognitive effort and may confuse users until new patterns are learned.

3. Pair Icons with Labels When Possible

Text labels eliminate ambiguity and support users unfamiliar with iconographic conventions. Consider label placement next to icons or tooltips that appear on hover/focus.

4. Consider Your Audience

Technical users may recognize sophisticated iconography immediately, while general audiences may need more guidance. Match icon complexity to user sophistication.

5. Test with Real Users

Before finalizing icon selection and placement, conduct usability testing with representative users. Observing actual behavior reveals recognition issues that may not be apparent during design.

6. Plan for Accessibility from the Start

Incorporate accessibility requirements (contrast, size, screen reader support) from initial design stages rather than retrofitting solutions later.

7. Maintain Visual Hierarchy

Menu icons should be prominent enough to be discovered but not so dominant that they compete with primary content. Balance visibility with context.

Conclusion

Menu icons are fundamental elements of digital interface design, serving as the primary way users navigate, configure, and interact with applications. From the ubiquitous hamburger menu to specialized icons for search, settings, and notifications, each element carries specific connotations and expectations that designers must understand and respect.

The most effective menu icon implementations share common characteristics: they follow established conventions, appear in expected positions, provide clear feedback when interacted with, and remain accessible to all users regardless of ability. By understanding the purpose, recognition patterns, and best practices for each common menu icon, designers and developers can create interfaces that feel intuitive and efficient.

Remember that icons exist to reduce cognitive load, not increase it. When an icon requires explanation, consider whether a different approach might serve users better. The best menu icons are those users don't have to think about--they simply work. Ready to implement these best practices in your next project? Our web development team specializes in creating intuitive, accessible user interfaces that delight users.

Need Help Creating Intuitive Navigation?

Our team of designers and developers can help you build user interfaces that work seamlessly across all devices and user abilities.

Sources

  1. LogRocket Blog: Every common UI menu icon and its use case - Comprehensive breakdown of common UI menu icons with practical use cases
  2. Nielsen Norman Group: The Hamburger-Menu Icon Today - Authoritative UX research on hamburger menu recognizability
  3. Lollypop Design: Hamburger Menu Design Best Practices - Modern guide covering hamburger menu design and alternatives