Inline Links to Footnotes
Inline Links to Footnotes finds every parenthesized absolute http/https URL matching a simple pattern, replaces it with [n], and appends [n]: URL definitions in encounter order. Despite the name, it does not parse Markdown link syntax or generate standardized footnote-extension syntax; ordinary parentheses containing URLs can be changed unexpectedly.
Runs locally — files stay on your deviceDoes it convert [label](https://example.com) correctly?
It replaces only the parenthesized URL portion, potentially leaving [label][1]; this can resemble a reference link but is produced by text matching, not a Markdown parser.
Reference links and footnotes are distinct Markdown extensions
The output [1]: URL resembles a link-reference definition. Footnote syntax varies by renderer and often uses [^1] rather than [1].
How it works
A global pattern matches parentheses containing an http/https URL without spaces or closing parentheses, assigns sequential numbers, substitutes [n], and appends definitions.
Key concepts
Renderer syntax varies
Many footnote extensions require a caret marker.
Duplicate URLs receive new numbers
No deduplication is performed.
When to use it
- Transform a controlled list of simple parenthesized URLs.
- Create numbered reference-link-style definitions.
- Draft citation-like output for manual review.
When not to use it
- Do not expect full Markdown AST handling.
- Do not use URLs containing balanced parentheses or spaces.
- Do not assume the target renderer treats [1] as a footnote.
Worked examples
Bare parenthesized URL
- Input
See (https://example.com).- Expected output
See [1]. plus [1]: https://example.com
One definition is appended.
Two occurrences
- Input
(https://a.test) and (https://a.test)- Expected output
[1] and [2] with two definitions
Duplicates are not merged.
URL with closing parenthesis
- Input
(https://example.com/a_(b))- Expected output
Potentially truncated match
Balanced parentheses are unsupported.
Common mistakes
Expecting footnote-extension syntax
The output omits ^ markers. Correction: Adapt to the target renderer.
Assuming duplicates merge
Every occurrence increments. Correction: Deduplicate manually when desired.
Using complex URLs
The pattern stops at a closing parenthesis or space. Correction: Use a URL-aware Markdown parser.
Best practices
- Test output in the destination renderer.
- Review punctuation and complex URLs.
- Use parser-based transformations for general Markdown.
Related operations and differences
Document Link Extractor
Choose Document Link Extractor when you need to extract labeled links from Markdown or HTML.; use Inline Links to Footnotes specifically for footnotes.
Document Word Statistics
Choose Document Word Statistics when you need to measure words, characters, lines and reading time.; use Inline Links to Footnotes specifically for footnotes.
HTML to Markdown Converter
Choose HTML to Markdown Converter when you need to convert common HTML elements into clean Markdown.; use Inline Links to Footnotes specifically for footnotes.
Markdown to HTML Converter
Choose Markdown to HTML Converter when you need to convert Markdown headings, emphasis, links and lists to HTML.; use Inline Links to Footnotes specifically for footnotes.
ASCII Table Generator
Choose ASCII Table Generator when you need to turn CSV rows into an aligned plain-text table.; use Inline Links to Footnotes specifically for footnotes.
CSV to Markdown Table
Choose CSV to Markdown Table when you need to turn comma-separated rows into a Markdown table.; use Inline Links to Footnotes specifically for footnotes.
Limitations and privacy
- Regex over parenthesized absolute URLs.
- No AST, deduplication, relative URLs, balanced parentheses, titles, or renderer-specific footnote syntax.
- Existing reference numbers are not detected.
Document text is transformed locally in this browser.
Frequently asked questions
Are duplicate URLs merged?
No.
Does it use [^1] syntax?
No.
Are relative URLs converted?
No.
Are complex parenthesized URLs safe?
They may be truncated.