Why Use Tags Instead of Folders? One Item, Many Homes
Why a folder is a tree and your knowledge is a graph, and when that difference actually matters.
Use tags instead of folders when your knowledge is connected and multi-faceted, because a folder forces each item into one location while a tag lets it live in every category it actually belongs to. A folder is a tree with one parent per item; your knowledge is a graph where one thing relates to many, and tags match that. Honestly, though, studies find folders and tags perform similarly and many people prefer folders, so the real answer is to use tags for connected knowledge work and folders for simple, out-of-sight workflow.
Use tags instead of folders when your knowledge is connected and a single item belongs in more than one place, because a folder forces each thing into exactly one location while a tag lets it live in every category it actually fits. A folder system is a tree: each item has one parent, sorted along a single dimension you have to choose up front. Your knowledge is not shaped like that. A note about the economics of attention belongs under economics, under attention, under the project you are using it for, and under the book you found it in, all at once. Folders make you pick one home and then lose it under the others. Tags let you find it by any of those angles. That said, the honest answer is not that folders are dead, because each approach has real tradeoffs, and which one wins depends on what you are organizing.
What is the actual problem with folders?
A folder lets each item live in only one place, and the world is not that tidy. A folder hierarchy is a strict tree: to file something, you choose one branch, and that decision is final unless you copy the file. The trouble is that most things are genuinely several things at once. A hierarchy allows only a single classification per item, which is why a thing that belongs in two categories, like a platypus that is both a mammal and an egg-laying animal, can only sit in one branch of the tree. For files, that means every save forces a small, lossy decision: of the four real categories this belongs to, which one do I bury it under? And whichever you pick, you will later look for it under one of the other three, and not find it. The single-location rule is the root of most folder frustration.
Why do tags fit the way knowledge works?
Because tags let one item be described by every facet it has, with no single forced order. Tagging is a form of faceted classification, and the whole point is multiplicity: a single resource can be described by many independent facets at once, navigated in any order the searcher prefers, and in a digital system the same item can effectively appear in many places at no cost of duplication. So the attention-economics note gets tagged economics, attention, the project, and the book, and it surfaces no matter which of those you start from. You no longer have to predict, at filing time, the one way you will later look for it. You describe what it is along every dimension that matters, and retrieval works from any of them. That is a fundamentally better match for knowledge that connects in multiple directions, which is most knowledge worth keeping.
Isn’t this just how my brain works anyway?
Yes, and that is the deeper reason tags feel right. Your mind does not store ideas in a strict filing tree. Memory for concepts is organized as a network of nodes linked by associations, where any idea connects to many others, so a single thought naturally belongs to dozens of mental categories at once. A folder system fights that structure by forcing each idea into one slot; a tag system mirrors it by letting each idea keep all its connections. When your external organization matches your internal one, finding things feels like remembering rather than searching, because you can approach an item from any of the associations your mind already made. Folders ask you to think like a tree. Tags let you think like the graph you actually are.
| Folders | Tags | |
|---|---|---|
| Structure | A tree, one parent per item | A graph, many labels per item |
| Each item lives | In exactly one place | In every category it fits |
| You find it by | The one path you filed it under | Any facet you remember |
| Best for | Simple, out-of-sight workflow | Connected knowledge you reuse |
So are tags objectively better?
Not objectively, and the honest evidence is more mixed than tag enthusiasts admit. This is where most folders-versus-tags arguments overreach. In controlled studies of how people actually manage their files, tags and folders perform surprisingly similarly for finding things, and people show a persistent preference for folders despite tags’ theoretical advantages, partly because moving an item into a folder gets it out of sight and feels like progress. Each approach also carries its own cost: folders make you spend effort choosing the one right place, while tags make you spend effort maintaining many labels and resisting sprawl. So tags are not a free upgrade. They are a different tool with a different cost profile, and the right question is not which is better in the abstract but which fits what you are organizing.
Why do most people stick with folders despite all this?
Because folders feel satisfying in a way tags do not, and feeling matters for a habit you repeat all day. Even when tags would serve them better, people gravitate to folders for reasons that are psychological as much as practical. Filing an item into a folder makes it disappear from view, which registers as completion and tidiness, while tagging leaves everything in one big pile that never visibly shrinks. Folders also inherited decades of the desktop metaphor, so they feel like the natural, obvious way a computer stores things, whereas tags ask you to think in an unfamiliar, abstract way. And a folder requires one decision per item, which is cognitively cheaper in the moment than weighing several labels, even if it costs you more later when you cannot find anything. None of this means folders are right; it means the pull toward them is real, and switching to tags is a habit change, not just a settings change.
When do folders still win?
For simple, action-oriented stuff you want out of your way. Folders are genuinely good at some things, and pretending otherwise is how tag advocates lose people. When an item has one obvious category, when you mostly want to file it and forget it, and when your goal is a tidy, out-of-sight workspace rather than rich cross-referencing, folders are simpler and faster. Receipts, completed projects, downloads, anything you file to archive rather than to reconnect, all live happily in folders, because they are not knowledge you plan to weave together later; they are stuff you want stored and gone. The single-location rule that cripples folders for connected ideas is a feature for things that really do have one home. Use folders where the world actually is a tree.
When do tags clearly win?
For connected knowledge you intend to reuse, recombine, and find from many angles. Tags pull ahead exactly where folders break down: a research note, an idea, a quote, a reference, anything that relates to several topics and that you will want to retrieve later by whichever of those topics is on your mind. If you are building a body of thinking, where the value comes from connecting pieces across projects and topics over time, the multi-classification of tags is not a luxury, it is the whole point, because the connections are the asset. This is the same reason a knowledge system should mirror a graph rather than a cabinet, the idea behind keeping your notes in a connected web instead of a flat filing structure. For thinking work, tags win because thinking is connection, and folders sever exactly the connections you are trying to keep.
How do you set this up without it turning to chaos?
Keep the tag vocabulary small and deliberate, or tags become their own mess. The honest risk with tags is sprawl: invent a new label every time and you end up with a thousand near-duplicate tags that help nobody, which is just disorganization wearing a different hat, the same way an over-elaborate system can paralyze you with the burden of maintaining it. The fix is a small, controlled set of tags you actually reuse, a hybrid where broad folders handle the coarse split and tags handle the cross-cutting connections, and ruthless restraint about adding new ones. Most importantly, remember that the system is not the thinking. A tidy tag structure around a vague mind helps very little, because the real organization has to live in you first, which is why a sharp first brain comes before any external filing system. The book Building Your First Brain covers how to build that internal structure, and it is free for the first 1,000 readers.
Key takeaways: match the structure to the knowledge
Use tags instead of folders when knowledge is connected, because a folder forces each item into one location while a tag lets it live in every category it belongs to. A folder is a tree with one parent per item, while your knowledge, and your memory, is a graph where one thing relates to many, and tags match that. The honest caveat is that the evidence is mixed: folders and tags perform similarly and many people prefer folders, since each has real costs, folders in choosing a home, tags in maintenance and sprawl. So use folders for simple, out-of-sight workflow and tags for connected knowledge you will reuse from many angles, often as a hybrid. And keep the tag set small, because the system matters far less than the mind behind it.
Frequently asked questions
Why use tags instead of folders?
Because a folder forces each item into one location, while a tag lets it live in every category it actually belongs to. A folder hierarchy is a tree with one parent per item, but most things are several things at once, so you file a note under one topic and then cannot find it under the others. Tags let you describe an item by all its facets and retrieve it from any of them, which matches how connected knowledge really works.
Are tags actually better than folders?
Not objectively. Studies of real file management find folders and tags perform similarly, and many people prefer folders because filing an item out of sight feels like progress. Each has a different cost: folders make you choose one right place, tags make you maintain many labels and resist sprawl. Tags are a different tool with a different cost profile, not a free upgrade, so the right choice depends on what you are organizing.
When should I use folders instead of tags?
For simple, action-oriented things with one obvious home that you want filed and forgotten. Receipts, finished projects, downloads, anything you archive rather than reconnect, lives happily in folders, because the single-location rule that cripples folders for connected ideas is fine for things that really do have one place. Use folders where your world genuinely is a tree.
When are tags clearly the better choice?
For connected knowledge you intend to reuse and find from many angles: research notes, ideas, quotes, references, anything that relates to several topics. If you are building a body of thinking where the value comes from connecting pieces across projects over time, the multi-classification of tags is the whole point, because the connections are the asset. For thinking work, tags win because thinking is connection.
Don’t tags get messy and out of control?
They can, which is the real downside. Invent a new tag every time and you end up with a thousand near-duplicates that help nobody, which is just disorganization in a new form. The fix is a small, controlled set of tags you reuse, often combined with a few broad folders for the coarse split, and restraint about adding new ones. A disciplined handful of tags beats an endless pile of them.
Should I switch my whole system to tags?
Usually not wholesale. The strongest setup is a hybrid: broad folders for the simple, archival split, and tags for the cross-cutting connections in the knowledge you actually reuse. And remember the system is secondary to the mind using it, since a tidy structure around a vague understanding helps little. Build the internal organization first, then pick whichever external structure matches how you actually retrieve things.