Free Markdown Editor

Write and preview Markdown in a clean split-pane editor. The left pane accepts standard Markdown — headings, bold, italic, code blocks, lists, links, blockquotes, and tables. The right pane shows the rendered HTML preview in real time. Download as a .md file, copy the raw Markdown, or copy the generated HTML.

HeadingsBold & ItalicTablesCode blocksLinksLists
Free to embed on your website · No signup required
Markdown
Preview

Welcome to Markdown Editor

Write Markdown on the left and see the live preview on the right.

Features

  • Headings (# H1, ## H2, ### H3)
  • Bold, italic, strikethrough
  • inline code and fenced code blocks
  • Links and tables

Code Example

const greet = (name) => `Hello, ${name}!`;
console.log(greet('World'));

Table Example

NameRoleExperience
AliceEngineer5 years
BobDesigner3 years

Tip: Use the toolbar above to insert formatting, or write Markdown directly.

102 words · 629 charactersCommonMark Markdown · all processing in-browser
Free to embed on your website · No signup required

Frequently Asked Questions

What Markdown syntax is supported?+

Standard CommonMark: headings (#, ##, ###), bold (**text**), italic (*text*), inline code (`code`), fenced code blocks (```), unordered lists (- or *), ordered lists (1. 2. 3.), blockquotes (>), horizontal rules (---), links ([text](url)), images (![alt](url)), and tables (| col | syntax).

How do I create a table in Markdown?+

Use pipe | characters to separate columns and a row of dashes for the header separator. Example: | Name | Age | on line 1, then | --- | --- | on line 2, then data rows.

Can I use this as a GitHub README editor?+

Yes. GitHub uses CommonMark-based GFM. This editor supports all standard Markdown that works in GitHub READMEs. GFM-specific features like @mentions are displayed as plain text.

Is my document saved?+

Your Markdown is stored only in your browser's memory for the current session. Use "Download .md" to save your work before closing.

How do I add a fenced code block?+

Start a new line with three backticks (```) optionally followed by a language name (e.g., ```javascript). Write your code, then close with three backticks on a new line.

📊

Check your word count as you write

Use the Word Counter to hit ideal lengths for README files, blog posts, and documentation.

Word Counter →

Markdown Syntax Reference

Markdown was created by John Gruber in 2004 with the goal of making plain-text documents readable and converting easily to HTML. The syntax is intentionally minimal — the most common elements are taught in under five minutes.

Headings

Use one to six hash characters followed by a space: # H1, ## H2, ### H3. H1 should be used once per document for the main title. H2 and H3 are for sections and subsections. Avoid skipping levels (e.g. going from H1 directly to H3) as this confuses screen readers and hurts document structure.

Emphasis and bold

Single asterisks or underscores for italic: *italic* or _italic_. Double for bold: **bold**. Triple for bold italic: ***bold italic***. Strikethrough uses double tilde: ~~strikethrough~~. Use emphasis sparingly — if everything is bold, nothing stands out.

Links and images

Links use square brackets for the label and parentheses for the URL: [Visit Google](https://google.com). Images use the same syntax with a leading exclamation mark: ![Alt text](image.png). The alt text in images is important for accessibility — describe what the image shows, not just its file name.

Tables

Tables use pipe characters to separate columns. The second row must contain only dashes (and optional colons for alignment). Example: | Name | Age | on line 1, | --- | --- | on line 2, then data rows. Add colons to control alignment: :--- for left, :---: for center, ---: for right.

Markdown for GitHub READMEs

GitHub uses GitHub Flavored Markdown (GFM), which extends CommonMark with task lists (- [x] Done), auto-linking URLs, and syntax-highlighted code fences with language identifiers like ```javascript. This editor supports all CommonMark elements — GFM-specific extensions like @mentions render as plain text in the preview but will work correctly when pasted into GitHub. Use the Word Counter to stay concise in your README introduction.