Obsidian Second Brain: Set Up a Vault That Lasts

November 11, 2026 · 10 min read

Obsidian Second Brain: Build a Vault You'll Keep Using

An obsidian second brain is a vault of plain Markdown notes built for fast capture and easy retrieval. It needs four things: a small folder skeleton, Maps of Content that link related notes, two or three templates, and a weekly review. This tutorial builds each one.

What an Obsidian Second Brain Needs (and What It Skips)

Obsidian stores notes as plain text Markdown files in a vault, which is just a local folder. That's the main reason to use Obsidian for a second brain: your notes outlive any app, plugin or subscription.

The second brain idea comes from Tiago Forte. Its CODE loop is Capture, Organize, Distill, Express, and its PARA system files everything under Projects, Areas, Resources and Archives. The method works in any app, so this post skips the theory and covers the Obsidian setup.

What you can skip at the start: a theme, a dozen community plugins, nested tag hierarchies and an AI assistant. In our experience, a second brain in Obsidian usually dies from too much structure, not too little.

How Do You Build a Second Brain in an Obsidian Vault? Start With Folders

Create a new vault, then add six top-level folders. The number prefixes keep them in a fixed order whenever the file explorer sorts by name.

My Vault/
├── 00 Inbox/
├── 01 Projects/
├── 02 Areas/
├── 03 Resources/
├── 04 Archive/
└── 99 System/
    ├── Templates/
    └── Attachments/

That's Forte's PARA method with two additions: an inbox for unsorted captures and a system folder for templates and files you never file by hand.

We prefer five or six top-level folders and never more than two levels deep. Deep trees force you to decide where a note lives before you've written it, and that friction kills capture. Our Obsidian folder structure comparison sets PARA beside four other layouts.

Then open Settings → Files & Links and make two changes:

  • Default location for new notes: choose In the folder specified below and pick 00 Inbox. Every quick capture now lands in one place.
  • Default location for new attachments: choose the same option and pick 99 System/Attachments. Images and PDFs stop scattering across your folders.

Maps of Content: Linking Notes by Meaning Instead of Nesting Folders

A Map of Content (MOC) is an ordinary note whose job is to link other notes on one theme. It's a community convention, not an Obsidian feature, so you don't install anything. Keep MOCs in 03 Resources, or wherever the theme naturally belongs.

# Writing MOC

## Active projects
- [[Newsletter relaunch]]
- [[Book proposal]]

## Craft
- [[Strong opening paragraphs]]
- [[Editing checklist]]

## Sources
- [[On Writing Well notes]]

In Obsidian, each [[...]] becomes a clickable internal link, and the target note shows this MOC in its Backlinks panel. Graph view draws the same connections as a cluster. For link variants such as aliases, headings and block links, see our Obsidian Markdown cheat sheet.

The rule that keeps the vault sane: folders describe a note's status, links describe its meaning. A note about pricing research sits in 01 Projects while the project runs and moves to 04 Archive afterwards. Its link from the Marketing MOC never changes.

Templates for Project Notes and MOCs

Turn on the core Templates plugin, then set its Template folder location to 99 System/Templates. To use one, run the command Templates: Insert template from the command palette and pick a file.

Templates support three variables: {{title}} for the note's name, {{date}} for today's date and {{time}} for the current time. Dates default to YYYY-MM-DD and times to HH:mm, and you can add Moment.js tokens, for example {{date:DD MMM YYYY}}. Here's a project note template:

---
type: project
status: active
area: Work
created: "{{date}}"
---

# {{title}}

## Goal
One sentence: what does done look like?

## Next actions
- [ ] 

## Notes

## Related
- [[Work MOC]]

Inserted on 11 November 2026 into a note called Website redesign, the heading becomes # Website redesign and the created property gets today's date, 2026-11-11. A MOC template is shorter: a title, two or three empty headings, and a type: moc property.

Edit template files in Source mode. The Templates docs warn that the properties panel in Live Preview can overwrite variables that aren't in quotation marks. Daily notes run through their own core plugin with a separate template setting, so treat them as a different job. If you outgrow the built-in variables, the Templater community plugin adds scripting.

A Few Properties That Make Notes Findable

Properties are the YAML block at the top of a note. You only need four to start:

type: project
status: active
area: Work
created: 2026-11-11

