Tags vs Folders for Notes: Which Organization System Actually Works?

The question appears early when building a PKM system:

Should I organize my notes with folders (hierarchical: Projects → Current → ProjectA) or tags (flat with metadata: #project-a, #urgent, #research)?

Both work. But differently. And for different reasons.

The wrong choice can make your system feel wrong as it grows.

This guide covers the tradeoffs, where each excels, and the hybrid model that works best for most people.

---

Folders: Hierarchical Organization

How Folders Work

You organize by hierarchy:

Projects/
  Client Work/
    Client A/
      Proposal.md
      Feedback.md
    Client B/
Areas/
  Health/
    Fitness/
    Nutrition/
  Career/
Learning/
  Books/
  Courses/
Reference/

Each note lives in exactly one folder.

Strengths of Folders

1. Intuitive Structure

• Everyone understands folders (it's how file systems work)
• New users need no explanation

2. Clear Boundaries

• A note is in one place (no ambiguity)
• Project A's notes stay separate from Project B's

3. Browsable

• You can explore folders and discover what you have
• Useful for serendipitous discovery

4. Familiar Tool Integration

• Works in Google Drive, Dropbox, Obsidian, Windows Explorer, etc.
• No special tool knowledge needed

Weaknesses of Folders

1. Rigid Once Created

• If a note fits multiple categories, you have to choose one
• Moving notes to new folders is disruptive

2. Scaling Problems

• As you add more notes, folder structures become complex
• Deep hierarchies (Projects > Current > Active > Q1 > Marketing) are hard to navigate

3. Maintenance Burden

• Old folders accumulate (do you archive or delete?)
• Folder names become outdated
• Moving between projects means reworking structure

4. Cross-Cutting Relationships are Hard

• If you want to see all notes tagged "urgent" across projects, you have to dig through multiple folders
• Many useful views require folder-based thinking

5. Limited Metadata

• A note is just a title in a folder
• No way to tag, rate, or categorize without adding to filename

---

Tags: Flat Organization with Metadata

How Tags Work

All notes live in one folder (or a few top-level folders).

Notes are organized using tags:

All Notes/
  Client A Proposal.md
    #client-a #proposal #urgent #q1
  Learning Spaced Repetition.md
    #learning #technique #pKM
  Product Roadmap.md
    #product #urgent #planning #q1

You can view notes by any tag combination.

Strengths of Tags

1. Flexible Categorization

• A note can have multiple tags
• One note can belong to several categories simultaneously
• "Client A Proposal" is both #project-a and #urgent and #proposal

2. Scales Infinitely

• Whether you have 10 or 10,000 notes, tags work the same way
• No folder hierarchy to maintain

3. Cross-Cutting Views

• Show me all #urgent notes across all projects
• Show me all #learning notes in #pKM
• Show me notes for #project-a from the last week

4. Non-Destructive Reorganization

• Change a tag, and all views update
• No moving files, no broken links
• Add or remove tags without disruption

5. Rich Metadata

• Each tag adds a dimension of information
• Can tag by project, by type, by status, by urgency, by date

Weaknesses of Tags

1. Requires Discipline

• Inconsistent tagging breaks the system
• "client-a" vs "clientA" vs "Client A" creates multiple tags
• Tagging adds friction to note creation

2. Less Intuitive Initially

• New users have to learn how to tag effectively
• "What tags should I use?" requires thinking

3. Tag Sprawl

• Over time, you accumulate hundreds of tags
• Becomes hard to choose the right tags
• Some tags become unused

4. Discoverability Challenges

• Without browsing folders, you might not discover notes you forgot you had
• Tag search requires knowing what tags exist

5. Tool Dependency

• Tags only work in sophisticated tools (Obsidian, Roam, Notion)
• Not portable to simpler tools like basic markdown editors

---

Where Each Excels: By Scenario

Scenario	Folder	Tag	Reason
< 50 notes	Folders	—	Small systems don't need tag complexity
> 500 notes	—	Tags	Folders become unwieldy
Very organized person	Folders	—	Enjoys hierarchy
Cross-cutting views needed	—	Tags	"Show all urgent" across projects
Simple archival	Folders	—	Easy to move old folder to archive
Multiple projects	—	Tags	Notes span projects easily
Collaborative team	Folders	Slightly better	Shared folder structure is clear
Personal knowledge base	—	Tags	Flexible, non-destructive
Legacy/formal system	Folders	—	Established structure, low change
Flexible/evolving system	—	Tags	Adapt easily as priorities change

---

The Hybrid Model (Best of Both)

Most users end up with a hybrid:

Shallow folders + intentional tags

Structure

Projects/
  Project A/
    note.md
    note.md
  Project B/
Areas/
  Career/
    note.md
  Health/
    note.md
Learning/
  note.md
  note.md
Reference/
  note.md

Folder rules:

• Max 3 levels deep
• Top level: Projects, Areas, Learning, Reference (PARA method)
• Projects and Areas are self-contained

Tag rules:

• Consistent naming (lowercase, hyphens)
• 10–20 core tags
• Common tags: #urgent, #waiting, #in-progress, #done, #status-*

Why This Works

From folders: You keep intuitive browsing and clear top-level structure.

From tags: You add cross-cutting organization and metadata.

In practice:

• Browse Projects folder to see active projects
• Use tags to filter: show me #urgent notes across all Projects
• Search for #learning-spaced-repetition to find all related notes, even if scattered

---

How to Choose: Decision Framework

Ask These Questions:

1. How many notes do you have?

• < 100: Folders alone is fine
• 100–500: Hybrid model
• 500+: Tags are essential

2. Do you need cross-project views?

• Yes (show all #urgent, all #waiting): Tags
• No (each project is isolated): Folders

3. How much change/reorganization?

• High: Tags (non-destructive)
• Low: Folders (simpler)

4. How disciplined are you with metadata?

• Very: Tags can work well
• Somewhat: Hybrid
• Not at all: Folders (no choice to make)

5. Is your tool tag-aware?

• Yes (Obsidian, Roam, Notion): Tags work great
• No (vanilla markdown, Google Drive): Folders only

Recommendations by Type

Student: Hybrid (folders for courses, tags for urgency + status)

Researcher: Tags (need to cross-reference between projects)

Writer: Folders (projects are self-contained, simpler browsing)

Team Manager: Folders (clear shared structure, simpler onboarding)

Librarian/Archivist: Folders (formal structure, stable over time)

Entrepreneur/Maker: Hybrid (projects need flexibility, status tracking)

---

Migration: From One to the Other

If you switch, here's how:

From Folders to Tags

1. Accept that reorganization is one-time work
2. Take all notes from folders into a flat structure
3. Add tags based on former folder location: file in "ProjectA/Overview" gets #project-a tag
4. Add additional tags: #urgent, #status, #date
5. Delete folders (or keep for archival)

Time estimate: 2–4 hours for 100 notes.

From Tags to Folders

1. Identify your top-level categories (Projects, Areas, Learning, Reference)
2. Create folder structure
3. Move notes from flat structure into folders based on primary tag
4. Remove tags

Time estimate: 2–4 hours for 100 notes.

---

Maintaining Your System

For Folder Systems

Monthly:

• Review folder structure
• Archive completed projects
• Clean up old folders
• Add necessary new folders

For Tag Systems

Monthly:

• Review active tags
• Delete unused tags
• Standardize tag names if they've drifted
• Add new tags as needed

For Hybrid Systems

Monthly:

• Clean up folders (archive completed projects)
• Review and standardize tags
• Ensure tagging is consistent

---

Conclusion

There is no universal best system.

Folders work best for:

• Small systems
• Organized people
• Formal structures
• Single-project focus

Tags work best for:

• Large systems
• Cross-cutting views
• Flexible structures
• Multiple-project focus

Hybrid works best for:

• Most people with growing systems
• Systems needing both structure and flexibility

Start with what feels natural. If your system feels wrong after 3 months (too rigid, too complex, hard to find things), switch.

For more on organizational methods, see PARA Method. For broader PKM context, check Personal Knowledge Base.

Organize intentionally. Maintain consistently. Evolve as needed.

Find your system.