A Markdown note is a piece of writing with a small amount of visible structure. A line beginning with # can be a heading. Surround a phrase with ** to emphasize it. A list is still recognizable as a list before any app formats it.
If the format itself is new to you, begin with what Markdown is. This page is about what happens when you use it to keep notes over time.
That is the appeal: the source remains readable. You can draft a note in a plain-text editor, look at it in a rendered preview, or move it between tools without first decoding a proprietary document format.
The syntax and the file are different things
Markdown is a way to write structure in text. A .md file is one common container for that text. This is a complete Markdown note:
# Weekend ideas
- Walk by the water
- Read for an hour
Remember to bring **a notebook**.
The file usually contains ordinary UTF-8 text. Its extension tells software how to interpret it; the content is still text you can open directly. A notes app may also let you write Markdown while keeping notes in its own database. Writing in Markdown does not guarantee that every note is stored as a separate .md file. Check storage and export independently.
Why people keep notes this way
Markdown encourages a small, repeatable vocabulary: headings for shape, lists for action, links for context, code fences for exact text. It is useful when notes need to stay easy to read after the app, device, or workflow changes.
Portable text also fits common work outside a notes app. A README, a draft for a website, and a working note can share the same basic format. You still need to move attachments, preserve relative links, and test an export; .md alone is not a complete backup plan. The Markdown files guide walks through those details.
For project or team notes, a GitHub repository can put .md files beside code and keep a change history. It is a good fit for some writing and awkward for other writing. The GitHub notes guide gives a small starting structure and the privacy limits.
Sync is a separate decision
A folder of .md files can be synced through a file service such as iCloud Drive. Another app may keep structured note records in an app-managed CloudKit database. Both can use iCloud, but they have different file access and export behavior. You can also keep local files and copy or back them up yourself. Our iCloud guide explains the choices without treating them as interchangeable.
On iPhone and Mac, the practical questions are whether you can capture quickly, edit comfortably, find a note again, and get your writing out. A good editor should make the Markdown syntax easier to work with while preserving the underlying words.
Where Markdown is less comfortable
Markdown is deliberately modest. It is awkward for precise page layout, complex tables, tracked changes, and documents where typography is the work. Different tools also support different extensions: a task list, wiki link, or callout may render in one place and remain literal text in another. The CommonMark specification describes a shared core, not every extension a notes app might add.
Rich text may be the better choice for visual collaboration or finished documents. Plain text may be enough for a quick list. The right format is the one that lets you write now and retrieve the result later. See Markdown versus rich text for a fairer comparison.
A good first workflow
Start with a heading, a few paragraphs, and one list. Keep filenames or note titles descriptive. Add images only after deciding where the image files will live. Once you have several notes, export or copy a small sample and open it in a second tool. That exercise teaches more about portability than a promise on a feature page.
Use the syntax guide as a reference, or try Markdown live in your browser.