How to Add Footnotes in Markdown

Footnotes are the difference between a clean argument and a wall of parenthetical asides. They let you cite sources, drop in tangential detail, or qualify a claim without breaking the flow of a paragraph. The catch is that standard Markdown does not define a footnote syntax — they come from a widely adopted extension that most modern parsers support. This guide walks through adding footnotes in Markdown, the exact syntax, inline references, multi-line notes, and how the result converts to Word and PDF.

Does Standard Markdown Support Footnotes?

Strictly speaking, no. John Gruber's original Markdown specification from 2004 has no footnote construct at all. The syntax almost everyone uses today comes from the PHP Markdown Extra extension, which was later absorbed into MultiMarkdown, Pandoc Markdown, PHP Markdown, and a long list of JavaScript parsers such as markdown-it (via the markdown-it-footnote plugin).

In practice, "Markdown with footnotes" means Markdown plus the footnote extension. If you paste footnote syntax into a parser that does not support the extension, you will usually see the raw [^1] markers leak through into the rendered output.

Support across popular tools looks roughly like this:

If your target is a static-site generator, a note-taking app, or a document conversion pipeline, footnotes will generally work. If your target is a GitHub README.md, they will not, and you should fall back to plain inline links.

Markdown Footnote Syntax Explained

The markdown footnote syntax has two parts: a reference marker inside the body text, and a definition elsewhere in the document that the marker links to. The two are connected by a shared label.

The first release shipped in 2004.[^1]

[^1]: Gruber and Swartz designed the original parser over a single weekend.

A few rules worth memorizing:

• The label must start with ^ and sit inside square brackets: [^1], [^note], [^gruber2004].
• Labels are case-insensitive and may contain letters, digits, and some punctuation, but descriptive labels are easier to maintain than numbers.
• The definition can live anywhere in the document — most writers put all footnotes at the bottom so the source stays readable.
• Multiple references can point to the same footnote label, and the rendered note number is auto-managed.

The original spec is terse.[^spec] Later flavors extended it.[^spec]

[^spec]: See the original Markdown documentation by John Gruber.

Add Inline Footnote References in Markdown

For very short notes you can write the entire footnote inline, next to the text that references it, without defining a separate block. This keeps related information visually together in the source.

Markdown was designed for writers, not for machines.^[John Gruber called it "a text-to-HTML conversion tool for web writers."]

There is also a square-bracket inline form supported by some parsers:

The parser is open source.[^open]

[^open]: Source code is hosted in a public repository.

When the inline form is expanded, the rendered output matches the two-part form exactly. Choosing between them is a question of style:

• Use the two-part form for citations and longer notes.
• Use the inline form for one-off asides of a single sentence.
• Mix the two freely inside the same document — possible, but harder to read in source.

Write Multi-Line Footnotes in Markdown

Footnotes frequently need more than one line — a full citation, a block quotation, or a short paragraph of qualification. To write multi-line footnotes in Markdown, indent every continuation line by four spaces (or one tab) so the parser knows the lines still belong to the note.

The footnote extension predates GitHub Flavored Markdown.[^extra]

[^extra]: PHP Markdown Extra introduced the footnote extension in 2004.

    The extension was later adopted by MultiMarkdown and Pandoc, which
    refined the syntax for academic writing. Most modern parsers trace
    their footnote handling back to this lineage.

Inside a multi-line note you can use most block-level Markdown: paragraphs, lists, blockquotes, even fenced code blocks — as long as each line stays indented.

This claim needs a code example.[^demo]

[^demo]: The relevant snippet looks like this:

    ```bash
    pandoc input.md -o output.docx

Run it from the project root.

> Caveat: deeply nested content inside a footnote works, but every extra indentation level makes the raw Markdown harder to scan. If a note grows beyond a paragraph, consider promoting it to body text or an appendix.

## Convert Markdown Footnotes to Word and PDF

Footnotes really earn their keep when you move out of plain text and into a formatted document. Word and PDF both have first-class footnote rendering, and the right converter will turn your `[^1]` markers into real, numbered footnotes at the bottom of each page — exactly where an editor or reviewer expects them.

| Target format | Recommended path | Footnote result |
|---|---|---|
| Word `.docx` | Paste into the [Markdown to Word converter](/) | Numbered footnotes, auto-placed |
| PDF | Route through [Markdown to PDF](/markdown-to-pdf) | Footnotes rendered per page |
| HTML | Use [Markdown to HTML](/markdown-to-html) | Linked superscripts + footer list |

When you convert a Markdown file with footnotes into `.docx`, a good converter will:

- [x] Replace each `[^label]` marker with an auto-numbered superscript.
- [x] Move the definitions into Word's native footnote layer.
- [x] Renumber sequentially so you never edit a footnote number by hand.
- [ ] ~~Preserve your original labels in the output~~ — the labels are a source-file convenience and are usually discarded.

If your notes file is a pile of plain text right now, run it through [text to Markdown](/text-to-markdown) first so the footnote syntax is well-formed before conversion. Writers coming from a `.md` file they cannot open in a comfortable reader can also drop it into the [online Markdown viewer](/md-opener) to check that the footnotes render before exporting.

## Conclusion: Add Footnotes to Markdown the Right Way

Footnotes in Markdown are an extension, not a built-in, but the syntax is stable and the support is wide enough for almost any writing workflow: write a `[^label]` marker in the body, define the note anywhere in the file, and indent continuation lines by four spaces for multi-line notes. When you are ready to share the document, the [Markdown to Word converter](/) turns those markers into properly numbered Word footnotes — no manual renumbering, no copy-pasting citations into the footer by hand.