MultiQC Configuration Reference
This document describes all configuration options available in MultiQC.
Introduction
MultiQC configuration can be set in several ways:
- Command line parameters - Command line flags are available for many options (run
multiqc --helpto see all available options) - Configuration files - MultiQC looks for configuration files in the following locations (in order of precedence):
<current working directory>/multiqc_config.yaml~/.multiqc_config.yaml<installation_dir>/multiqc/utils/config_defaults.yaml
- Environment variables - MultiQC checks for environment variables that match configuration options prefixed with
MULTIQC_, for example:MULTIQC_TITLE="My Report"
Configuration values are loaded in the following order of precedence (highest to lowest):
- Command line parameters
- Current working directory config file
- User home directory config file
- Environment variables
- Default configuration values
The options below can be specified in your YAML configuration files.
For boolean options, use true or false (all lowercase) in your YAML files.
If you'd rather build your config visually, the Config Wizard renders every option below as a form field with the same descriptions and defaults, and validates as you type.
Report Meta
Header text
title
Type: str
Title shown at the top of the report and used in the page title.
subtitle
Type: str
Subtitle shown under the report title. Plain text only.
intro_text
Type: str
Paragraph shown under the title. Useful for adding context about the analysis.
report_comment
Type: str
Free-text comment shown at the top of the report. HTML is allowed.
Example:
report_comment: This report was generated from the RNA-seq pipeline on 2024-08-21.
report_header_info
Type: List[Dict[str, str]]
Extra key/value pairs shown in the report header, eg. contact name, run ID, pipeline version. Each list item is a single-key dictionary.
Example:
report_header_info:
- Contact E-mail: phil.ewels@seqera.io
- Application Type: RNA-seq
- Project Type: Application
- Sequencing Platform: HiSeq 2500 High Output V4
Report generation info
show_analysis_paths
Type: bool (default: true)
Show the absolute paths of analysed directories in the report header.
show_analysis_time
Type: bool (default: true)
Show the date and time the report was generated in the header.
Report Appearance
Template
template
Type: str (default: "default")
Name of the report template. Built-in templates: default, original, simple, sections, gathered, geo, disco. Plugin packages can register additional templates via the multiqc.templates.v1 entry point.
Example:
template: default
template_dark_mode
Type: bool (default: true)
Enable the dark mode toggle in the report template.
simple_output
Type: bool (default: false)
Render a minimal HTML report without the toolbox or interactive widgets. Useful for very large reports.
Logo
custom_logo
Type: str
Path to an image to show at the top of the report, replacing the MultiQC logo.
Examples:
custom_logo: /path/to/logo.png
custom_logo: ./assets/logo.svg
custom_logo_dark
Type: str
Path to an alternative logo for dark mode. Falls back to custom_logo if unset.
Example:
custom_logo_dark: ./assets/logo_dark.svg
custom_logo_url
Type: str
URL the custom logo links to when clicked.
Example:
custom_logo_url: https://www.scilifelab.se
custom_logo_title
Type: str
Tooltip text shown when hovering over the custom logo.
Example:
custom_logo_title: Our institute name
custom_logo_width
Type: int
Logo width in pixels. Height scales proportionally.
Example:
custom_logo_width: 200
Branding
custom_favicon
Type: str
Path to a custom favicon image to show in the browser tab.
Examples:
custom_favicon: /path/to/favicon.ico
custom_favicon: ./assets/favicon.png
custom_css_files
Type: List[str]
Paths to additional CSS files to inline into the report. Useful for branding overrides.
Example:
custom_css_files:
- ./assets/custom.css
- /path/to/branding.css