Zettelkasten Folder Structure: Keep Notes Easy to Find

A practical Zettelkasten folder structure separates incoming material, source references, and developed ideas into a few shallow folders. Use links to connect subjects instead of giving every subject its own branch. fenbs can hold the project context distilled from those notes when you want different AI assistants to continue the same work.

This is a starting layout you can adapt, not a required filing system. The test is whether you can save a thought quickly, find its source later, and follow its connections without remembering where you filed it.

How do you set up the smallest useful layout?

1. Create one collection for notes that need to link to each other. In Obsidian, that collection is a vault.
2. Add an Inbox folder for captured material, a Sources folder for references, and a Notes folder for ideas you have developed.
3. Add an Attachments folder if you save PDFs or images. Keep these supporting files separate from note titles in the main list.
4. Create a Start here note with links to a few useful starting points. Add links between individual ideas as you develop them.
5. Try the layout with existing material from one active project before moving your entire archive.

My notes/
  Start here.md
  Inbox/
    Unsorted observation.md
  Sources/
    Source - Interview transcript.md
  Notes/
    Constraints can clarify a choice.md
    Familiar language reduces explanation.md
  Attachments/
    interview-transcript.pdf

Obsidian describes a vault as a local folder↗ (opens in a new tab). You can use these names or choose labels that make sense to you. Number prefixes such as 00 or 10 are optional sorting aids; they do not make the notes more connected or more useful.

What belongs in each folder?

A source note and an idea note can discuss the same subject without being duplicates. The source note records what you read and where it came from. The idea note explains a claim you want to develop, with a reference back to that source and any limits on the claim.

Do not copy the source into every subject folder where it might apply. Give the original one clear home and link to it. If several notes depend on one interview, keeping one source record makes it easier to correct a mistaken interpretation everywhere you use it.

How do links replace a deep subject hierarchy?

An idea about explaining constraints might help with product design, teaching, and contract discussions. A folder tree forces you to pick a primary address; a link lets you reach the same idea through several questions. Use folders for a small number of storage purposes and links for those changing relationships.

In Obsidian, a note can point to another with a wikilink such as [[Constraints can clarify a choice]]. Its internal-link documentation↗ (opens in a new tab) also explains folder paths and Markdown links. Add a sentence around the link to say whether the other idea supports, contradicts, or gives an example of this one.

For a broader organization system that also covers files beyond linked notes, use the separate guide to second-brain folder structure. Keep this setup focused on the smaller job of developing and reconnecting ideas.

When should you add another folder?

Add a folder when it gives a distinct kind of file a useful home. Templates can justify a folder because you reuse them rather than read them as finished ideas. A Maps folder can hold navigation notes if you actually maintain several. Neither is necessary before you have that need.

Project folders can help when a project contains working drafts, exports, or materials that need to travel together. Keep general ideas in the shared Notes collection and link to them from the project. Finishing a project should not hide reusable ideas inside an archive you rarely open.

A task hierarchy serves a different purpose: it describes work to complete. The work breakdown structure guide covers that planning question. Your note folders do not need to mirror the task plan, and changing the plan does not require moving all the underlying research.

What should you check before moving an existing collection?

Make a separate backup, then test a small group of notes and attachments. Open a few inbound and outbound links after moving them. Check notes with identical titles especially carefully, because a short title may not make the intended destination obvious to you.

Obsidian’s data-storage documentation↗ (opens in a new tab) explains that notes are plain-text Markdown files and links are local to a vault. Avoid creating a vault inside another vault as a filing shortcut. Treat a separate vault as a separate collection, with a boundary you intend to maintain.

For supporting files, Obsidian lets you choose a default attachment location↗ (opens in a new tab). Point it at Attachments if you use the layout above, then check a newly added image or PDF. Setting a destination for future files is a separate step from reviewing files already saved elsewhere.

How do you stop the Inbox from becoming permanent storage?

Review a manageable group of incoming notes after a reading or work session. For each, decide whether to discard it, retain it as a source reference, or develop it into an idea you can explain. There is no benefit in keeping every captured fragment just because saving it was easy.

Before filing a developed note, search for a similar idea. You may need to improve an existing note rather than create a competing version. Check that you can return to the source and follow at least one useful relationship when there is one to record.

When a note changes real work, save the reviewed conclusion and next step in fenbs’s project context. That gives the assistant a deliberate starting point instead of asking it to infer current instructions from the arrangement of your files.

How to do this with fenbs

1. Create a free account and add one active project that uses your research.
2. Add a context note summarizing the findings you reviewed, with references to the original material and clear limits on what was checked.
3. Record approved choices in Decisions and rules, and add a task when a finding requires a concrete action.
4. Ask your connected assistant to read the project context, then save progress before the session ends so the next assistant knows where to begin.

fenbs does not reorganize your vault or import its contents. If all you need is a personal file layout, the folders and links above may be enough. For the broader reason to keep work available between tools, see portable AI memory and what an AI brain is, or browse the second-brain topic hub.