Most note-taking apps give you a toolbar. Bold button, italic button, heading dropdown. You write, then you format. The two steps are separate, and the formatting is locked to that one app.
Markdown collapses both steps into one and works everywhere.
What Is Markdown?
Markdown is a plain-text formatting system. You type simple symbols alongside your text and they render as formatted output: **bold** becomes bold, # Heading becomes a large heading, - item becomes a bullet point.
The same Markdown file renders identically in GitHub, Notion, your notes app, and every major content management system. It's not tied to any application — it's just text with a small set of conventions. Learn it once and use it permanently, regardless of what tools you're using five years from now.
The 10 Elements You'll Actually Use
These cover the vast majority of real-world note-taking:
Headings — Use # for H1, ## for H2, ### for H3. The number of # symbols sets the level.
Bold and italic — **bold** renders as bold. *italic* renders as italic. ***both*** for bold italic.
Bullet lists — Start each line with - or * . Indent with two spaces to create a sub-list.
Numbered lists — Start each line with 1. . Markdown auto-numbers them correctly even if you type 1. for every item.
Links — [link text](https://example.com) renders as a clickable link. Internal links to tools on this site work the same way.
Code — Backticks for inline code: `code`. Triple backticks for a code block:
```
code here
```
Blockquotes — Start a line with > to create an indented quote block. Useful for pulling out key information.
Horizontal rule — Three dashes --- on their own line creates a divider. Useful for separating sections.
Task checkboxes — - [ ] creates an empty checkbox. - [x] creates a checked one. Many apps render these as interactive checkboxes. If you want a dedicated place for actionable items separate from your notes, the Task Manager on this site is built around the same checkbox model.
Tables — Column headers separated by |, then a row of --- separators, then data rows. Slightly verbose to write but renders cleanly.
| Name | Role |
| ----- | ----- |
| Alice | Admin |
| Bob | User |
Practice in a Live Editor
The best way to learn Markdown is to write it somewhere that renders it simultaneously. The Markdown Notes editor on this site has a split-pane view — Markdown source on the left, rendered output on the right. As you type, you see exactly what your formatting produces.
Open it and try each of the ten elements above. Ten minutes of hands-on practice will do more than twenty minutes of reading about it.
The Word Counter is useful alongside it if you're writing something with a length target — a blog post, a report, or an email with a word limit.
Your First Five Notes to Write
Starting with a blank page is the hardest part. Here are five note templates that will force you to use the most common Markdown elements:
1. Meeting notes — One ## heading per agenda item, bullet points for discussion, - [ ] checkboxes for action items. You'll use headings, lists, and task syntax.
2. Project brief — # title, ## sections for Goals, Constraints, and Open Questions. You'll practice headings and blockquotes for key decisions.
3. Book or article summary — Title, author, ## Key Ideas with bullet points, ## My Take as a blockquote. Covers the most common structures.
4. Reference note — A note with links you want to remember, using [description](url) for each. Practices link syntax.
5. Weekly review — ## What went well, ## What didn't, ## Next week with numbered lists. A structure you'll reuse every week.
Markdown Flavors: What Changes Between Apps
The core Markdown spec — headings, bold, italic, links, lists — is consistent. The extended syntax is not. If you write Markdown across multiple tools, these are the differences you will run into:
GitHub Flavored Markdown (GFM) — The most widely adopted extension of the original spec. It adds tables, task checkboxes (- [ ]), strikethrough (~~text~~), and fenced code blocks with syntax highlighting. GitHub, GitLab, and most developer tools use it.
CommonMark — A strict, unambiguous specification for the core syntax. Focuses on consistency rather than features. Most modern implementations use CommonMark as the base.
Notion — Supports most Markdown for import and basic formatting, but renders it into its own block-based format. Once content is in Notion, it is no longer a plain Markdown file.
Obsidian — Uses its own extended spec that adds wiki-style links ([[note name]]) and backlinks. Compatible with standard Markdown but the link syntax is proprietary.
Typora, iA Writer — Clean Markdown editors with live rendering. GFM-compatible with minor differences in extended syntax handling.
The practical implication: anything you write using only the 10 elements in this post will render identically across all of them. If you use extended features like tables or footnotes, test in the target app before relying on them.
When Not to Use Markdown
Markdown is the right tool for most structured writing, but not all of it.
Documents that need precise layout — Markdown has no concept of columns, page breaks, margins, or exact positioning. For anything that will be printed with specific formatting requirements, a word processor or design tool is necessary.
Content with complex tables — Markdown table syntax becomes unwieldy for anything beyond five or six columns. Spreadsheets or dedicated table tools are easier to maintain.
Collaborative documents with comments and tracked changes — Markdown files have no native support for inline comments or change tracking. Google Docs or Word is more practical for anything requiring editorial review from multiple people.
Rich media presentations — If slides, embedded video, or interactive content are the primary output, a presentation tool handles this better than Markdown.
For everything else — notes, drafts, documentation, checklists, logs, reference material — Markdown's simplicity is an advantage.
Why Plain Text Is Worth Caring About
Every proprietary note format — Evernote's ENEX, Apple Notes, Notion's export — is a format controlled by a company. If the company changes direction, sunsets a product, or paywalls a feature, your notes are affected.
Plain Markdown files are text. Text opens in any editor on any device and will continue to work indefinitely. You can search them with any tool, back them up simply, and move them between apps without a migration script.
The Markdown Notes editor stores everything in your browser's local storage — your notes never leave your device and no account is required. That is the real argument for both Markdown and browser-based tools: not that they are faster (though they are), but that the data is permanently yours.
Frequently Asked Questions
Does Markdown look the same in every app?
The core syntax — headings, bold, italic, links, lists — renders consistently across almost all Markdown editors. Extended features like tables, footnotes, and task checkboxes vary by implementation. GitHub Markdown, for example, renders tables and checkboxes. Some simpler editors do not. The Markdown Notes editor on this site supports tables and task checkboxes.
Does the Markdown Notes editor send my notes to a server?
No. Notes are stored only in your browser's local storage. Nothing is transmitted to any server, and there is no account required. The tradeoff is that notes are specific to the browser and device where you write them.
How is Markdown different from a word processor like Word or Google Docs?
A word processor stores formatting as hidden metadata embedded in a binary or proprietary file format. Markdown stores formatting as readable characters in a plain text file. The practical difference: Markdown files open in anything, never break, and are trivially searchable. Word and Google Docs files require specific software and are controlled by the company that made them.
Can I add images to a Markdown note?
Yes, using the syntax: ``. This works with external URLs. Embedding local images directly into a Markdown file is not standard — most editors either do not support it or handle it with proprietary extensions.
What should I use Markdown Notes for alongside other tools?
Markdown Notes works well as a scratchpad for anything that needs formatting but is too informal for a full document — meeting notes, research notes, project briefs, checklists. For actionable tasks with due dates, the Task Manager is better suited. For tracking time across focused work sessions, pair notes with the Pomodoro Timer.
Quick Checklist
- [ ] Tried at least five of the ten syntax elements in the Markdown Notes editor
- [ ] Written at least one structured note using headings and lists
- [ ] Saved the note — it persists automatically in browser local storage
- [ ] Added a task checkbox and confirmed it renders correctly
- [ ] Started one of the five note templates above