Skip to main content

BETANow in public beta.Public betaBeta

日本語Español

NAV-005 Published

Mega menu header

A header where hovering over or pressing a menu item opens a full-width panel beneath, with the child pages arranged in groups with short descriptions.

FigmaThis part is included in our free, editable Figma file: 235 website UI patterns across 32 parts, 2 designs each Open in Figma Community ↗ (opens in a new tab)

Wireframe (desktop) | Mega menu header

Mega menu header UI design (desktop wireframe)

Wireframe (mobile) | Mega menu header

Mega menu header UI design (mobile wireframe)

What changes on mobile

  1. Descriptions dropped; choose by name and group: Descriptions on a narrow screen make the list far too long, so only group names and page names remain.
  2. Only the menu scrolls: Even when the list is taller than the screen, the × button in the header stays visible to close it.
  3. Current section open by default: When the menu opens, the child pages of the current section are visible at once.
  4. Open/close and navigate kept distinct: Buttons that open in place and links that navigate differ in icon, position and behavior.

Before you choose this pattern | Mega menu header

Good fit

  • Many child pages that make a long single-column list, or are easier to choose in groups
  • You want short descriptions on the child pages so readers can compare and choose
  • Several angles under a large category: services, industries, products
  • Sites with many pages: companies with many services, manufacturers with many products, schools and organizations

Poor fit

  • Few child pages that fit in a single-column list (the <a href="/patterns/en/header-dropdown/">dropdown header</a>, which opens a single-column list, works better)
  • Few main pages and no child hierarchy (the <a href="/patterns/en/header-horizontal/">horizontal header</a>, with the menu in one row, works better)
  • Child pages are added or renamed often, and keeping the panel descriptions updated is hard

Why this wireframe works | Mega menu header

Many child pages, scannable by category

In a single column, the more child pages there are, the longer the list and the harder the search. Child pages are grouped, such as “Build”, “Grow” and “Rethink”, and laid out side by side, so many can be scanned at once.

Compare the descriptions as you choose

Child pages whose names alone do not reveal the difference leave people unsure which to open. A one-line description under each name lets people compare within the panel.

A clue where to start

With many child pages, people who have not decided cannot pick any and stop. The left of the panel carries a description of the category and “See all services”, so people can start from the category page.

Set apart from the content while open

A large panel overlays much of the content, making its edges unclear. This wireframe dims the content while the panel is open, and clicking the dimmed area closes it.

People know which section and which page they are on

The more child pages, the harder it is to tell which category the current page belongs to. The current child page is marked and the parent “Services” is underlined and bold to show the current section. In the code, aria-current=”page” goes only on the link to the current page itself (the child).

Common mistakes | Mega menu header

Every child page listed, so the panel cannot be scanned

Listing all child pages makes the panel too crowded to find anything. Show the main child pages that can be scanned at a glance, and let the rest be found from the category page.

Groups that do not match how readers search

Grouping by internal department or product code leaves readers unsure which group to look in. Group by purpose, industry, audience or another angle readers choose with.

Long descriptions turn the panel into prose

Several lines per child page make the panel read like an article. Keep descriptions to about one line and leave the detail to each page.

The panel closes too soon or vanishes during use

In a large panel, child pages sit far from the parent item. If the panel closes while the pointer is moving or while over it, nothing can be chosen. Do not close during movement or use, and add a short delay against accidental opening and closing.

The bottom of the panel is cut off

What fits on a large screen can overflow the bottom on a low laptop screen. Check on low screens, and if it does not fit, reduce the items or let the panel scroll.

Group names and child pages not linked for screen readers

Even when child pages sit under a group name visually, without an association in the code screen readers cannot tell which group an item belongs to. Associate the group name as the list’s label or build it as a heading.

FAQ | Mega menu header

Dropdown or mega menu: how do I choose?

With few child pages that fit a single-column list, the dropdown header is easier. With many child pages, or when grouping and descriptions help the choice, the mega menu suits better. They can be mixed on one site: a mega menu for categories with many children, dropdowns for the rest.

Can the panel include images?

For products or case studies chosen by appearance, images can help. More images make the panel heavier and slower, though. When names and short descriptions are enough, text is usually sufficient. If an image conveys something the name does not, give it alt text that says so; if it only repeats the adjacent text, an empty alt attribute is an option.

How many child pages can the panel hold?

As many as can be scanned at a glance. It depends on screen width and height and whether descriptions are included; this wireframe shows eight under “Services”. If not all fit, keep the main ones and let the rest be found from the category page.

Should descriptions be shown on mobile too?

Not necessarily. Descriptions on mobile make the list long, so this wireframe drops them and shows only group names and page names. If a description is essential to the choice, make it readable on the category page.

Related pages

Share this pattern

Send this page to your team or your design partner.

Was this pattern useful?

Written by

Yuta Okano

ENVY DESIGN Inc.

CEO / Director / Designer

14 years in the web industry. Has worked on more than 500 web projects, from corporate and recruiting sites to e-commerce. Focuses on information architecture, direction and design, from planning websites to improving them. In recent years he has focused on AIO (AI optimization) and GEO, helping sites get cited by generative AI search such as ChatGPT, Perplexity and Google AI Overviews.

Review and revision history

  1. Published AvatarYuta Okano Pattern published