Markdown Editor
Write Markdown on the left, see rendered HTML on the right — in real time. Auto-saves to your browser.
What is Markdown?
Markdown is a lightweight markup language created by John Gruber in 2004. It lets you write formatted text using plain-text syntax that is easy to read and write. Instead of clicking buttons in a rich text editor, you type simple characters like **bold** for bold or *italic* for italic.
Markdown has become the de facto standard for technical writing. GitHub uses it for README files and issues. Stack Overflow, Reddit, Discord, Slack, and many other platforms support it. Static site generators like Jekyll, Hugo, Astro, and Next.js use Markdown for content. If you write documentation, notes, blog posts, or emails — Markdown saves you time.
The syntax is intentionally minimal. A heading is just # Heading. A link is [text](url). A code block is three backticks. You learn the basics in five minutes and use them every day.
Markdown Syntax Quick Reference
| Element | Markdown Syntax | Result |
|---|---|---|
| Heading 1 | # Heading | Heading |
| Bold | **bold** | bold |
| Italic | *italic* | italic |
| Strikethrough | ~~text~~ | |
| Link | [text](url) | text |
| Image |  | Embedded image |
| Unordered list | - Item | • Item |
| Ordered list | 1. Item | 1. Item |
| Blockquote | > Quote | Quote |
| Inline code | `code` | code |
| Code block | ```lang ... ``` | Highlighted code |
| Table | | H | H | | Formatted table |
| Task list | - [x] Done | Checkbox list |
GitHub Flavored Markdown (GFM)
This editor supports GitHub Flavored Markdown — the extended Markdown specification used by GitHub. GFM adds features that standard Markdown does not include:
- Tables — create data tables with pipes and dashes:
| Header | Header | - Task lists — checkboxes for to-do items:
- [x] Doneand- [ ] Todo - Strikethrough — cross out text:
~~deleted~~ - Autolinks — URLs are automatically converted to clickable links
- Fenced code blocks — syntax-highlighted code with language tags
GFM is the most widely used Markdown variant. If you write for GitHub, GitLab, or any modern documentation platform, GFM is what you need.
Tips for Writing Better Markdown
Use headings to structure content
Start with # Title and use ## Section and ### Subsection to create a clear hierarchy. Do not skip levels.
Add blank lines between blocks
Always put a blank line before and after headings, code blocks, lists, and blockquotes. This prevents rendering issues and improves readability of the raw Markdown.
Specify the language in code blocks
Always include the language tag after the opening backticks: ```javascript. This enables syntax highlighting and makes code much easier to read.
Use descriptive link text
Instead of "click here", write [read the documentation](url). Descriptive links improve accessibility and SEO.
Keep lines reasonable
While Markdown does not enforce line length, keeping lines under 120 characters makes the raw source easier to read and produces cleaner diffs in version control.
Use task lists for actionable items
For project planning and issue tracking, task lists (- [x] Done) provide a clear visual indicator of progress.