MARKDOWN
LINK CHECKER
Extract and categorize all links from your Markdown. Identifies external links, relative paths, images, and more.
NOTE: This tool extracts and categorizes links. For actual validation (checking if URLs are accessible), use CLI tools like markdown-link-check or broken-link-checker.
HOW LINK CHECKING WORKS
WHAT IT CHECKS
- Scans all
[text](url)links in your markdown - Reports broken links (4xx, 5xx responses), redirects (3xx), and malformed URLs
LIMITATIONS
- Some sites block automated requests (return 403 or timeout)
- These are flagged as "unreachable" rather than broken
- Check manually if in doubt
TIPS
- Run before publishing
- Internal links (relative paths like
/about) are checked against the current domain - Anchor links (
#section) are not validated
WHEN TO USE THIS TOOL
BEFORE A CONTENT MIGRATION
You are moving a documentation site from Notion, Confluence, or another platform to a GitHub-backed markdown repo. Hundreds of internal links now point to the old domain or paths that no longer exist. Paste the exported markdown in here to see every URL before a single broken link goes live.
AUDITING A GITHUB README
Your project README links to docs, demo videos, CI badges, and NPM packages that were created a year ago. Packages get renamed, videos get taken down, and badge URLs change with CI providers. A quick paste here shows you which links still resolve and which return 404.
REVIEWING BLOG POSTS BEFORE PUBLISH
You drafted a technical blog post with links to Stack Overflow answers, library docs, and GitHub issues. Some of those threads get closed or moved. Paste your draft in before hitting publish to catch any dead links while they are still easy to fix.
WHAT HAPPENS UNDER THE HOOD
LINK EXTRACTION
The tool parses your markdown text and pulls out every link using the standard [text](url) syntax, including image links written as . Reference-style links ([text][ref]) and bare URLs in angle brackets are also picked up.
CATEGORIZATION
Each URL is sorted into a category: external (starts with http:// or https://), relative path (starts with / or ./), anchor (#section), or image. This gives you a quick inventory of what your document links to, so you can prioritize which ones to verify first.
NOTHING IS SENT TO A SERVER
The parsing runs entirely in your browser. Your markdown text is never uploaded anywhere. This makes it safe to use with draft content, internal docs, or anything you have not published yet.
FREQUENTLY ASKED QUESTIONS
DOES THIS ACTUALLY FETCH EACH URL TO CHECK IF IT'S LIVE?
The tool extracts and categorizes all links from your markdown, giving you a full list to review. For live HTTP status checking (whether a URL returns 200 or 404), you would need a server-side tool or a CLI like markdown-link-check. This tool focuses on extraction and categorization so you can audit structure and spot obvious issues fast.
WHAT LINK FORMATS ARE SUPPORTED?
Standard inline links [text](url), image links , reference-style links [text][id], and autolinks in angle brackets <https://example.com> are all detected. Bare URLs without any markdown syntax may not be picked up unless they are in autolink format.
CAN I CHECK LINKS IN A LARGE DOCUMENT?
Yes. Paste as much markdown as you need. There is no character limit enforced in the tool. Very large documents with thousands of links may take a moment to process, but the parsing is fast since it runs locally in your browser.
HOW IS THIS DIFFERENT FROM RUNNING MARKDOWN-LINK-CHECK IN A CI PIPELINE?
A CI pipeline tool like markdown-link-check runs HTTP requests against every URL on each commit, which catches broken links in production but adds latency to your build. This tool is for quick, ad-hoc auditing during writing or review, with no setup, no config files, and no CI integration required. Use both: this one while drafting, the CLI in CI.