Tags or Folders for Your Notes? The Honest Answer Is in How You Get Them Back

Stop asking whether tags or folders are better. Ask how you get a note back. Folders answer one question: where does this belong? Tags answer another: what is this about? Search answers a third: I will find it later. The right mechanism is the one that matches how your future self reaches for the note.

That reframing is not a rhetorical trick. It is the conclusion of a 2025 case study of researchers building personal knowledge bases in Obsidian: "A key finding is that participants' knowledge retrieval strategy influences how they build and maintain their content."¹ The people who organize well do not pick a winner. They let the way they retrieve decide the way they file.

This essay follows that thread to its honest end. That includes the part where both tags and folders fail you, and the part where the whole choice turns out to be reversible.

The question everyone actually asks

People phrase the debate as a contest: tags versus folders, pick a side, defend it. The instinct is reasonable, because the two feel like rivals — a folder is a place, a tag is a floating label. So the search box fills with "should I use tags or folders for my notes" and "tags vs folders Obsidian," each expecting a verdict.

The contest framing is the mistake. It treats organization as a property of the note (this note is filed correctly) when organization is really a property of the moment you need the note again. You do not retrieve a note the way you stored it. You retrieve it by whatever fragment your memory coughs up: a project, a feeling, a half-remembered phrase.

The filing question and the finding question are different questions, and only one of them matters on a deadline. That is the question the whole debate keeps skipping.

Why folders feel safe and quietly trap you

A folder gives every note exactly one home, which is calming and also the whole problem. The reassurance is real: one place to put it, one place to look. But a single home forces a single answer to "what is this about," and most notes are about more than one thing. A folder makes you choose.

A meeting note is about a project, a person, and a decision at once. The structural asymmetry was stated plainly by PKM writer Sébastien Dubois: "Tags are much more powerful than folders because you can add as many as you want to a single note, whereas a note can only ever be in a single folder."² One folder — unlimited tags.

The cost of folders is not that they are wrong. It is that they make you predict, at filing time, the one path your future self will take. You rarely guess right, so notes drift into a "misc" folder — which is where notes go to be forgotten.

What tags do that folders cannot

Tags let one note live under many lenses without copying it anywhere. That is the move folders cannot make. A note keeps its one folder while also carrying every label that describes it, so a single document can answer several "what is this about" questions instead of just one. Tags add doors — without moving walls.

Tiago Forte, who shaped the modern practice of tagging for personal knowledge, describes it as crossing the walls instead of climbing them: tags "create alternative pathways that tunnel through the walls of our siloed folders, while leaving them just as we left them."³

A note in /projects/atlas/ can also carry #decision, #budget, and #hiring. None of those are folders — all of them are doors. When you later think "where did we decide the budget," you do not need to recall which project it lived in. You follow the #budget thread across every project at once.

Forte calls this perceiving "cross-disciplinary themes and patterns that defy simple categorization."⁴ Folders organize by container. Tags organize by question. The questions are what you actually have at retrieval time.

The honest part: tags rot too

A tag only helps if you use it again, with the same word, spelled the same way, every time. Break that discipline and you get #todo, #to-do, #tasks, and #task scattered across a year: four labels for one idea, none of them complete. An un-reused tag is exactly as useless as a forgotten folder.

A tag feels like organization while you type it and finds you nothing later. The label cost nothing — only the discipline behind it was ever worth anything.

So the case for tags is not "tags win." It is "tags pay off if you maintain a small, reused vocabulary." This is why Dubois warns against treating the choice as a war: "Don't fall into the trap of thinking that tagging is an either or proposition."⁵ Tags reward consistency the way folders reward decisiveness, and most people have a limited supply of both. The trap is believing a mechanism will organize for you. None of them will.

The third option nobody frames as a choice

Before you build any structure, ask whether you need it. Full-text search answers a real and common case: "I will find it later." If you can usually recall a distinctive phrase from a note, search retrieves it with zero filing effort and zero maintenance. For a large share of notes, search is the cheapest retrieval path there is.

Search is not a universal answer. It fails when you cannot remember any exact words, or when you want every note about a fuzzy theme rather than one note containing a phrase. That is precisely where tags and a hand-written index earn their keep.

We have argued elsewhere that the most reliable way to navigate a note collection is one index note you write by hand — a curated list of links to your live topics — and not the auto-generated graph view, which is a trap. An index is a third retrieval path alongside tags and folders.

The point is not to organize maximally. It is to organize only as much as your retrieval habit demands. The full case for capturing differently rather than capturing more lives in our piece on why people are deleting their second brains.

So which one wins? Neither, and that is the answer

