Skip to content
TypeParser
All tools

Markdown Preview

GFM Markdown with live preview.

beats dillinger.io edge: GFM tables + task lists + read-time counter
markdown
— words · — read
Guide

About Markdown Preview

Type Markdown on the left, see GitHub-flavored HTML on the right. Tables, task lists, strikethrough, and fenced code blocks render exactly as GitHub renders them. Live word count and read-time counter sit in the header. Export to HTML or copy as raw HTML for embedding.

What Markdown gives you

A text format where the source is readable and the rendered output is structured. Headings, lists, tables, links, emphasis, code — all expressible without leaving plain ASCII. It became the default writing format for engineers because it round-trips cleanly between editors, version control, and viewers — your README on GitHub, your wiki on Notion, your prompts to an LLM, all the same syntax.

What GFM adds over plain Markdown

  • Tables — pipe-delimited
  • Task lists- [ ] and - [x]
  • Strikethrough~~text~~
  • Autolinks — bare URLs become links
  • Fenced code blocks — triple-backtick with optional language hint
  • Footnotes[^1] references

Almost every modern Markdown is GFM in practice. Our renderer matches GitHub’s behavior closely enough that a README rendered here looks the same on GitHub.

Common workflows

Drafting a README. Compose here, paste into the repository. The preview matches what GitHub will show, so no surprise on the first push.

Composing a long Slack message. Slack accepts limited Markdown — bold, italics, code. Use the preview to verify your formatting before paste.

Writing technical docs offline. No setup, no plugins. The editor handles 50 KB documents fluidly.

Converting Markdown to HTML for a custom site. Compose, copy the HTML, paste into your blog template. Skip the static site generator for one-off pages.

Why Markdown won

The format is readable as source. Other markup languages — HTML, AsciiDoc, reST — render gorgeously, but the source files take training to read. Markdown’s source survives flattening — pasted into Slack, copied to email, viewed cat-style in a terminal — and it still communicates structure. That property made it the lingua franca of technical writing.

Frequently asked questions

Which Markdown flavor is supported?
GitHub Flavored Markdown (GFM) — the dominant flavor in 2025. Includes tables, task lists, autolinking, strikethrough, fenced code blocks. Pure CommonMark works too.
Why does my code block not highlight?
We render the structure but skip syntax highlighting to keep the bundle tiny. For language-specific colorization, paste into a real Markdown previewer or GitHub Gist after composition.
How is read time computed?
Words ÷ 240 wpm (the average adult reading speed for technical text). Round up. The counter updates live as you type.
Can I export rendered HTML?
Yes — copy the rendered output as HTML or save as a file. The HTML is self-contained — no external CSS — paste it anywhere that accepts HTML.
Is my draft saved?
No persistent storage. The draft lives only in the textarea. Refresh the page and it is gone — copy out before closing.
How do I add a checkbox?
- [ ] task for unchecked, - [x] task for checked. They render as live checkboxes in the preview (read-only — clicking does not toggle since there is no source to update).

Related tools

Last updated: 2025-01-15