TL;DR
Obsidian has been around long enough that millions of people have set it up and walked away. The most common reason is rarely the software. It is the system the user built in week one that they could not maintain by month three.
A system that lasts has to be simple at the start, open to expansion as the work changes, light on rules at first, and built around the way the user's mind actually works, not around an idealised system on a YouTube channel.
This guide sets out how to set up Obsidian in 2026. Vault structure. Atomic notes in the Zettelkasten sense. Work organisation through PARA. The new Bases and Canvas features in version 1.12. The small set of plugins worth installing. Sync and backup. The traps that take down the most users.
The audience is anyone who wants Obsidian as a primary thinking tool. Academic work. Writing. Software development. Research. Daily planning. Reading time is about 16 minutes.
What Obsidian Is in 2026
Obsidian is a notes program that stores files as Markdown on the user's own machine. The company's tagline is "Sharpen your thinking." The phrase "Your thoughts are yours" captures the design.
Three properties make Obsidian stand out.
First, the files belong to the user. Every note is a Markdown file that any text editor can open. There is no vendor lock-in. If Obsidian disappears tomorrow, the user still owns and can open every note.
Second, native linking. Typing [[Note Title]] creates a two-way link automatically. Obsidian maintains backlinks and shows them everywhere. Notes linked to each other carry structure that does not need to be enforced through folders.
Third, the core plugins cover most of what most users need. Properties for metadata. Canvas for visual whiteboard work. Graph view for seeing connections across the whole vault. Bases, added in early 2026, for treating the vault as a database.
The core app is free with no caps. Paid services are Sync for cross-device sync and Publish for turning notes into a public site. Both sit near the price of a personal Notion plan.
A Vault Structure That Lasts
The number one mistake new users make is to build a deep folder hierarchy on day one, mixing real categories with imagined ones. As work changes, the folders stop matching what the user does. The user stops maintaining the system. The vault becomes a heap.
A structure that holds up over years uses six folders at the top level.
- 00 Inbox for notes that just landed, with no home yet.
- 10 Projects for work with an endpoint and a deadline.
- 20 Areas for ongoing responsibilities such as health, finance, a team.
- 30 Resources for reference material by topic.
- 40 Archive for finished projects and things kept but not used.
- 50 Atlas for Maps of Content and the indexes that hold the vault together.
The numbers force the folders into a stable order in the sidebar, instead of alphabetical, and leave room to insert new categories between 10 and 20 without renaming the rest.
The rule that matters more than the categories is "flat structure." One level of subfolders at most. The moment a third level feels tempting, that is the signal that the notes should live in the link graph instead.
Inside the Atlas folder live Maps of Content (MOCs), which work as tables of contents for large topics. An MOC for "writing software" might list links to notes on code review, refactoring, performance, and debugging, without moving those notes into a shared folder.
Write Atomic Notes
Niklas Luhmann's Zettelkasten, developed in the 1960s, is still the standard for note systems that last. The core is the atomic note. One note, one idea.
In practice, if a book teaches ten things, the right output is ten notes, not one note with ten sections. The reason emerges six months later. A search for "leadership decision under pressure" should land on the note about that idea, not a book note where the idea sits halfway down the page.
What makes an atomic note good.
First, the title is a phrase or claim that names the idea. "Deploying often lowers risk per release" works. "20240615" does not. "Deploy" alone does not. A title that names an idea is searchable and linkable later.
Second, the body is in the user's own words. Not pasted from the source. Rewriting forces the brain to process, not just store.
Third, at least one link to another note. An atomic note with no outgoing links is a note the user has not understood in context, and it will die in the vault.
Fourth, the source is captured in a Property. URL or book title. Future verification depends on it.
A useful note length is short enough to read in about fifty seconds. Longer than that is usually a sign that the note is carrying more than one idea, and that the idea should split.
Link Notes With Wikilinks and Backlinks
Obsidian's link system is the feature that makes folders not the centre of organisation. Typing [[Note Title]] anywhere creates a two-way link. The user can move from A to B, and back from B to A through the Backlinks panel.
Three habits that make the vault grow into a network rather than a heap.
Link while writing, not after. While drafting a note on "scope creep in ERP projects," if the note on "writing clear specs" comes to mind, type the link right then. Do not search. Do not check whether the note exists. If it does not, Obsidian creates a placeholder. The user now knows what to write next.
Link in three directions. Andy Matuschak's evergreen-notes practice calls for linking up (to the broader concept), sideways (to peer concepts), and down (to examples or instances). This shape gives the vault graph depth, not just density along one axis.
Use block references for citation. Obsidian supports [[Note Title^block-id]], which links to a specific paragraph. Long-form writing that pulls from earlier notes uses this often.
What to be careful of. Backlinks earn their keep when the link reflects a real relationship. Links added speculatively make the Graph view noisy and navigation slow.
Properties Replace Frontmatter
Through 2024, Obsidian carried metadata in YAML frontmatter at the top of each file. Users typed in the YAML syntax, and a missing colon or wrong indent would break parsing.
Properties is a core plugin that replaces frontmatter with a UI key-value structure that Obsidian manages. The user clicks to add a property, selects a type (text, number, date, checkbox, list, tag), and enters the value. Obsidian writes the YAML correctly in the file.
Properties recommended for every note.
created for the creation date.modified for the last edit (set to auto-update through Templater or Linter).type for the kind of note: atomic, project, area, MOC, reference.status for project notes: active, paused, done.source for reference notes: URL or book title.
Properties pay off most when paired with Bases, covered next. Bases reads Properties for filtering, sorting, and grouping, turning the vault into a queryable database.
Tags That Stay Useful
Many Obsidian guides encourage too many tags. The user follows along, spends three months building an eight-level tag hierarchy, and forgets the rules they set. The tags become noise.
Tag habits that survive.
Keep the active tag set to five to ten. More than that, the user forgets which ones exist and creates new tags for ideas already tagged. Duplicate tags pointing at the same concept accumulate.
Use tags for status or stage, not topic. #seedling, #evergreen, #fleeting from digital-garden practice work. Topic belongs in the links between notes, not in tags.
Do not nest tags more than two levels. #project/active is fine. #project/active/q2/2026 will not be remembered.
Some practitioners drop tags entirely and rely on links. That position is extreme, but the underlying point holds. If a note on "code review" already links to an MOC for "software engineering," a tag #engineering is duplicated information that requires maintenance for no extra value.
PARA as the Work Frame
PARA is Tiago Forte's organising system, set out in Building a Second Brain. The acronym is Projects, Areas, Resources, Archive. Each category has a clear purpose.
Projects. Work with an endpoint and a deadline. "Write the 2026 ERP article." "Send the proposal to client A by Friday." "Set up the CI/CD pipeline for the new project."
Areas. Ongoing responsibilities with no endpoint. "Health." "Personal finance." "Engineering team." "Client B."
Resources. Reference material by topic, potentially useful later. "Odoo customisation tricks." "TypeScript advanced patterns." "PDPA case law."
Archive. Finished projects and material kept but not active. Prevents the loss of work that might be wanted again, and keeps the active workspace clean.
The rule Forte emphasises and the Obsidian community has carried into practice is "move, do not delete." When a project finishes, move it from 10 Projects to 40 Archive. When a resource topic falls dormant, move it to Archive. Deleting loses intellectual capital. Moving keeps the workspace responsive.
Combining PARA with Zettelkasten is the dominant Obsidian practice in 2026. PARA is the frame for work. Zettelkasten is the frame for thought. The two coexist through the wiki link system, which lets a note in Resources connect to a note in Atlas without anything moving.
Daily Notes and Templates
A daily note is a file Obsidian creates automatically each day. It serves as the day's starting point, an inbox for thoughts that arrive during the day, and a log of important decisions.
A daily note template that works in practice.
# {{date:dddd, D MMMM YYYY}}
## Today's tasks
- [ ]
- [ ]
## Thoughts and notes
## People talked to
-
## Links of the day
-
Open the day by writing the tasks already in mind. Thoughts that arrive during meetings or reading go under "Thoughts and notes" in atomic form. When a thought is substantial enough, it migrates out into its own atomic note, with a link back from the daily note.
Templater, a community plugin, extends Obsidian's template engine with JavaScript support. With it, the daily note can carry forward unfinished tasks from yesterday, or insert different sections based on the day of the week.
Teams that work on rotation use Periodic Notes alongside dailies. The plugin covers daily, weekly, monthly, quarterly, and yearly notes in one system.
Bases as a Built-in Database
Bases is the core plugin Obsidian added in early 2026, and it is a paradigm shift in how the notes system relates to data.
Bases reads Properties from notes across the vault or a specified folder, and displays the result in a List, Table, or Card view. Three forms similar to a Notion database.
Examples.
Project tracker. A Base that pulls every note with type: project, shown as a Table with status, deadline, and priority columns. Edits made in the Base write straight into the file's Properties.
Book log. A Base of notes with type: book, shown as a Card view with cover image, rating, and review excerpt.
Meeting dashboard. A Base of notes with type: meeting, shown as a List ordered by date, with a filter for team.
In the mid-2026 1.12 release, Bases added drag-and-drop import, column resizing in Table view, and right-click context menus.
The point that separates Bases from a Notion database is that the underlying files remain plain Markdown. Bases is a lens onto the files. Delete the Base, and the notes are still there in full.
Canvas for Visual Thinking
Canvas is a core plugin Obsidian released in 2022, providing an infinite space for cards, links, images, and note embeds.
Strong uses of Canvas.
Mind map of a new topic. Start from a central card. Spread branches outward. Link cards by drawing connections. Each card is an atomic note that will be written up later.
Brainstorm with the whole picture in view. Use Canvas as a two-dimensional thinking surface that folders cannot offer.
Visual project plan. Lay project cards, milestone cards, and dependency cards on a single canvas. Relationships emerge that a list does not show.
Knowledge maps. For large topics with many sub-concepts, Canvas lets the user lay out the structure by hand, instead of relying on the auto-layout of the Graph view.
In 1.12, Canvas adds backlink detection for files embedded inside a canvas, and those files count as links in the Graph view. Canvas stops being an isolated space and joins the wider network of notes.
Plugins Worth Installing
The Obsidian community plugins library has more than a thousand entries. New users install too many, slowing Obsidian down and overcomplicating their workflow. Systems that last use few plugins, but the right ones.
The baseline set.
Dataview. Query Properties and tags in a SQL-like syntax. Used to build dashboards of notes filtered, sorted, and grouped by condition. Bases covers part of this work in 1.12, but Dataview's query language goes deeper.
Templater. Extends templates with JavaScript. Used for dynamic daily notes, auto-inserted dates, and snippets that adapt to context.
Periodic Notes. Manages daily, weekly, monthly, quarterly, and yearly notes in one system.
Tasks. Extends Markdown checkboxes with due dates, recurrence, priority, and Dataview-queryable structure.
Excalidraw. Hand drawing inside Obsidian. Saved as SVG and embeddable in notes. Useful for sketching ideas that words do not capture.
Iconize. Adds icons to folders and tags for visual category recognition.
Linter. Keeps Markdown formatting consistent, sets modified dates automatically, and orders YAML frontmatter.
Smart Connections or Copilot. Integrates AI for surfacing connections between notes the user has not yet seen. This is the main 2026 use of AI in Obsidian.
The recommended path is to start with the first three (Dataview, Templater, Periodic Notes), use them for a couple of months, then add others only when a real need emerges.
Sync and Backup
Obsidian stores files locally. Sync across devices and backup are the user's responsibility.
Three approaches the community uses.
Obsidian Sync. The official service, at $4 to $10 per month by tier. Keeps version history for every file. End-to-end encrypted. Works across every device, including iOS and Android. Cost is ongoing.
iCloud or OneDrive. Free if the user already has a subscription. Works well on macOS and iOS, or Windows. Conflicts can occur when files are edited on two devices before sync catches up. iCloud occasionally has file-lock issues on Mac.
Git. For developers comfortable with the command line, the Obsidian Git plugin auto-commits and pushes to a private GitHub repository. Full version control for free. Setup is steeper, and mobile support is weaker.
Whichever option is chosen, a separate backup is non-negotiable. Several Enersys clients have lost notes over a year of work because they treated sync as backup. Sync only keeps copies in step. Delete a file on one device, and every device deletes the copy. A real backup is a separate copy that does not follow changes.
The Enersys team's pattern is Obsidian Sync for daily cross-device sync, plus an rclone script that copies the vault to separate cloud storage weekly. Three months of rollback is available if needed.
AI Integration in 2026
In 2026, AI as part of a PKM workflow has moved from experimental to ordinary. The community uses AI in three patterns.
Connection finder. Plugins such as Smart Connections use embedding models to surface notes related to the one being written, without an explicit query. In a vault of thousands of notes, this opens up connections the user has forgotten.
Note expansion. AI takes an atomic note and expands it into a paragraph or draft article. Used for first drafts, not final output.
Knowledge query. Plugins like Copilot for Obsidian let the user converse with their own vault. Questions return answers grounded in the user's notes, not in the model's general knowledge.
Three cautions the community emphasises.
First, a capable AI lets the user produce more notes faster. If the notes have not passed through the user's own thinking, the vault fills with content that is not the owner's. Long term, that vault does not sharpen thinking, contrary to Obsidian's tagline.
Second, sending notes into an external AI is a privacy decision. Users with sensitive material should run a local model through Ollama rather than calling a cloud API.
Third, the embeddings AI uses to find connections work best on notes in one language. A vault that mixes Thai and English may return imperfect results.
Traps to Avoid
The errors that take down most Obsidian systems by month three.
Tool exploration crowds out writing. New plugins and other people's workflows on YouTube absorb the time meant for writing. A useful rule. Whenever a new plugin is installed, no further plugin install for two weeks. Use the new one until it is familiar.
Perfectionism on note titles. Pausing to find the perfect title loses the thought. Write the body first, name the note second.
Folders that go too deep. After three months, most users find their notes do not match the folders they set up in week one. Cut folder depth and use tags and links instead.
Replicating Notion or Roam. Some users try to make Obsidian act like the tool they came from. The result is workflows that Obsidian does not do well, ignoring what Obsidian does differently. Try a few months on Obsidian's defaults, then adjust.
Skipping backup. Sync is not backup. Worth repeating, because this is the costliest mistake.
Tag explosion. New tags every time a new note is written. Six months later, 200 tags exist and the user remembers none of them. Prune tags every quarter. Merge duplicates.
Using Obsidian as a project manager for a team. For team work that requires roles, permissions, assignments, and sprint boards, Obsidian works but not as well as a dedicated tool. Obsidian is a personal knowledge tool that suits solo work or small high-trust teams.
Closing and Next Steps
Obsidian in 2026 is a complete tool for anyone who wants to hold their own thoughts, link notes into a network, and work with their own data over a long horizon. A system that lasts is not the result of a chosen plugin or someone else's template. It comes from the user deciding to write every day, linking whenever a connection comes to mind, and accepting that the system will start simple and grow with the work.
Next steps for someone serious about starting.
First, create a vault with the 00 through 50 structure described earlier. Start with daily notes and atomic notes captured as ideas arrive. Set no more than three rules in the first month.
Second, install Dataview, Templater, and Periodic Notes. Use the daily note template above. Repeat for two or three weeks until it becomes a habit.
Third, add Bases from the 1.12 release for a project tracker, once there are at least 50 linked atomic notes in the vault.
Fourth, set up a backup separate from sync immediately, not after the first lost note.
Fifth, read Andy Matuschak's evergreen-notes garden or Tiago Forte's Building a Second Brain. Pick one. Read it through. Skip the summaries.
A good PKM system is the accumulation of small writing every day. The trap of building the perfect system before writing has caught many people. Start in the middle. Adjust as you go.
Sources
- Obsidian, official website. Tagline, core features, and Sync and Publish pricing.
- Obsidian, Changelog. Per-release feature notes including 1.12 and Bases.
- Obsidian Tips for 2026, Geeky Gadgets. Summary of Mobile 2.0, Bases, and Canvas workflows.
- 2026 Obsidian Report Card, Practical PKM. Community assessment of Obsidian in 2026.
- Obsidian PKM System Build, PARA + GTD + Zettelkasten, Tech Edu Byte. Methodology blending referenced in the PARA section.
- Para and Zettelkasten combined, Digital Garden. The philosophy of combining PARA with Zettelkasten.
- Tiago Forte, Building a Second Brain. Source of the PARA system.
- Andy Matuschak, Evergreen notes. The three-directional linking practice referenced in the wikilink section.
- Best Obsidian Plugins for 2026, Sébastien Dubois. Plugin list referenced in the plugins section.
