Obsidian is a powerful knowledge base and note-taking application built on a local folder of plain-text Markdown files. Unlike cloud-based tools, Obsidian stores your notes locally, giving you full ownership and privacy of your data. It excels at bi-directional linking, creating a web of interconnected thoughts visualized through an interactive graph. The application supports an extensive plugin ecosystem, customizable themes, and advanced workflows that make it ideal for building a second brain, implementing Zettelkasten methodologies, and managing complex personal knowledge systems from daily journaling to academic research.
What This Cheat Sheet Covers
This topic spans 30 focused tables and 182 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: Vault Structure and File Organization
Everything in Obsidian lives inside a vault — a plain folder of Markdown files plus a hidden .obsidian config directory. How you arrange that folder is one of the first decisions you make, and these rows lay out the spectrum from deep nested hierarchies to nearly flat setups that lean on links and tags instead. The takeaway: folders are just one organizing tool, not the foundation.
| Concept | Example | Description |
|---|---|---|
C:\MyNotes\ (local folder) | Root directory containing all notes and .obsidian configuration folder; one vault = one complete knowledge base. | | ||
note.md with plain text | Base storage format — human-readable, future-proof, and portable across platforms without vendor lock-in. | |
Projects/, Areas/, Resources/ | Traditional hierarchical structure; useful for broad categorization but links reduce strict folder dependency. | |
All notes in root, organized by links/tags | Minimal folder hierarchy; relies on links and tags for connections rather than physical location. |