A Markdown heading is created by placing one or more hash (#) characters before text.

The number of hash symbols determines the heading level.

# Heading 1
## Heading 2
### Heading 3
#### Heading 4
##### Heading 5
###### Heading 6

If you're completely new to Markdown, start with Markdown Basics before diving into heading structure.

Markdown supports six heading levels from H1 through H6.

Level	Syntax	Typical Use
H1	# Heading	Document title
H2	## Heading	Major sections
H3	### Heading	Subsections
H4	#### Heading	Smaller sections
H5	##### Heading	Rarely used
H6	###### Heading	Smallest heading

Each level creates a nested outline that readers and screen readers can follow. For every other syntax rule in one place, see the Markdown Syntax reference.

A typical README or documentation page might look like this:

# My Project

## Installation

### Windows

### macOS

## Usage

### Examples

## License

This structure creates a clear document hierarchy that is easy to scan.

Rendered outline

The H1 heading should usually appear only once on a page.

# Markdown Guide

Good examples

# README

# User Documentation

# API Reference

Avoid using multiple H1 headings unless your platform specifically supports it.

Use H2 headings for the main sections of your document.

## Installation

## Usage

## Features

## FAQ

Most documentation pages are primarily built using H2 sections.

Use lower heading levels when you need additional organization.

## Installation

### Windows

### Linux

### macOS

#### Ubuntu

##### Docker

###### Advanced Configuration

Only use deeper heading levels when they improve readability.

Markdown also supports Setext-style headings.

Heading Level 1
===============

Heading Level 2
---------------

Example

Markdown Guide
==============

Installation
------------

Although valid, most modern Markdown editors recommend using # headings because they are easier to read and maintain.

GitHub fully supports all heading levels.

# Repository

## Installation

## Usage

## License

GitHub also automatically generates anchor links for headings, allowing users to jump directly to sections using the table of contents.

The standard heading syntax works consistently across nearly every Markdown application.

Platform	Supported
GitHub	✅
VS Code	✅
Obsidian	✅
Notion	✅
GitLab	✅
Markdown Preview	✅

Follow these recommendations for clean documentation.

• Use only one H1 per page.
• Leave one space after the #.
• Keep headings short and descriptive.
• Maintain a logical hierarchy.
• Don't skip heading levels unnecessarily.
• Use sentence case or title case consistently.

Good

## Installation Guide

Bad

##Installation Guide

Missing space

Incorrect

##Heading

Correct

## Heading

Multiple H1 headings

Avoid this

# Project

# Installation

Instead

# Project

## Installation

Skipping levels

Instead of

# Project

#### Installation

Use

# Project

## Installation

### Requirements

Proper heading order improves accessibility and navigation for screen readers.

A recommended structure looks like this:

# Page Title

## Section

### Subsection

### Another Subsection

## Next Section

This also helps search engines understand page structure.

Heading	Best Use
H1	Page title
H2	Main content sections
H3	Subsections
H4	Detailed topics
H5	Minor divisions
H6	Rarely needed

Continue learning Markdown with these guides:

Available now

• Markdown Basics — core concepts for beginners
• Markdown Cheat Sheet — quick syntax lookup
• Markdown Syntax — complete reference with examples
• Markdown Paragraphs — blank lines, line breaks, and spacing
• Markdown Lists — ordered, unordered, nested, and task lists
• Markdown Links — inline, reference, and relative links
• Markdown Images — syntax, URLs, alt text, and GitHub paths
• Markdown Tables — syntax, alignment, and GitHub GFM

Coming soon to MDConvertHub Docs

• Markdown Code Blocks

Each guide explores one topic in greater detail with examples and best practices.