Format Markdown consistently (bullets, heading spacing, list numbering, aligned tables) and get a lint report of broken headings, missing alt text, bare URLs and unclosed code blocks.
0 words · 0 characters · 0 lines
Works in your browser. What you paste or upload is processed on your device.
Paste Markdown or open a .md file.
Pick the bullet marker and the blank-line limit, and switch list renumbering, table alignment and the heading fix on or off.
Fix errors first (they change how the file renders), then the warnings you care about.
Copy or download the formatted Markdown, or click Use as input to keep editing.
A Markdown formatter rewrites a Markdown file in one consistent style without changing what it renders, and a linter points out mistakes that make it render wrongly. This tool does both: paste Markdown and you get a formatted version plus a lint report with line numbers.
Formatting: one bullet marker throughout (-, * or +), one space after heading #s and closing #s removed, a blank line around headings, lists, tables and code blocks, numbered lists renumbered 1, 2, 3, table pipes aligned, thematic breaks written as ---, trailing spaces removed (two-space hard breaks are kept), and runs of blank lines collapsed. Code blocks and YAML front matter are left untouched. A fix for "#Heading" without a space is on by default and can be turned off.
Lint checks: headings missing the space after #, empty headings, more than one H1, skipped heading levels (H2 to H4), duplicate headings, headings ending in punctuation, images without alt text, links with no URL or no text, bare URLs, reference links with no definition, code blocks without a language, unclosed code fences, tabs used for indentation, trailing whitespace and a missing final newline. Limits: it is not a full markdownlint or Prettier run, so it doesn't reflow long lines or apply project config files.
Consistent Markdown is easier to review and diff, and small syntax slips (a missing space after #, an unclosed ``` fence) silently break how a README or docs page renders. Catching them before you commit saves a round of fixes.
Something else? Ask the team
It shouldn't. The formatter changes markers, spacing and alignment, not content. The one deliberate exception is the "#Heading" fix, which turns text that wasn't a heading into one; switch it off if that line was meant to be text.
It covers the most common rules from both, with no install. For CI, project config files and rules such as line-length limits, run markdownlint or Prettier in your repository.
CommonMark and GitHub only treat # as a heading when a space follows, so #Title renders as plain text. The tool reports it as a warning because it might be intended, like #hashtag.
No. Everything inside fenced code blocks is left exactly as it is.
Yes. Align tables pads every cell so the pipes line up, keeping the column alignment colons.
Each one opens on its own page and works straight away, with no sign-up.
Convert Markdown to HTML
Convert HTML to Markdown
Write Markdown with a live preview
Convert Markdown (.md) to Word .docx
Explore more free tools:Schema GeneratorMeta Tag GeneratorLLMs.txt GeneratorBrowse all free tools
Markdown Formatter & Linter is one piece of the puzzle. See how ChatGPT, Gemini, Perplexity, and Google AI Overviews actually view your brand, and get a prioritised list of fixes, with a free AEO & GEO audit from AI Rank Lab.
Run a free AEO & GEO audit or View pricing.
Site audit
Paste your site. The free audit scores it for SEO, answer engines and generative engines, with the fixes.