There is no universal best system, and any honest guide says so. The consensus is not a verdict but a blend: shallow folders for broad type, intentional tags for cross-cutting topic, search underneath both. One 2026 industry guide puts it bluntly: "There is no universal best system," and "Most users end up with a hybrid: Shallow folders + intentional tags."⁶

Forte reaches the same place from the other direction. The purpose of tagging, he writes, is "Not to replace the hierarchy, but to complement it."⁷

That is the resolution. A few broad folders give your notes a place to live. A small set of reused tags gives them the cross-cutting doors folders cannot. Search catches everything you never bothered to file. You are not choosing a side — you are assigning each mechanism the job it is good at.

What to actually do this week

Pick a structure you can maintain, then change it freely as your retrieval habits reveal themselves over the next few weeks. Start small and let real use, not aspiration, grow it. Most over-organized systems die of ambition in the first month. Four moves are enough to begin, and each one can be undone later:

• Keep folders shallow and few. Use them for the one broad type that never changes: work, personal, a major project. If you hesitate over where a note goes, the folder tree is already too deep.
• Tag the questions you actually re-ask. Not every attribute, only the threads you have pulled before (#decision, #someday, a client name). Keep the list short enough to remember without looking.
• Trust search for the rest. If you will recall a phrase, you do not need a tag. Reserve structure for what search cannot reach.
• Reuse, or delete. Once a quarter, merge the duplicate tags and drop the ones you applied once and never followed. A tag used once is noise.

Why this choice is reversible

In plain Markdown, tags and folders are both just text on your own device, so any decision is undoable. A folder is a directory name. A tag is a #tag line inside a file. Reorganizing folders is renaming files; renaming a tag is a find-and-replace across your notes. Nothing is locked in a proprietary schema, because there is no schema.

A precise fact underwrites this. A #tag is not even part of Markdown. The CommonMark specification reserves # for ATX headings only, and it shows directly that #hashtag on its own line renders as the literal paragraph <p>#hashtag</p>, "not a heading, because the first [#] is not followed by a space."⁸ The hashtag-as-tag is a convention each app layers on top of plain text; the spec has no note-tag syntax at all.⁹

That is the ownership turn. Because both mechanisms are ordinary text, your structure travels with your words — readable in any editor, searchable with any tool, rewritable whenever your needs change. This is the same property that lets your notes act like a database without becoming a silo.

Steph Ango, who maintains Obsidian, frames the principle behind it: "File over app is a philosophy: if you want to create digital artifacts that last, they must be files you can control, in formats that are easy to retrieve and read."¹⁰

Frequently asked questions

The questions below are the ones people actually type when choosing a structure. Each answer holds the same line as the essay: pick by how you retrieve, expect to use more than one mechanism, and remember that in plain Markdown the whole decision stays reversible.

Should I use tags or folders for my notes?

Use folders for the one question "where does this belong" — a single broad home per note. Use tags for "what is this about" — many cross-cutting labels one note can carry at once. Most people end up using both, plus search, because the questions differ.

Are tags better than folders?

Neither is better in the abstract. Tags are more flexible because a note can hold unlimited tags but only one folder. Folders are simpler because they force one clear home. The 2025 Obsidian case study found that the right choice follows how you retrieve, not which is objectively superior.¹

What is the difference between tags and folders?

A folder is a container: a note lives in exactly one. A tag is a label: a note can carry many. Folders sort by where something belongs; tags sort by what it is about. In plain Markdown a folder is a directory name and a tag is a #tag line — both are editable text.²

Do tags or folders work better in Obsidian?

In Obsidian, as in any Markdown app, the mechanism that works better is the one matching your retrieval habit. Both store as plain text — folders as directories, tags as #tag lines you own. The reversibility is the same. The decision is yours to change at any time, not the app's to lock.

Is a hashtag part of Markdown?

No. The CommonMark spec uses # only for headings and shows that #hashtag alone renders as literal text, not a tag or a heading.⁸ Tags are an app convention layered on plain text — which is exactly why a tagged note stays readable and rewritable without the app.⁹

Can I just use search instead of organizing?

Often, yes. If you reliably recall a distinctive phrase, full-text search retrieves a note with no filing or upkeep. Search struggles only when you cannot remember any exact words or want every note about a fuzzy theme. Reserve tags and a hand-written index for those cases.

How do I stop my tags from becoming a mess?

Keep a small, reused vocabulary and audit it on a schedule. Merge duplicates like #todo and #to-do, and delete any tag you applied once and never followed. An un-reused tag is as useless as a forgotten folder; consistency, not quantity, is what makes a tag findable.⁵

The question was never which mechanism is correct. It is how you reach for a note when you need it, and whether the structure you chose can change as freely as your mind does.

Both folders and tags are just text you can rewrite — you can try one today and the other tomorrow on mnmnote.com, where your notes stay plain Markdown on your own device.