How to write and preview Markdown online
This Markdown editor shows a live preview next to your text as you type, so you can draft a README, a pull-request description, release notes or documentation and see exactly how it will look. When you're done, export the rendered document to PDF with one click using your browser's print dialog.
It supports the common GitHub-flavoured Markdown syntax — headings, emphasis, strikethrough, links, lists, blockquotes, code blocks and tables. Your text stays in your browser, and recent documents are kept in the local history panel so you don't lose a draft.
How to use the editor
- Type or paste Markdown into the editor on the left. The preview on the right updates live.
- Click the PDF button and choose "Save as PDF" in the print dialog. Turn off headers and footers in the dialog for a clean document.
- Copy your Markdown back into GitHub, GitLab, your docs site or a ticket.
Markdown syntax cheatsheet
| You type | You get |
|---|---|
# Heading 1 … ###### Heading 6 | Headings, from largest to smallest |
**bold** / *italic* | bold / italic |
~~strikethrough~~ | Struck-through text |
| Text wrapped in single backticks | Monospaced inline code within a sentence |
[link text](https://example.com) | A hyperlink |
- item or 1. item | Bulleted or numbered list |
> quoted text | Blockquote |
--- | Horizontal rule |
Fenced code blocks use three backticks, optionally followed by a language name:
```js
const answer = 42;
```Tables use pipes and a separator row of dashes:
| Tool | Runs in |
|---------|----------|
| JSON | Browser |
| Regex | Browser |Tips for a good README
- Lead with what it is and how to run it. One sentence of purpose, then install and quick-start commands in a code block.
- Use a single
#heading for the project name, then##for sections. Many renderers build a table of contents from headings. - Leave blank lines around blocks. Lists, code blocks and tables often fail to render if they directly follow a paragraph line.
- Specify the language on code fences (
bash,json) so GitHub highlights them. - Escape literal characters with a backslash when you mean them literally, e.g.
\*or\_.
Common rendering differences
Markdown has many dialects. CommonMark defines the core; GitHub Flavored Markdown (GFM) adds tables, strikethrough, task lists and autolinks; tools like MkDocs, Docusaurus and Obsidian add their own extensions. This editor implements the common core plus tables and strikethrough with a lightweight renderer, so edge cases — deeply nested lists, HTML blocks, footnotes, task-list checkboxes — may render differently from GitHub. When exact output matters, preview on the target platform before publishing.
Need to count words or change case in plain text instead? Use the text tools. To include a JSON example, format it first with the JSON formatter.
Frequently asked questions
How do I export Markdown to PDF?
Click the PDF button. Your browser's print dialog opens with the rendered preview; choose "Save as PDF" as the destination. The exact page layout depends on your browser.
Is my document saved?
Recent edits are saved in your browser's local history panel (IndexedDB) on this device only. Nothing is uploaded, so copy your Markdown somewhere permanent when you're done.
Does it support GitHub Flavored Markdown?
It supports the most common GFM features: tables, strikethrough and fenced code blocks, alongside standard headings, lists, links, emphasis and blockquotes. Less common extensions such as footnotes may not render.