Free tool · works now

Footnote Renumbering Assistant

Renumber Markdown footnotes sequentially, reorder definitions, and detect missing or orphaned references.

Runs 100% in your browser. Paste any Markdown note to renumber scattered footnote citations sequentially, organize definition blocks at the bottom, and audit missing or orphaned references.

6Citations in body
5Unique citations
6Definitions found
1Orphaned definitions
0Missing definitions
Found 1 orphaned footnote definition(s) that are never referenced: [^unused_citation].
Input Markdown with footnotesEditable
Sequential outputCleaned

Footnote mapping audit report

Shows original keys mapped to sequential identifiers
Original keyRenumbered keyCitationsDefinition statusDefinition excerpt
[^design][^1]1MatchedOusterhout and Douglis, Beating the I/O Bottleneck: A Case for Log-Structured Fi
[^legacy][^2]1MatchedGray and Reuter, Transaction Processing: Concepts and Techniques, 1992.
[^1][^3]1MatchedPatterson et al., Computer Architecture: A Quantitative Approach, 6th ed.
[^paper][^4]1MatchedRosenblum and Ousterhout, The Design and Implementation of a Log-Structured File
[^gc][^5]2MatchedBlackburn and McKinley, Immix: a mark-region garbage collector with space effici
[^unused_citation][^6]0OrphanedThis definition was added earlier but is no longer cited in the prose.

Why footnote numbering breaks during iterative drafting

Footnotes provide rigorous academic citations, contextual qualifications, and parenthetical commentary without disrupting the narrative rhythm of primary arguments. In Markdown editors such as Obsidian, VS Code, and standard CommonMark applications, footnotes are defined through reference labels such as [^1] or arbitrary descriptive slugs like [^provenance-source].

During intensive technical drafting or research synthesis, paragraphs are continuously rearranged, revised, and expanded. When a paragraph containing a citation is moved to the top of the file, its numbering immediately drifts out of chronological alignment. Furthermore, deleting a section of prose frequently leaves behind an orphaned definition block at the foot of the document, while introducing new arguments can introduce citations whose corresponding bibliographic notes were never appended.

The Footnote Renumbering Assistant solves this friction deterministically. It reads your document in reading order, identifies every unique footnote citation in its first appearance order, maps arbitrary or scattered identifiers into clean sequential numbers (or alphabetical letters), updates all inline markers, and tidies your definition catalog at the document base.

Dialect compatibility: CommonMark, GFM, and Obsidian

Markdown footnotes were introduced in early extensions such as MultiMarkdown and PHP Markdown Extra before becoming standardized in GitHub Flavored Markdown (GFM) and Obsidian:

  • GitHub Flavored Markdown (GFM): GitHub processes footnote citations strictly at render time. GFM allows arbitrary alphanumeric tags (e.g., [^alpha]), but displays rendered superscripts as incrementing numbers. Keeping your raw Markdown numbered sequentially ensures that the raw text file in version control mirrors the rendered document view.
  • Obsidian: Obsidian supports both numbered footnotes and named identifiers. Obsidian also supports inline footnotes (e.g., ^[inline footnote content]), which are kept in place while standard referenced footnotes are parsed and synchronized.
  • Pandoc and MultiMarkdown: Publishing pipelines compiling Markdown into PDF or LaTeX require strict definition parity. Unresolved footnote citations trigger compilation warnings or abort document builds entirely.

Code block protection and inline literal immunity

A frequent failure of naive regex replacers is corrupting code examples. Technical documentation routinely presents Markdown tutorials, regex explanations, or programming scripts containing caret symbols, brackets, or footnote examples inside code snippets.

Our engine implements strict lexical isolation. Before evaluating footnote patterns, the entire text stream passes through a tokenizer that isolates every fenced block (``` or ~~~) and inline code span (`...`). These segments are shielded with unique cryptographic token placeholders during transformation and restored byte-for-byte upon completion, guaranteeing that your code snippets and configuration blocks remain unaltered.

Private browser-local execution

Research files, academic manuscripts, and confidential meeting syntheses contain sensitive intellectual property. This utility executes 100% inside your local web browser tab using standard JavaScript string processing primitives. No text is ever uploaded to a remote server, no API requests are dispatched, and no external tracking libraries inspect your content.

For related local Markdown processing, explore our companion utilities: compare note revisions with our Markdown diff viewer, generate clean document outlines with the Markdown table of contents builder, convert note link systems with the Wikilink to Markdown converter, or inspect your entire repository with the vault health inspector. Browse the full collection in our browser tools catalog.

Questions

How do Markdown footnotes work across CommonMark, GFM, and Obsidian?

In modern Markdown dialects including GitHub Flavored Markdown (GFM) and Obsidian, footnotes use bracketed caret syntax. An inline citation appears in prose as [^identifier], and its corresponding definition starts on an isolated line as [^identifier]: followed by note text. The parser links the reference superscript to the definition at the bottom of the rendered page.

Why do footnote numbers get scrambled during writing and editing?

When drafting technical notes, long-form essays, or research summaries, authors frequently insert new citations or rearrange existing paragraphs. Markdown does not automatically renumber footnotes, leaving documents with out-of-order labels (such as [^3] appearing before [^1]), orphaned definitions whose citations were deleted, or missing definitions for references introduced in haste.

How does this assistant ensure footnote syntax inside code blocks is not modified?

Before scanning for footnote identifiers, the engine completely masks all fenced code blocks (delimited by triple backticks or tildes) and inline code spans (delimited by backticks). Any text matching footnote patterns inside programming code snippets, terminal commands, or documentation comments is protected and restored byte-for-byte upon export.

What is the difference between an orphaned definition and a missing definition?

An orphaned definition is a footnote note block ([^id]: text) that exists at the bottom of the document but is never cited anywhere in the prose. A missing definition is an in-body reference ([^id]) that cites a label with no matching definition block. The assistant highlights both conditions in the audit ledger.

Does this tool transmit my research notes or confidential documents over the network?

No. The entire footnote parsing, renumbering, and formatting algorithm executes locally in your web browser. No text, notes, citations, or metadata ever leave your computer or transmit to any remote server.

Want research notes that stay organized automatically?

Full Obsidian vault compatibility, clean Markdown footnotes, and private on-device meeting recording in Oyma.

tools footnote renumbering assistant downloadDownload for Mac

No account needed. Intel Mac build