When is reference style better than inline?

When prose has many long URLs — reference style keeps the body readable and groups all targets at the bottom.

How are reference IDs generated?

By default, links get sequential numbers (1, 2, 3). You can switch to slugified labels derived from the link text instead.

Are existing reference definitions reused?

Yes. When converting back to inline, definitions are inlined into the right links and any orphan definitions are dropped.

Is my document sent anywhere?

No. Conversion is local to your browser tab.

toggle inline ⇄ reference Markdown links

Convert between Markdown link styles

Switch a document between inline links ([text](url)) and reference-style links ([text][1]) with a single click — keeps prose clean and URLs at the bottom.

Reference Link Converter

Input

199 B

5 lines

Output

198 B

9 lines

Status

ready

live

Ratio

0.99×

out/in

input · markdown

output · reference style

See [the docs][1] and [the repo][2].

We also reference [the docs][1] again later.

Source: [API][3].

[1]: https://example.com/docs
[2]: https://github.com/example/repo
[3]: https://example.com/api

Quick Start

How to convert link styles

Inline → reference replaces each [text](url) with [text][n] and emits a deduped table of [n]: url at the bottom. Reference → inline does the reverse and drops the definitions.

01
Paste Markdown
Any doc with [text](url) or reference-style links.
Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.
inputGFMmarkedCommonMarklive
input · markdownmd · GFM
```
[a](u)
```
loaded · GFMGFM · ready
02
Pick direction
Inline → reference, or reference → inline.
Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.
dirsoft-breaksoptionsconfiglive
mode · options→ref · live
```
inline→ref
```
options applied · livelive
03
Convert
Inline mode dedupes URLs into a numbered table.
The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.
applypreviewscoped CSSrenderstable
out · renderedref · ready
```
[a][1]
[1]: u
```
rendered · liverendered
04
Paste back
Cleaner prose, all URLs at the bottom.
Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.
exportclipboard.md.htmlblob
✓ · exportedmd · done
```
✓ shipped
```
shipped · ready to shipsuccess

Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Use Cases

When to switch styles

Long docs read better with references; short snippets prefer inline.

Long-form posts

Move URLs out of paragraphs for readability. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

Snippet sharing

Inline form is portable to chat / messaging. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

URL reviews

Reference form gives one place to audit links. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Translation prep

Translators only see prose, not URLs. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

i18n

Dedup URLs

Same URL referenced once across the doc. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Linter friendliness

Some linters prefer one style across a repo. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly

FAQ

Frequently asked questions

Does it preserve link titles?

Inline → reference drops the optional title; reference → inline keeps the URL only. Titles can be added back manually.

Are image links touched?

No — ![alt](url) is left alone. Use the Image Extractor for image-specific work.

How are duplicate URLs handled?

When converting to reference style, identical URLs share the same numeric id.

What if a reference id has no definition?

Reference → inline leaves the original [text][id] intact so you can spot dangling refs.

Is anything uploaded?

No. Conversion runs locally in your browser.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!