Quotes, captions, names, wishes & practical how-tos

Markdown Basics

Markdown Cheat Sheet: Every Syntax You Need

Backlit laptop keyboard used for typing a markdown cheat sheet
Photo: Colin, CC BY-SA 4.0, via Wikimedia Commons

A Markdown cheat sheet fits on one screen: use # for headings, * or _ for emphasis, - for bullet lists, [text](url) for links and triple backticks for code. This page lists every common element with a working example so you can copy it into any editor.

Key takeaways

  • Markdown is plain text with a few symbols that convert to formatted output.
  • The core syntax (headings, emphasis, lists, links, images, code, quotes) works almost everywhere.
  • Tables, task lists and strikethrough come from extended flavors such as GitHub Flavored Markdown.
  • Always leave a blank line between blocks to avoid surprises.

What Markdown Is and Why a Cheat Sheet Helps

Markdown was created by John Gruber in 2004 as a way to write for the web in plain text. You type simple symbols and a converter turns them into HTML or another format. Because the source stays readable, it is popular for README files, notes, documentation and blogs.

The catch is that several “flavors” exist, so a few features differ between tools. This markdown cheat sheet sticks to the widely supported core and marks the extras. If you plan to move text between apps, our guide to converting Markdown to Google Docs shows how the syntax behaves after conversion.

Person writing notes in a notebook next to a laptop, using a markdown cheat sheet
Photo: Shixart1985, CC BY 2.0, via Wikimedia Commons (source)

Markdown Cheat Sheet: Headings and Paragraphs

Start a line with one to six hash signs followed by a space. One hash is the top-level heading, six is the smallest.

# Heading 1
## Heading 2
### Heading 3

A paragraph is simply text separated from the next block by a blank line. A single line break inside a paragraph is usually ignored; to force a break, end the line with two spaces or a backslash in tools that support it.

Emphasis, Quotes and Rules

You type You get
*italic* or _italic_ italic
**bold** or __bold__ bold
***bold italic*** bold italic
~~strikethrough~~ strikethrough (extended flavors)
> quote block quote
--- on its own line horizontal rule

Lists and Task Lists

Use -, * or + for bullets and numbers followed by a period for ordered lists. Indent child items by two to four spaces to nest them.

- Item one
  - Nested item
1. First step
2. Second step
- [ ] Open task
- [x] Finished task

The last two lines are task lists, which belong to GitHub Flavored Markdown and may show as plain text in simpler editors.

Code and text on a computer monitor, similar to a markdown source file
Photo: Markus Spiske markusspiske, CC0, via Wikimedia Commons (source)

A link is [link text](https://example.com). An image uses the same pattern with an exclamation mark in front: ![alt text](image.jpg). Always write meaningful alt text, because it helps screen readers and search engines.

For code, wrap short snippets in single backticks and longer blocks in triple backticks, optionally followed by a language name for syntax highlighting. See the dedicated article on code blocks and inline code for details.

Tables

Tables are an extended feature. Separate columns with pipes and add a divider row of hyphens under the header. Colons in the divider control alignment.

| Name | Role |
|:-----|-----:|
| Ana  | Editor |

Our guide to Markdown table syntax covers alignment and escaping pipes.

Writer at a laptop checking markdown syntax in an editor
Photo: Crew crew, CC0, via Wikimedia Commons (source)

A Quick Practice Exercise

To lock the syntax in, open any Markdown editor and rebuild a short meeting note from scratch: a heading with the date, a bullet list of attendees, a numbered list of decisions, one bold deadline, a link to the shared folder and a small table of owners. It takes about five minutes, and it touches nearly every element in this markdown cheat sheet. Once you can do it without looking, you know enough to write real documents.

If you later paste the result into another app, preview it first. Rich-text editors sometimes keep the raw symbols visible, and in that case a converter or the app’s own Markdown import is the cleaner route.

Escaping and Common Mistakes

  • Put a backslash before a symbol you want to show literally, such as \*.
  • Leave a space after # in headings; some parsers ignore #Title.
  • Insert a blank line before lists and code blocks.
  • Check your tool’s documentation, because behavior for line breaks and tables varies. The original Markdown syntax documentation and the GitHub Flavored Markdown specification are the best references.

Frequently Asked Questions

Is Markdown the same everywhere?

No. The core is shared, but extras such as tables, task lists and footnotes depend on the flavor your tool supports.

Which file extension should I use?

Most tools use .md, and .markdown also works.

Can I use HTML inside Markdown?

Many processors allow inline HTML, though some platforms remove or restrict it for security reasons.

How do I preview Markdown?

Use an editor with live preview, a browser extension, or convert the file to HTML or PDF with a tool such as Pandoc.

Do I need to memorize everything?

No. Learn headings, emphasis, lists and links first, and keep this cheat sheet handy for the rest.

Wrap-Up

Bookmark this page, copy the examples you need, and expand to tables and task lists once the basics feel natural. Syntax details can change between tools, so test a short sample in the app you use.

Written byEditorial Team

Part of the MarkdownToGoogleDocs editorial team, sharing copy-ready words and practical Markdown and Google Docs how-tos.