Markdown Link Extractor
List simple inline HTTP(S) labels and URLs
Paste simple [label](https://destination) inline links to list labels and URLs in source order. Repeated matches are kept; relative and reference-style links are not resolved.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Extract simple inline patterns such as [Guide](https://example.com/guide) into numbered label-and-URL lines. Repeated matches remain in source order. Relative links, reference definitions, optional title syntax, and nested parentheses are not fully parsed. The pattern may also match image destinations and examples inside code; review the source before using the list for a link audit.
Suggested Workflow
Production Snippets
Inline labels are retained, duplicates are retained, and relative links are skipped
text
INPUT
[Docs](https://example.com/docs)
[Docs again](https://example.com/docs)
[Local guide](/guide)
[Reference][docs]
[docs]: https://example.com/reference
OUTPUT
1. Docs -> https://example.com/docs
2. Docs again -> https://example.com/docsFrequently Asked Questions
Which Markdown syntax is supported?
A nonempty bracketed label followed immediately by a parenthesized URL starting with lowercase http:// or https://. Relative destinations, reference-style links, bare URLs, and optional link titles are not resolved.
Are repeated URLs removed?
No. Every matching label-and-URL occurrence is numbered in source order. Two labels pointing to the same URL remain separate; there is no URL-only or deduplicated export switch.
Are image links and code blocks excluded?
No. This is pattern matching rather than a Markdown syntax tree. Image destinations and text inside code can match; nested brackets or parentheses may be missed or truncated.
Can the output prove a README has no broken links?
No. The tool does not fetch destinations, resolve reference definitions, or validate redirects. Use a Markdown-aware checker for complete document coverage and test destination status separately.
Keep browsing