Markdown syntax

How to Add Footnotes in Markdown
the [^1] syntax, and why they might not render

You want a footnote in Markdown, a small marker in your text that links to a note at the bottom. The syntax is two parts: a reference where the marker goes, and a definition with the actual note. Here is how to write them, what a footnote can hold, and why they sometimes show as raw [^1] text.

The footnote syntax

A footnote has two halves. The reference goes inline, where you want the little marker:

Markdown is a plain-text format[^1] that is easy to read.

The definition goes elsewhere, usually at the bottom of the file:

[^1]: It was created by John Gruber in 2004.

The renderer turns [^1] into a small numbered link and collects the note at the end. The two halves are tied together by the label between the brackets, so the 1 in the reference has to match the 1 in the definition.

Labels and what a footnote can hold

  • The label can be a word, not just a number: [^note] or [^ref1] both work. It is only an identifier; the visible marker is still numbered in order.
  • The definition can hold Markdown: bold, links, and other formatting are fine inside the note.
  • It can run several lines: indent the continuation lines under the definition to keep them part of the same footnote.

Why footnotes might not render

Footnotes are an extension, part of GitHub Flavored Markdown and several other flavors, not the core CommonMark spec. So the two usual reasons a footnote shows as a raw [^1]:

  • The tool does not support footnotes. A strict CommonMark-only renderer leaves [^1] as plain text. This is the same class of issue as Markdown not rendering in general.
  • One half is missing. A reference [^1] with no matching [^1]: definition, or a definition with no reference, has no partner to link to.

How they render in NoteLoom

NoteLoom renders footnotes in both the edit and reading views. The marker is clickable, so you can jump from the reference down to the note, and back up again. In a long note with several footnotes, that turns a wall of markers into something you can actually navigate.

And because it is all plain text, the [^1] references and definitions stay right there in your .md file, readable and portable even in a tool that does not render them.

FAQ

How do you add a footnote in Markdown?
Put a reference where you want the marker, like [^1], and a definition elsewhere, usually at the bottom: [^1]: the note text. The renderer turns the reference into a small linked number and collects the notes at the end of the document.
Are footnotes standard Markdown?
No, they are an extension. GitHub Flavored Markdown and several other flavors support them, but a strict CommonMark-only renderer shows [^1] as plain text because footnotes are not in the core spec.
Can a footnote label be a word instead of a number?
Yes. A label like [^note] or [^ref1] works; it does not have to be a number, and the label is just an identifier that ties the reference to its definition. The marker you see in the rendered text is still numbered in the order it appears.
Why is my footnote showing as [^1] text?
Either the tool does not support footnotes, or one half is missing. A reference [^1] needs a matching definition [^1]:, and a definition needs a matching reference. If one side has no partner, it will not link and may show as literal text.
Can a footnote contain links or formatting?
Yes. The definition can hold bold, links, and other Markdown, and it can span multiple lines if you indent the continuation lines under the definition. It is not limited to plain text.
Does NoteLoom render footnotes?
Yes, in both the edit and reading views. The marker is clickable, so you can jump from the reference down to the note and back, which makes long notes with several footnotes easy to move around in.

See your footnotes render and link

Open NoteLoom in Chrome / Edge / Arc, open a .md file with footnotes, and watch the markers render with a clickable jump to each note, saved straight back to the file. No install and no account.

Open NoteLoom and try it