Obsidian Cheat Sheet

Updated 2026-05-17

Obsidian is a powerful knowledge management application that stores notes locally as plain Markdown files, creating a personal knowledge base through bidirectional linking. Unlike cloud-first note apps, Obsidian builds on your file system — your notes remain yours forever, linkable into an interconnected graph of ideas. With extensive customization through plugins, themes, and workflows (PARA, Zettelkasten, GTD), Obsidian scales from simple note-taking to sophisticated second brain systems, supporting everything from daily journaling and task management to research databases and project documentation.

What This Cheat Sheet Covers

This topic spans 15 focused tables and 168 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.

Table 1: Vault Structure and Folder OrganizationTable 2: Markdown Syntax and FormattingTable 3: Internal Linking and BacklinksTable 4: Properties, Tags, and MetadataTable 5: Core Plugins and Essential FeaturesTable 6: Community PluginsTable 7: Zettelkasten and PKM MethodsTable 8: Dataview Queries and Dynamic ContentTable 9: Canvas and Visual WorkspacesTable 10: Mobile Apps and Cross-Device SyncTable 11: Search and NavigationTable 12: Themes, CSS Snippets, and AppearanceTable 13: Callouts and Content BlocksTable 14: Advanced Markdown FeaturesTable 15: Hotkeys and Productivity Tips

Table 1: Vault Structure and Folder Organization

Organizing your vault establishes the foundation for long-term knowledge management. Whether you prefer folders, tags, or link-based navigation, Obsidian adapts to your workflow — PARA for project-action systems, Zettelkasten for atomic networked notes, or hybrid approaches combining structure with emergence.

Method	Example	Description
Flat structure with MOCs	All notes in root + index notes	• Minimal folders • organization through Maps of Content (index notes linking related topics) and rich internal linking — favored for emergent structure
PARA method	`Projects/`, `Areas/`, `Resources/`, `Archive/`	Four top-level folders for actionable projects, ongoing areas of responsibility, reference resources, and completed work — implements Tiago Forte's system
Zettelkasten structure	Atomic notes + permanent notes + indexes	• Atomic notes with unique IDs, linked through structure notes • emphasizes note connections over folder hierarchy
Folder-based hierarchy	`Work/Projects/`, `Personal/Health/`, etc.	• Traditional nested folders by topic or life area • familiar structure, easy to browse — trade-off with reduced link-based emergence
Attachment subfolder	`.obsidian/attachments/` or per-note subfolder	Dedicated folder for images, PDFs, media (configured in Settings → Files and Links → Default location for new attachments)

Table 1: Vault Structure and Folder Organization

Method	Example	Description
Flat structure with MOCs	All notes in root + index notes	• Minimal folders • organization through Maps of Content (index notes linking related topics) and rich internal linking — favored for emergent structure
PARA method	`Projects/`, `Areas/`, `Resources/`, `Archive/`	Four top-level folders for actionable projects, ongoing areas of responsibility, reference resources, and completed work — implements Tiago Forte's system
Zettelkasten structure	Atomic notes + permanent notes + indexes	• Atomic notes with unique IDs, linked through structure notes • emphasizes note connections over folder hierarchy
Folder-based hierarchy	`Work/Projects/`, `Personal/Health/`, etc.	• Traditional nested folders by topic or life area • familiar structure, easy to browse — trade-off with reduced link-based emergence
Attachment subfolder	`.obsidian/attachments/` or per-note subfolder	Dedicated folder for images, PDFs, media (configured in Settings → Files and Links → Default location for new attachments)