How to Structure an Obsidian Vault (Without Rebuilding It Every Month)

Most Obsidian vaults die the same way. Not from a bug or a lost file — from three weekends spent designing the perfect folder hierarchy, then a fourth spent rebuilding it, and by the fifth the person has stopped writing notes and started maintaining a filing system.

The uncomfortable part is that this feels productive. Reorganising a vault has all the sensations of work — decisions, progress, tidiness — and produces nothing. Here is a structure that is deliberately boring, and the reasoning for why boring is the point.

Start with four folders

Folder	What goes in it
Inbox	Anything you capture and have not sorted. Everything lands here first.
Notes	The actual thinking. Flat — no subfolders.
Daily	Daily notes, if you use them.
Files	Images, PDFs and attachments, so they stay out of the way.

That is the whole structure. The one that matters is Notes being flat.

A flat folder feels wrong to anyone who grew up with nested directories, and it is the single decision that keeps a vault alive. The moment you have subfolders, every new note comes with a question — where does this go? — and that question is friction. Enough friction and you stop capturing. A note that never got written is worse than a note in the wrong folder.

Folders also force a note to live in exactly one place, which is a poor fit for how ideas actually work. A note about pricing a freelance project is about pricing, about freelancing, and about that specific client. A folder makes you pick one. Links do not.

Let links do the organising

Instead of filing a note into a folder, link it from wherever it belongs. Make a note called Freelancing and link to it from anything freelance-related. That note becomes an index — not because you designed it as one, but because things point at it.

This is what backlinks are for, and it is the actual reason to use Obsidian over a folder of text files. A note can sit under five different topics at once without being duplicated, and the structure grows out of what you write rather than being decided in advance by someone who did not yet know what they would write.

Practical version: when you finish a note, ask “what would I have been thinking about when I want this again?” Link it from there. That is the entire filing system.

Tags, and why fewer is better

Tags are useful for state, not topic. Topic is what links are for.

• Good tags: #todo, #draft, #reference, #someday — things that change over a note’s life and that you might want to filter on.
• Bad tags: #productivity, #work, #ideas — topics. These duplicate what a link already does, and they multiply. You will end up with #productivity, #productivity-tools and #Productivity, all slightly different, none of them findable.

If your tag list has run away already, Tag Wrangler will let you merge and rename in bulk rather than editing files one at a time. We covered it, and when to skip it, in the plugin guide.

Naming notes

Name a note the way you would say it out loud when looking for it. “Why the vault got slow” beats “obsidian-performance-2026-v2”, because in six months you will search for the first and not remember the second.

• No dates in titles unless the note is genuinely about a date. The file already knows when it was made.
• No numbering systems unless you have a specific reason. Prefixes like 01.02.03 are a folder hierarchy wearing a disguise.
• Full sentences are fine, and often better than keywords.
• Be consistent about capitals. Obsidian will treat differently-cased links as different notes, which produces phantom empty notes you did not mean to create.

When to add structure — and when not to

Add structure when a real problem appears, never in anticipation of one.

• You cannot find things → make an index note for that area and link to it. Do not make a folder.
• Your Inbox has 200 items → the problem is that you never process it, not that you need more folders. Fifteen minutes a week clears it.
• You keep writing the same note twice → search before creating. This is a habit, not a structure problem.
• Genuinely separate domains — work and a novel, say — → a second vault, not a subfolder.

The general test: if the change makes future notes easier to write, do it. If it only makes the current vault look tidier, skip it. Tidiness is not a feature of a notes system; recall is.

The one thing that actually matters

Your notes are plain markdown files sitting in a folder on your disk. That is Obsidian’s real advantage over every competitor — not the graph, not the plugins. Whatever structure you choose, the files survive the app.

Which means the cost of getting the structure wrong is much lower than it feels. You can reorganise later, with search and replace, on files you own. So stop designing and start writing — the vault will tell you what it needs after about a hundred notes, and it will tell you something you could not have guessed on day one.

If you are still choosing a tool, Notion vs Obsidian covers the trade-off, and the sync options are compared here — including the free ones.