What Is Markdown? A Guide to the File Format, Pros and Cons, and Effective Note-Taking
Markdown is everywhere—in README files, documentation, note-taking apps, and research workflows. But what is Markdown exactly, and why has it become the default format for so many knowledge workers?
Markdown is a lightweight plain-text format that uses simple syntax to indicate formatting. You write in plain text, add a few characters for structure, and any Markdown-capable tool can render it as formatted output. No proprietary file formats, no lock-in, no bloat.
This guide covers what Markdown is, its pros and cons, how to use it effectively for note-taking, and how Shadow Reader supports Markdown in your reading and synthesis workflow.
What Is Markdown? The File Format Explained
Markdown was created in 2004 by John Gruber with Aaron Swartz. The goal was simple: make it easy to write readable plain text that could be converted to structurally valid HTML. The syntax is minimal and human-friendly—you can read a .md file even without a Markdown renderer.
Core Syntax at a Glance
| Element | Syntax | Result |
|---|---|---|
| Heading 1 | # Title | Large heading |
| Heading 2 | ## Section | Medium heading |
| Bold | **bold** | bold |
| Italic | *italic* | italic |
| Link | [text](url) | Clickable link |
| List | - item or 1. item | Bullet or numbered list |
| Blockquote | > quote | Indented quote block |
| Code | `inline` or ```block``` | Monospace text |
That's most of what you need. Headers create hierarchy, lists organize items, blockquotes set off quotes or callouts, and links connect ideas. The format stays readable as plain text—a # is obviously a heading, ** is obviously emphasis.
Why Plain Text Matters
Markdown files are just text. They open in any editor, survive format changes, and work across operating systems. You're not dependent on a specific app to read your notes. A .md file from 2010 will still open in 2030. That portability and future-proofing are core to Markdown's appeal.
Pros and Cons of Markdown
Pros
Portable and future-proof. Your notes are plain text. No vendor lock-in, no proprietary binary formats. You can move between Obsidian, VS Code, Notion, or a simple text editor without losing content.
Readable as source. Unlike HTML or Word's XML, Markdown is designed to be human-readable. You can skim a raw .md file and understand it without rendering.
Lightweight and fast. Markdown files are small. No embedded fonts, images, or formatting metadata. They load instantly and work well with version control (Git) for tracking changes.
Universal support. GitHub, Notion, Slack, Discord, Reddit, and most documentation tools support Markdown. Write once, use everywhere.
Focus on structure, not decoration. Markdown encourages clear hierarchy (headings, lists) instead of font sizes and colors. That structure helps with note-taking and synthesis—you organize ideas, not pixels.
Cons
No single standard. CommonMark, GitHub Flavored Markdown (GFM), and other dialects add features (tables, task lists, strikethrough) that aren't universal. A table that renders in one tool might not in another.
Limited formatting control. You can't specify exact fonts, colors, or layout. For rich documents, you need HTML or a word processor.
Tables are awkward. Markdown tables require careful alignment and are tedious to edit by hand. Many people avoid them or use a table generator.
Images need URLs. Embedding images requires a path or URL. Local images break when you move files unless you use relative paths consistently.
Learning curve for power users. Basic syntax is easy; advanced patterns (nested lists, complex tables, footnotes) can be fiddly.
How to Use Markdown Effectively for Note-Taking
1. Structure With Headers
Use #, ##, and ### to create a clear hierarchy. Your future self will thank you when searching or skimming.
# Literature Review - Climate Policy
## Economic Impacts
### Cost-benefit analysis
### Distributional effects
## Policy Recommendations
2. Use Lists for Capture
Bullet lists (- or *) are ideal for quick capture. Numbered lists (1.) work for sequences or ranked items.
- Key finding from Paper A
- Contradiction in Paper B
- Gap: no study addresses X
3. Blockquotes for Source Material
Use > for direct quotes or extracted highlights. This visually separates your words from the source.
> "The evidence suggests that policy effectiveness depends on public buy-in."
> — Paper A, p. 12
4. Links to Connect Ideas
[anchor text](url) creates links. Use them to connect notes, cite sources, or reference related documents. Many note-taking apps (Obsidian, etc.) support [[wiki-style]] links for internal connections.
5. Keep It Simple
Resist the urge to over-format. A few headers, lists, and blockquotes go a long way. Complexity (nested lists, complex tables) increases maintenance cost.
6. Adopt Conventions
Define a system and stick to it: how you name files, how you use tags (#tag), how you structure sections. Consistency makes retrieval and synthesis easier.
How Shadow Reader Supports Markdown Note-Taking
Shadow Reader is built for reading and synthesis—PDFs, web articles, and a focused writing editor. Markdown fits naturally into that workflow in several ways.
Export Annotations as Markdown
When you tag highlights, sticky notes, and markers in Shadow Reader, you can export them by tag. One of the export formats is Markdown.
- Highlights render as blockquotes
- Notes and markers include type labels
- Tags appear as
#hashtags
This lets you pull your annotated reading into a Markdown-based workflow. Export a tag like "literature-review" and you get a .md file ready to paste into Obsidian, a research doc, or a Zettelkasten system.
Export Notes Documents as Markdown
Shadow Reader's built-in editor lets you draft alongside your reading—drag highlights and sticky notes into documents, add your own synthesis, and structure your thinking. When you're done, you can export the document as Markdown.
The export preserves headings, lists, blockquotes, and embedded highlights with source attribution. You get a clean .md file you can open anywhere, version with Git, or import into another tool.
Web Articles Stored as Markdown
When you clip a web article into Shadow Reader, the extracted content is stored as Markdown. Headings, paragraphs, lists, and blockquotes from the original article are preserved in a clean, readable format. You're reading and annotating Markdown under the hood—portable and future-proof.
A Unified Reading → Markdown Pipeline
The flow looks like this:
- Read PDFs and web articles in Shadow Reader
- Annotate with highlights, sticky notes, and markers
- Tag annotations for projects or themes
- Draft in the editor, embedding highlights as you go
- Export annotations or full documents as Markdown
Your reading stays in one place; your output is Markdown you can take anywhere.
Quick Reference: Markdown Cheat Sheet
| Need | Syntax |
|---|---|
| Heading 1 | # Heading |
| Heading 2 | ## Heading |
| Bold | **text** |
| Italic | *text* |
| Link | [text](https://url.com) |
| Bullet list | - item |
| Numbered list | 1. item |
| Blockquote | > quote |
| Inline code | `code` |
| Code block | ``` on its own line |
Getting Started
Markdown is worth learning because it's the lingua franca of knowledge work. Start with headers, lists, and blockquotes. Add links and basic formatting as you go.
If you read and annotate in Shadow Reader, use the Markdown export for annotations and notes. Your highlights and synthesis become portable, structured text you can build on in any Markdown-capable tool.
Ready to try it? Start reading and annotating in Shadow Reader, then export your tagged annotations or notes as Markdown.