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.