Obsidian Folder Structure: PARA and 4 Layouts Compared
November 11, 2026 · 12 min read
Obsidian Folder Structure: PARA and 4 Other Vault Layouts Compared
A good obsidian folder structure answers one question per note, such as its status or its type, and leaves everything else to links and tags. This guide compares five layouts on one table: PARA, Johnny.Decimal, ACE, type-based and a flat Inbox plus Archive vault. Then it wires your pick into Obsidian's folder settings.
How Should You Organize an Obsidian Vault? Folders, Links or Both
An Obsidian vault is just a folder on your computer. The Obsidian help on data storage describes notes as plain-text Markdown files inside that folder and its subfolders. So the folders you see in the file explorer are real folders on disk, and your Obsidian folder structure is your file system layout too. That's also why a vault feels different from apps that keep notes in a database, a split our Markdown note-taking app comparison covers.
That has one hard consequence. A note lives in exactly one folder, but it can carry as many links and tags as you like. Folders are therefore good at answering a single question about a note, and bad at answering several.
Pick that question first:
- Status: is this active, ongoing, reference or finished? (PARA)
- Address: what number does this live at? (Johnny.Decimal)
- Type: is this a meeting, a journal entry or a reference? (type-based)
- Nothing: let search and links do all the work (flat)
Links and tags handle the rest. If you need the link syntax itself, our Obsidian Markdown cheat sheet covers wikilinks, embeds and tags. Some people also add Maps of Content, which are ordinary notes that collect links on one theme. They're a community habit, not a folder.
What Is a Good Obsidian Folder Structure? Five Layouts Compared
There's no single best layout. Each one sorts notes by a different property, and each breaks in a predictable place. This table puts them side by side so you can match one to how you actually look for notes.
| Layout | Top-level folders | Sorts notes by | Best for | Weak spot |
|---|---|---|---|---|
| PARA | Projects, Areas, Resources, Archive (plus an Inbox) | How active the work is | People juggling several projects with deadlines | Notes must move when a project ends |
| Johnny.Decimal | Numbered ranges like 10-19, 20-29 | A fixed numeric address | Large vaults, and people who remember numbers | Heavy setup for a vault of 200 notes |
| ACE | Atlas, Calendar, Efforts | Knowledge, time, or current work | Writers and researchers mixing ideas with journals | Atlas grows into a junk drawer without links |
| Type-based | Notes, Journal, Meetings, References, Output | What kind of note it is | Steady routines like meetings and logs | Says nothing about which notes still matter |
| Flat | Inbox, Archive, Attachments | Almost nothing | Heavy linkers and search-first users | The root gets crowded fast |
We prefer something close to the flat end: five or fewer top-level folders, at most one level of subfolders, and links for every other relationship. Every extra level is one more filing decision, and a vault you have to think about before typing is a vault you stop opening.
A PARA Folder Structure in Obsidian
PARA comes from Tiago Forte. In his PARA article, Projects are short-term efforts with a goal and Areas need ongoing attention. Resources are topics you're interested in, and Archives hold anything from the other three that's gone inactive. That's all the theory you need for a vault.
In Obsidian, a para folder structure looks like this:
Vault/
├── 0 Inbox/
├── 1 Projects/
│ ├── Kitchen renovation/
│ └── Q1 newsletter/
├── 2 Areas/
├── 3 Resources/
├── 4 Archive/
├── _Attachments/
└── _Templates/
The leading digits keep the inbox and the four PARA folders in a fixed order when the file explorer sorts by file name. The underscore folders are plumbing: they hold images and templates, not notes you file by hand. Give a project its own subfolder only when it has more than a handful of notes.
The Obsidian-specific part is what happens at the end of a project. You drag 1 Projects/Kitchen renovation onto 4 Archive in Obsidian's file explorer, or right-click it and choose Move folder to.... Doing that inside the app matters, as the restructuring section below explains. Areas rarely move, and Resources slide into the archive only once they go stale.
Johnny.Decimal in an Obsidian Vault
Johnny.Decimal gives every item a numeric address. Areas are ranges such as 10-19, categories inside them are two-digit numbers such as 11, and IDs look like 11.01. The system caps you at 10 areas, 10 categories per area and 100 IDs per category, so no folder ever holds an endless list.
Vault/
├── 10-19 Life admin/
│ ├── 11 Me/
│ │ └── 11.01 Passport and visas.md
│ └── 12 House/
│ └── 12.01 Lease and deposit.md
├── 20-29 Work/
│ ├── 21 Clients/
│ └── 22 Writing/
└── 30-39 Learning/
└── 31 Courses/
In a vault, the ID level usually works best as a single note rather than another folder. That keeps the tree three levels deep at most.
The catch is that the numbers live in file and folder names. They show up in wikilinks to those notes and in the quick switcher, so you'll type 11.01 a lot. That's a strength if you search by number and a chore if you don't. For a small personal vault, the setup cost usually outweighs the benefit.
Type-Based, ACE and Flat Vaults: Sort by Kind, Time or Barely at All
A type-based vault files notes by what they are. Meetings, journal entries and reading notes pile up fast, and each one is easy to classify the moment you create it.
Vault/
├── 01 Notes/
├── 02 Journal/
├── 03 Meetings/
├── 04 References/
├── 05 Output/
└── 99 Templates/
The layout is honest about what it can't do: a folder called 03 Meetings says nothing about which meetings still matter. Pair it with a status tag or property if you need that.
ACE is a community framework with three top-level folders. As it's usually described, Atlas holds ideas and reference knowledge, Calendar holds anything tied to a date (daily notes, meetings, logs), and Efforts holds the work you're doing now. It sits between PARA and type-based: one folder by time, one by activity, one for everything you know.
The flat vault keeps only an Inbox, an Archive and an Attachments folder, with every other note at the root. You find things with search, the quick switcher and links. It's the least maintenance and the hardest to browse, so it suits people who rarely open the file explorer at all.
Point Obsidian's Settings at Your Folders
A layout that isn't wired into Obsidian's settings decays within weeks, because new notes and pasted images land wherever the defaults put them. Five settings do the wiring. The names below match the Obsidian settings reference.
- Settings > Files and links > Default location for new notes. Choose In the folder specified below and enter your inbox, such as
0 Inbox. The other options are Vault folder and Same folder as current file. - Default location for new attachments, on the same screen. The options are Vault folder, In the folder specified below, Same folder as current file and In subfolder under current folder. We'd pick a single folder like
_Attachments, which keeps images out of your note folders entirely. - Excluded files, under Advanced on the same screen. Excluded paths are hidden in Search, Graph view and Unlinked mentions, and they're less prominent in the quick switcher and link suggestions. Excluding
4 Archivekeeps search focused on live work. - Template folder location, in the Templates settings under Core plugins, once that plugin is on. Point it at
_Templatesso the insert-template command only lists real templates. - Daily notes > New file location, if you use that core plugin. Set it to your journal or calendar folder so daily notes don't pile up at the root.
One limitation to accept: excluding the archive also hides it from search. When you need an old note, you'll browse the folder or remove the exclusion for a moment.
How Do You Restructure an Obsidian Vault Without Breaking Links?
Changing your Obsidian folder structure later is normal. The safe rule is simple: do every rename and move inside Obsidian, never in Finder, Windows File Explorer or a terminal.
Per the settings docs, Obsidian updates internal links when you rename a file while Automatically update internal links is on, and asks first when it's off. Obsidian does refresh the vault when files change in another program, but nothing in that program rewrites your links. Links that pointed at an old name or path can end up unresolved.
A restructure that keeps links intact goes like this:
- Create the new top-level folders first, inside Obsidian.
- Move notes by dragging them in the file explorer, or right-click and choose Move file to... for one note at a time.
- Rename folders with right-click > Rename rather than in your operating system.
- Open a few notes you just moved and check the backlinks pane still lists the notes that point to them.
- Update the five settings above so new notes follow the new layout.
Folders also have a hard limit no layout fixes. A note that belongs to two projects can only sit in one folder, so the second relationship has to be a link or a tag. Community plugins like Folder Note, which shows a note describing a folder when you click it, can make folders feel richer. They don't change that one-folder rule, and our review of editing in Obsidian covers the wider plugin picture.
If you're moving notes out of Obsidian entirely, the Obsidian to Markdown converter rewrites wikilinks, embeds, callouts, highlights, comments, tags and front matter into standard Markdown. It works on one pasted or uploaded note at a time and doesn't read a whole vault.
Draw and Document Your Vault Structure
Writing your Obsidian folder structure down makes it stick, especially if someone else shares the vault. Start with a tree. Our directory tree generator turns an indented list or a list of paths into a box-drawing tree, an ASCII tree or a Markdown list. You can also pick or drop your vault folder: it reads the file paths in your browser and doesn't upload them. From a terminal, the tree command prints the same view, and our Linux directory tree guide covers its options.
Then keep a vault map note at the root. Use plain Markdown, with no wikilinks, so it reads the same in any app. A table of folders and a short checklist covers most of it. Here's one for the PARA layout above, ready to edit:
The preview renders the table and shows the task list as checkboxes. Change the folder names to match your own layout, then copy the Markdown into a note called Vault map in Obsidian, where those checkboxes become clickable. Our Obsidian Markdown table guide covers editing the table's rows once it's there.
Frequently Asked Questions
The best obsidian folder structure is the one you'll still follow in six months, so start small. Pick a layout from the table, create the folders inside Obsidian and set the new note, attachment and template locations before you file anything. Then draft your vault map in the editor to check the table renders cleanly, and paste it into your vault as its first note.