Normalise Markdown: setext headings become #, bullets become consistent, tables line up, and fenced code and front matter are reproduced exactly.
Waiting for Markdown
Front matter and fenced code are reproduced exactly; everything else is normalised.
Formatted Markdown appears here
Consistent bullets and headings, tables lined up, and fenced code untouched.
Markdown Formatter runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Markdown has more than one spelling for most things. A heading can be # Title or Title with ===== underneath. A bullet can be -, * or +. A table's pipes can line up or not. None of it changes what renders, and all of it changes how the source reads — particularly once several people have edited the same file.
This normalises the parts with more than one spelling and leaves everything else alone. Setext headings become the # form, which survives copy-paste and reads the same at every level. Bullet markers become whatever you choose. Runs of blank lines collapse to one. Trailing whitespace goes — except the two spaces that mean a hard line break, which are load-bearing and survive. Tables get their pipes lined up.
Two things are reproduced byte for byte. Front matter, because a YAML or TOML block is not Markdown and reformatting it is a different tool's job. And fenced code, because the contents of a fence are not Markdown either: a * at the start of a line in a shell script is a glob, a # is a comment, and a | is a pipe. A formatter that treats those as a bullet, a heading and a table column has corrupted the example.
Nothing is rendered. Markdown goes in and Markdown comes out, so there is no HTML anywhere in the path and nothing that needs sanitising. If your document contains raw HTML — which Markdown permits — it passes through as the text it is.
The result is idempotent: formatting the output again returns the same text, so this will not fight with a formatter in your editor.
No. Fenced code is reproduced byte for byte, including its blank lines and indentation. A * or # or | inside a fence belongs to whatever language the fence holds, not to Markdown.
It is reproduced exactly. A YAML or TOML block is not Markdown, and normalising its spacing could change what a site generator reads out of it.
No. Trailing whitespace is trimmed everywhere except where exactly that pattern appears — two or more spaces at the end of a line with content — which Markdown reads as a hard line break. Those are normalised to exactly two and kept.
No. Markdown goes in and Markdown comes out. Nothing is rendered, which also means there is no HTML to sanitise and nothing in your document can execute.
No. Hard-wrapping prose is a matter of taste and re-wrapping someone else's document produces an enormous diff for no rendering change, so it is left alone.
Yes. Running the output through again returns the same text, so it will not oscillate with another formatter.