mkdocs-material/docs/setup/changing-the-logo-and-icons.md

template
overrides/main.html

Changing the logo and icons

When installing Material for MkDocs, you immediately get access to over 8,000 icons ready to be used for customization of specific parts of the theme and/or when writing your documentation in Markdown. Not enough? You can also add additional icons with minimal effort.

Configuration

Logo

:octicons-tag-24: 0.1.0 · :octicons-milestone-24: Default: material/library

The logo can be changed to a user-provided image (any type, incl. *.png and *.svg) located in the docs folder, or to any icon bundled with the theme. Add the following lines to mkdocs.yml:

=== ":octicons-image-16: Image"

``` yaml
theme:
  logo: assets/logo.png
```

=== ":octicons-package-16: Icon, bundled"

``` yaml
theme:
  icon:
    logo: material/library # (1)!
```

1.  Enter a few keywords to find the perfect icon using our [icon search] and
    click on the shortcode to copy it to your clipboard:

    <div class="mdx-iconsearch" data-mdx-component="iconsearch">
      <input class="md-input md-input--stretch mdx-iconsearch__input" placeholder="Search icon" data-mdx-component="iconsearch-query" value="material library" />
      <div class="mdx-iconsearch-result" data-mdx-component="iconsearch-result" data-mdx-mode="file">
        <div class="mdx-iconsearch-result__meta"></div>
        <ol class="mdx-iconsearch-result__list"></ol>
      </div>
    </div>

Normally, the logo in the header and sidebar links to the homepage of the documentation, which is the same as site_url. This behavior can be changed with the following configuration:

extra:
  homepage: https://example.com

Favicon

:octicons-tag-24: 0.1.0 · :octicons-milestone-24: Default: assets/images/favicon.png

The favicon can be changed to a path pointing to a user-provided image, which must be located in the docs folder. Add the following lines to mkdocs.yml:

theme:
  favicon: images/favicon.png

Customization

Additional icons

In order to use custom icons, extend the theme and create a new folder named .icons in the custom_dir you want to use for overrides. Next, add your *.svg icons into a subfolder of the .icons folder. Let's say you downloaded and unpacked the Bootstrap icon set, and want to add it to your project documentation. The structure of your project should look like this:

.
├─ overrides/
│  └─ .icons/
│     └─ bootstrap/
│        └─ *.svg
└─ mkdocs.yml

Then, add the following lines to mkdocs.yml:

markdown_extensions:
  - pymdownx.emoji:
      emoji_index: !!python/name:materialx.emoji.twemoji
      emoji_generator: !!python/name:materialx.emoji.to_svg
      options:
        custom_icons:
          - overrides/.icons

You can now use all :fontawesome-brands-bootstrap: Bootstrap icons anywhere in Markdown files, as well as everywhere icons can be used in mkdocs.yml. However, note that the syntaxes are slightly different:

• Using icons in configuration: take the path of the *.svg icon file starting at the .icons folder and drop the file extension, e.g. for .icons/bootstrap/envelope-paper.svg, use:

  theme:
    icon:
      logo: bootstrap/envelope-paper
  

• Using icons in Markdown files: additionally to taking the path from the .icons folder as noted above, replace all / with - and enclose the icon shortcode in two colons:

  :bootstrap-envelope-paper:
  

For further notes on icon usage, please consult the icon reference.