Skip to content

Setting up navigation

A clear and concise navigation structure is an important aspect of good project documentation. Material for MkDocs provides a multitude of options to configure the behavior of navigational elements, including tabs and sections, and its flag-ship feature: instant loading.


Instant loading

5.0.0 · Feature flag

When instant loading is enabled, clicks on all internal links will be intercepted and dispatched via XHR without fully reloading the page. Add the following lines to mkdocs.yml:

    - navigation.instant

The resulting page is parsed and injected and all event handlers and components are rebound automatically, i.e., Material for MkDocs now behaves like a Single Page Application. Now, the search index survives navigation, which is especially useful for large documentation sites.

Anchor tracking

8.0.0 · Feature flag · Experimental

When anchor tracking is enabled, the URL in the address bar is automatically updated with the active anchor as highlighted in the table of contents. Add the following lines to mkdocs.yml:

    - navigation.tracking

1.1.0 · Feature flag

When tabs are enabled, top-level sections are rendered in a menu layer below the header for viewports above 1220px, but remain as-is on mobile.1 Add the following lines to mkdocs.yml:

    - navigation.tabs

navigation.tabs enabled

navigation.tabs disabled

7.3.0 · Feature flag · Experimental

When sticky tabs are enabled, navigation tabs will lock below the header and always remain visible when scrolling down. Just add the following two feature flags to mkdocs.yml:

    - navigation.tabs
    - navigation.tabs.sticky

navigation.tabs.sticky enabled

navigation.tabs.sticky disabled

6.2.0 · Feature flag

When sections are enabled, top-level sections are rendered as groups in the sidebar for viewports above 1220px, but remain as-is on mobile. Add the following lines to mkdocs.yml:

    - navigation.sections

navigation.sections enabled

navigation.sections disabled

Both feature flags, navigation.tabs and navigation.sections, can be combined with each other. If both feature flags are enabled, sections are rendered for level 2 navigation items.

6.2.0 · Feature flag

When expansion is enabled, the left sidebar will expand all collapsible subsections by default, so the user doesn't have to open subsections manually. Add the following lines to mkdocs.yml:

    - navigation.expand

navigation.expand enabled

navigation.expand disabled

Section index pages

7.3.0 · Feature flag · Experimental

When section index pages are enabled, documents can be directly attached to sections, which is particularly useful for providing overview pages. Add the following lines to mkdocs.yml:

    - navigation.indexes

navigation.indexes enabled

navigation.indexes disabled

In order to link a page to a section, create a new document with the name in the respective folder, and add it to the beginning of your navigation section:

  - Section:
    - section/
    - Page 1: section/
    - Page n: section/

This feature flag is not compatible with toc.integrate.

Integrated table of contents

6.2.0 · Feature flag

When navigation integration for the table of contents is enabled, it is always rendered as part of the navigation sidebar on the left. Add the following lines to mkdocs.yml:

    - toc.integrate

toc.integrate enabled

toc.integrate disabled

This feature flag is not compatible with navigation.indexes.

Back-to-top button

7.1.0 · Feature flag

A back-to-top button can be shown when the user, after scrolling down, starts to scroll up again. It's rendered centered and just below the header. Add the following lines to mkdocs.yml:



Hiding the sidebars

When Metadata is enabled, the navigation and/or table of contents sidebars can be hidden for a document with custom front matter. Add the following lines at the top of a Markdown file:

  - navigation
  - toc

# Document title

hide.navigation enabled

hide.toc enabled

hide.* enabled


Keyboard shortcuts

Material for MkDocs includes several keyboard shortcuts that make it possible to navigate your project documentation via keyboard. There're two modes:


This mode is active when the search is focused. It provides several key bindings to make search accessible and navigable via keyboard:

  • Down , Up : select next / previous result
  • Esc , Tab : close search dialog
  • Enter : follow selected result

This mode is active when search is not focussed and when there's no other focussed element that is susceptible to keyboard input. The following keys are bound:

  • F , S , / : open search dialog
  • P , , : go to previous page
  • N , . : go to next page

Let's say you want to bind some action to the X key. By using additional JavaScript, you can subscribe to the keyboard$ observable and attach your custom event listener:

keyboard$.subscribe(function(key) {
  if (key.mode === "global" && key.type === "x") {
    /* Add custom keyboard handler here */
    key.claim() // (1)!
  1. The call to key.claim() will execute preventDefault() on the underlying event, so the keypress will not propagate further and touch other event listeners.
  - javascripts/shortcuts.js

Content area width

The width of the content area is set so the length of each line doesn't exceed 80-100 characters, depending on the width of the characters. While this is a reasonable default, as longer lines tend to be harder to read, it may be desirable to increase the overall width of the content area, or even make it stretch to the entire available space.

This can easily be achieved with an additional style sheet and a few lines of CSS:

.md-grid {
  max-width: 1440px; /* (1)! */
  1. If you want the content area to always stretch to the available screen space, reset max-width with the following CSS:

    .md-grid {
      max-width: initial;
  - stylesheets/extra.css

  1. Prior to 6.2.0, navigation tabs had a slightly different behavior. All top-level pages (i.e. all top-level entries directly refefring to a *.md file) defined inside the nav entry of mkdocs.yml were grouped under the first tab which received the title of the first page. This made it impossible to include a top-level page (or external link) as a tab item, as was reported in #1884 and #2072. From 6.2.0 on, navigation tabs include all top-level pages and sections. 

Back to top