Word & Character Counter
Words, characters, sentences and reading time, live as you type.
Text & Writing
Live split-pane Markdown preview with HTML export.
| You write | You get |
|---|---|
# Heading | A level-1 heading |
**bold** | bold |
*italic* | italic |
[text](url) | A link |
 | An image |
`code` | inline code |
```lang | A fenced code block |
> quote | A block quote |
- item | A bullet list |
1. item | A numbered list |
- [ ] task | An unchecked task box |
| a | b | | A table row |
--- | A horizontal rule |
GitHub-flavored Markdown, which is the de facto standard. It extends the original 2004 specification with tables, fenced code blocks, task lists, strikethrough and automatic URL linking.
That matters because Markdown is not one language. CommonMark is the strict specification; GFM is CommonMark plus the extensions above; and individual tools add their own. A table renders on GitHub, in Obsidian and in most static site generators, and does nothing at all in a strict CommonMark renderer.
If your target is a specific platform, check its documentation for footnotes, math and mermaid diagrams in particular — those are the extensions with the least consistent support.
Yes. The rendered output is sanitized before it is displayed or exported, which removes script tags, event handler attributes and javascript: URLs.
This matters more than it sounds. Markdown permits raw HTML by design, so a document from an untrusted source can carry an XSS payload straight through a naive renderer into your page. Any system that renders user-submitted Markdown — a comment box, a wiki, a support ticket — must sanitize after rendering, not before.
The exported HTML is plain semantic markup with no inline styles, so it drops cleanly into a CMS or a templating system.
Anything that needs structure but not layout. It is plain text, so it diffs cleanly in version control, survives being emailed, and will still open in fifty years.
READMEs, technical documentation, changelogs, notes, blog drafts and issue descriptions are all better in Markdown than in a word processor, because the formatting is visible in the source and the file has no proprietary container around it.
Where it stops being the right tool is anything needing precise layout — a report with figures positioned relative to text, a document with headers and footers, or anything going to print. Markdown deliberately has no concept of a page.
Yes, GitHub-flavored table syntax with alignment markers. Tables are one of the extensions missing from strict CommonMark, so check your target platform if you are publishing elsewhere.
Export to HTML and print to PDF from your browser, which gives you control over margins and page size. A direct PDF export would have to guess at those.
It stays in the editor while the page is open and is not transmitted anywhere. Export or copy before closing the tab.
Yes, for images at a public URL. Local file paths cannot be resolved by a browser for security reasons.
Fenced code blocks render in a monospace block with the language label preserved. Full tokenized highlighting would require loading a highlighting library, which is not worth the bytes for a preview.
Yes. Script tags, event handlers and javascript: URLs are stripped from the rendered output and the export.
Yes, after your first visit — the renderer is part of the cached page.