Paste Markdown straight out of ChatGPT or Claude and get properly formatted source back: consistent list markers, aligned tables, no stray escape characters. Then publish it as a shareable link.
Runs in your browser — nothing is uploaded until you choose to publish.
Formatting happens in your browser — nothing is uploaded until you publish.
A Markdown formatter rewrites your source so the syntax is consistent without changing a word of what it says. Bullets all use the same marker, table pipes line up, headings get the blank line around them that the spec expects, and trailing whitespace goes away. The rendered page looks the same — the source stops being painful to edit.
This formatter runs two passes, and you can switch either one off. Format is Prettier's Markdown printer, the same engine that formats Markdown in most editors. Clean is the pass Prettier does not have: it removes what a chat model leaves behind — the outer ```markdown wrapper it puts around a whole document, the citation glyphs, the zero-width characters, and backslashes in front of punctuation that never needed escaping.
Everything happens in your browser; the text is not uploaded unless you press Publish. When you do, you get a clean hosted page for the formatted document.
Paste your Markdown into the left pane, or clear the sample and drop your own in.
Leave both passes on, or switch off Clean if you want Prettier's formatting only.
Press Format Markdown. The formatted source appears on the right, with a list of every edit underneath.
Copy it, download it as a .md file, or publish it as a shareable link.
Priya writes release notes for an internal API and drafts them with ChatGPT, then pastes the result into the repo's CHANGELOG.md. Every time, the diff was noisier than the change: the model wrapped the whole answer in a ```markdown fence, alternated between * and - for bullets depending on how deep the nesting went, and wrote v2\.1\.0 and file\_name with backslashes that rendered as literal backslashes on GitHub.
Her editor's format-on-save fixed the bullets and the table pipes, but it left the fence and the backslashes alone — to a formatter they are simply valid Markdown. So every release she deleted the first and last lines by hand and ran a find-and-replace for \. that sometimes caught the ones inside code samples too.
She pasted a draft here instead. The fence came off, the backslashes in the prose went away while the ones inside the code block stayed, the mixed bullets came back as one list, and the compatibility table came back aligned. The ledger under the panes told her exactly what had been touched — four unescapes, one fence, six list markers — so she could see nothing else had been rewritten before she pasted it into the repo.
Only the syntax, never the content. It makes every bullet use the same marker, pads table cells so the pipes line up, puts a blank line around headings and lists where the spec expects one, normalises the number of # characters to the heading level you already wrote, and strips trailing whitespace. The rendered output is the same document — the source just stops fighting you in a diff.
Because the things that are wrong with it are valid Markdown. An outer ```markdown fence, a citation glyph, a zero-width space, \[note\] — a formatter has no reason to touch any of them, so it aligns your tables and leaves the rest exactly where it was. That is what the Clean pass here is for, and it is the half most formatters do not have.
No. Everything inside a fenced block or an inline code span is left byte for byte as you pasted it — a backslash there is a literal backslash and a leading * is data, not a list. The unescape rule is also deliberately cautious outside code: it never touches an escape at the start of a line, because \- and \# are how you stop a list or a heading from forming, and it never unescapes \* at all, because that is usually the model correctly protecting a literal asterisk.
Not unless you choose to publish it. The formatter runs entirely in your browser — the Markdown never leaves the page while you are formatting, copying or downloading it. Pressing Publish is the one action that sends anything to dochost, and that is what produces the shareable link.
In practice, nothing — they are two names for the same job, and this page and the Markdown beautifier run the same engine. "Format" is the word developers use for making source consistent; "beautify" is the word people use when raw Markdown is simply hard to read. Either way you get the same tidy source back.
免費帳號的連結保留 7 天。升級付費方案後，你建立的每個頁面都會永久上線。
查看方案與價格