Inspect a Markdown document locally for heading structure, missing image text, bare links and readability problems, with a downloadable line-by-line report.
Everything runs locally in this browser: your source text is not uploaded or saved by this tool.
How it works
A deterministic browser-only inspection walks the document line by line, ignoring fenced code, then checks heading hierarchy, title count, duplicate headings, image alternative text, bare URLs, trailing whitespace and unusually long source lines.
Tips for a clean result
- Treat the score as a triage aid, not an editorial verdict
- Inspect every high-severity finding before publishing
- Preview links, images and layout in the final renderer
When this tool is useful
Run a consistent pre-publication structural check on a README, guide, documentation page or article and retain a line-referenced report for review.
The important edge case
Static syntax can identify likely problems but cannot establish truth, originality, appropriate tone, rendered accessibility or whether a destination URL currently works.
Three checks before publishing
- Resolve or consciously accept every high-severity finding
- Preview the exact destination renderer
- Complete a human fact, link and editorial review
Worked example
Select Load example to place a deliberately small, non-sensitive input in the editor. Convert it, compare every row and then alter one awkward value—such as a comma, quote or vertical bar—to see how the output is escaped. This makes the conversion behaviour visible before you use your own material.
Compatibility
Markdown tables are a common extension rather than part of every minimal Markdown implementation. Preview the result in the exact renderer—such as GitHub, a documentation platform or a static-site generator—that will publish it.