Each one earns its place in search. Typing [status:active] in Obsidian's search finds every live note, and [type:moc] lists your maps. For the YAML rules behind these lines, read our guide to Markdown front matter. Property types and reserved keys are in our Obsidian front matter guide.

The bigger payoff is the core Bases plugin. A base is a .base file that shows notes as rows and properties as columns, with Table, List, Cards, Kanban and Map layouts per the Bases docs. Map needs the separate Maps plugin. Filter it to type equals project, sort by status, and you have a project dashboard with no plugin to install.

Is There an Obsidian Second Brain Template Worth Starting From?

Yes, several starter vaults are free to download, and they skip the blank-page stage. The catch is that you inherit someone else's folder names, properties and plugin choices. You'll spend the first month learning their system instead of building yours.

Our view: build the skeleton yourself. The folders, one MOC and one project template above take about 15 minutes, and you'll understand every piece. Here's the project note from earlier, filled in, as standard Markdown you can edit:

Project: Website redesign

Area: Work
Status: active
Deadline: 2026-12-15

Goal

Ship the new homepage and pricing page.

Next actions

  • Draft homepage copy
  • Review wireframes with design
  • Collect analytics baseline

Key notes

Note Why it matters
Pricing research Competitor tiers
Brand voice Tone for copy

Done when

Both pages are live and linked from the Website MOC.

79 words424 characters21 lines
Markdown

The preview shows the headings, the task list as checkboxes and the table. One limitation to know: our editor's preview doesn't render [[wikilinks]], embeds, callouts or a properties block, so the demo uses plain lines instead. To turn a real Obsidian note into standard Markdown, paste it into the Obsidian to Markdown converter, which handles one note at a time.

What Is obsidian-second-brain on GitHub? Starter Vaults vs Agent Tools

An obsidian-second-brain GitHub search mostly returns AI agent tools, not starter vaults. The repo with that exact name, eugeniughelbur/obsidian-second-brain, describes itself as persistent memory for Claude Code, Codex and other AI agents. It's MIT licensed, and its README calls it a skill that runs inside those agents.

That's software, not a template. An agent tool reads and writes your notes through an assistant, which is a separate topic from this setup. Plain starter vaults exist too, usually one person's own folders and templates shared as a download. For the agent route, see our second brain AI tutorial.

Before you clone any Obsidian second brain GitHub repo, check five things:

  1. License. No license file means you have no clear right to reuse it.
  2. Last commit. A repo untouched for years may depend on plugins that have changed.
  3. Required plugins. Count the community plugins the README asks for.
  4. Template or software. A folder of .md files is safe to copy. Scripts that write to your vault are software.
  5. Scripts. Read any install script before you run it.

Community Plugins to Add After the First Month

Start with core plugins only: Templates, Backlinks, Graph view, Bases and Daily notes. Live with them for a month. Then add a community plugin only when you hit a specific wall.

To install one, Obsidian requires you to turn off Restricted mode first, then go to Settings → Community plugins → Browse. These are the ones second brain setups reach for most:

  • Dataview runs queries over notes and properties when Bases can't express what you need.
  • Templater replaces core Templates with scripted, conditional templates.
  • Tasks collects checkboxes from every note into filtered task lists with due dates.
  • Periodic Notes adds weekly, monthly and yearly notes alongside daily ones, and Calendar gives you a clickable calendar to open them.
  • Git backs up the vault to a Git repository on a schedule.

For plugins that improve writing rather than organising, and how Obsidian's editing modes compare, see our honest review of Obsidian as a Markdown editor.

A Weekly Review That Keeps the Vault Alive

Obsidian won't tidy anything for you. Without a review, the inbox fills, finished projects pile up next to live ones, and your second brain turns into a junk drawer. Block 20 minutes each week for four steps:

  1. Empty the inbox. Move each note in 00 Inbox into a PARA folder, or delete it.
  2. Close finished projects. Set status: done and drag the note into 04 Archive.
  3. Update your MOCs. Add a link to every new note worth finding again.
  4. Check for orphans. With Graph view's Orphans filter on, notes with no links show up as loose dots. Link, merge or delete them.

This routine matters more than any plugin. A plain vault you review weekly beats an elaborate one you abandon in March.

An obsidian second brain that lasts is mostly boring: six folders, a handful of MOCs, one project template, four properties and a weekly review. Build that first, use it for a month, and only then add plugins or a starter vault's ideas. When you want to draft a template or check how a note reads as standard Markdown, open the editor and paste it in.