⌘ K
inline · reference · autolinks · mailto · output as list / JSON / CSV

Extract every link from Markdown

Pull every inline, reference, and autolink out of a Markdown document. Export as a URL list, JSON, or CSV for audits and link-rot checks.

Markdown → Links
Input
223 B
10 lines
Output
115 B
5 lines
Status
ready
live
Ratio
0.52×
out/in
input · markdown
output · list
https://example.com/docs
https://example.com/api
https://example.com/site
https://example.com
mailto:hi@example.com
Quick Start

How to extract Markdown links

Scans the source for every Markdown link variant — inline, reference, autolink, mailto — and emits a clean list, JSON, or CSV. No content is uploaded.

  1. 01

    Paste Markdown

    Any document with links — README, blog, docs.

    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
    [docs](u)
    loaded · GFMGFM · ready
  2. 02

    Detect every form

    Inline, reference, autolinks all captured.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    scansoft-breaksoptionsconfiglive
    scan · optionsall · live
    3 links found
    options applied · livelive
  3. 03

    Pick a format

    List of URLs, JSON pairs, or CSV with headers.

    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.

    formatpreviewscoped CSSrenderstable
    fmt · renderedjson · ready
    [{text,url}]
    rendered · liverendered
  4. 04

    Audit / pipe

    Feed to a link-rot checker, dataset, or report.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    exportclipboard.md.htmlblob
    OK · exportedaudit · done
    audited
    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.

Related toolsImage ExtractorLink GeneratorReference LinksAnchor IDsLink CheckerEditor
Use Cases

When to extract links

Auditing, migration, link-rot checks, dataset prep.

Link-rot audit

Pipe URLs to a checker like lychee or linkinator. 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

Dataset prep

JSON / CSV pairs for training or analysis. 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

SEO audits

Inspect outbound links from posts before publish. 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

Migration

Rewrite URLs when moving to a new domain. 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.

render-stable

Compliance

Verify no internal-only URLs leak in public docs. 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

Bibliographies

Build a reference list from a research note. 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

Inline [text](url), reference [text][id] + [id]: url, autolinks <https://…> and <mailto:…>. Bare URLs in prose are not captured.
Image syntax (![alt](url)) is skipped — use the Image Extractor for those.
Yes — double quotes inside fields are doubled per RFC 4180.
Document order: inline first, then reference resolutions, then autolinks.
No. Extraction runs locally in your browser.
Suggest a tool

Something missing?

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

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!