Markdown Editor with Live Preview

1. Type or paste Markdown into the left pane, or click Open to load a .md file from your computer.
2. Use the toolbar or shortcuts to format text: Ctrl/⌘+B for bold, I for italic and K for a link. Press Enter at the end of a list item to continue the list, and Tab to indent.
3. Check the result in the preview. Switch the right pane to HTML to see the generated markup.
4. Export with Save .md, Save .html, Copy HTML or Export PDF. In the print dialog, choose "Save as PDF" as the destination.

On a phone, use the Write and Preview tabs to switch between the editor and the rendered document.

These are the elements you will use most often. Everything in this table renders in the preview above, so you can paste any line into the editor to try it.

Markdown was created by John Gruber in 2004 as a plain-text format that reads naturally and converts cleanly to HTML. Because the original description left many edge cases open, CommonMark later defined a precise specification, and GitHub extended it into GitHub Flavored Markdown (GFM).

This editor follows GFM, which adds the features most developers rely on:

• Tables with optional column alignment.
• Task lists using - [ ] and - [x].
• Strikethrough with ~~double tildes~~.
• Autolinks: bare URLs such as https://example.com become links.
• Fenced code blocks with a language name for syntax highlighting.

If your Markdown renders correctly here, it will look the same on GitHub, GitLab and most static site generators. Platform-specific extras such as GitHub alerts, Mermaid diagrams or math blocks are shown as plain text or code.

Copy HTML puts the rendered markup on your clipboard, ready to paste into a CMS, a newsletter tool or a template. Save .html downloads a complete web page with simple, readable styles that you can open in any browser or attach to an email.

Export PDF opens your browser's print dialog with only the preview visible: the editor, toolbar and site navigation are hidden, and colors switch to a print-friendly light theme even if you use dark mode. Choose "Save as PDF" to produce the file. Long tables and code blocks wrap or break across pages as they would in any printed document.

• Missing blank lines. A list or code fence that starts directly under a paragraph may be swallowed into it. Leave an empty line before lists, tables, quotes and fenced code.
• No space after #. #Heading renders as plain text in most parsers; write # Heading.
• --- under a line of text. Without a blank line in between, the line above becomes a level-2 heading instead of being followed by a rule.
• Table header without a separator row. GFM tables need the | --- | row directly under the header, with the same number of columns.
• Unclosed code fences. If everything after a certain point renders as code, look for a ``` that was never closed.
• Underscores inside words. snake_case_name is safe in GFM, but some older parsers italicize it. Wrap identifiers in backticks.