> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/faq/navigation-and-header/why-is-my-mobile-menu-different-from-the-desktop-menu.md).

# Why is my mobile menu different from the desktop menu?

Why the Volume mobile menu can show different links from the desktop header, and where to edit each one.

Because they are two different sections.

The desktop navigation lives in the **Header** section. The mobile navigation is the **Menu drawer**, a separate section that sits in the **Overlay** group at the bottom of the section list — next to **Cart drawer** and **Popup**, not underneath the header.

That means the drawer has its own **Menu** setting. If you edited the header's menu and nothing changed on a phone, you edited the wrong one.

{% stepper %}
{% step %}

### Open the drawer

In **Customize**, scroll to the **Overlay** group in the section list and click **Menu drawer**.
{% endstep %}

{% step %}

### Set its menu

Change **Menu** to the same menu the header uses — or to a different one, if you deliberately want a shorter list on mobile.

**Heading** above it is the title shown at the top of the drawer, and **Position** puts the drawer on the **Left** or the **Right**. If you use [Smart Category Menu](/docs/volume-themes/navigation/smart-category-menu.md) on desktop, tick **Smart Category Menu** here as well — the drawer does not inherit it from the header.
{% endstep %}

{% step %}

### Add the extras

The drawer takes its own blocks: **Secondary menu**, **Buttons**, **Account**, **Localization**, **Store selector**, **Social media**, **Text**, **Context image**, **Banner slideshow**, **Menu item image**, **Nested menu**, **Custom Liquid**, **Empty space** and **Line**. None of them are inherited from the header, so add whatever your mobile visitors need.

**Pinned block** decides which one stays fixed at the bottom of the drawer: **None**, **Country and language**, **Buttons**, **Account**, **Context image** or **Store selector**.
{% endstep %}
{% endstepper %}

{% hint style="success" icon="lightbulb" %}
Finish the block list with an **Empty space** block. The pinned block floats over the drawer content, so without that padding it covers whatever you placed last.
{% endhint %}

### Other things that differ on mobile

There is no separate mobile header section — the **Mobile layout** group inside the **Header** section is where that lives. **Header layout** there offers **Logo left, burger menu left**, **Logo left, burger menu right** and **Logo center, burger menu left**, and **Enable search field** puts a search field into the mobile header. The mobile spacing settings are in the same section.

On desktop the burger is optional: **Header → Burger menu → Show burger**, with **Burger** to render it as **Icon**, **Icon with text** or **Text**. **Hide burger on mobile** hides it on small screens, where it is on by default.

The language and country switchers exist in several independent places — the **Header** section, the **Announcement bar**, the drawer's **Localization** block, and the footer sections. Switching one on does not switch on the others. If the country picker is missing only on mobile, add the drawer's **Localization** block.

{% hint style="success" icon="lightbulb" %}
More in [Menu Drawer](/docs/volume-themes/navigation/menu-drawer.md) and [Announcement Bar & Footer](/docs/volume-themes/navigation/announcement-bar-and-footer.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/volume-themes/faq/navigation-and-header/why-is-my-mobile-menu-different-from-the-desktop-menu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.