How to Organize Notes with Files, Projects, and Tags

Organize your notes in three layers: a file is a single note, a project is the stable bucket that note lives in, and tags are the flexible labels that cut across projects. Each note sits in exactly one project but can carry several tags, and that one rule is what keeps a growing pile of notes findable.

The reason it works is that the three layers answer different questions. A project answers "where does this belong?" A set of tags answers "what is this also about?" Mix those two jobs into one folder tree and most note systems collapse.

Quick answer

Think of it as one structural layer plus one cross-cutting layer.

• Files are the atomic unit: one note, one file.
• Projects are your handful of stable buckets — Work, Writing, a specific client, a course. A note belongs to exactly one.
• Tags are flat labels like draft, meeting, idea, or reference that you reuse across every project.

The single rule: one project per note, many tags per note. Get that right and you'll rarely have to remember where you filed something — you can find it by what it is about instead.

Step-by-step

1. Make each note a file

Keep one idea, meeting, or document per file. A file is the thing you actually open and edit, and small focused files are easier to move, link, and tag than one sprawling document. Give it a clear first line — a plain heading works as the title:

# Client kickoff — Acme
Date: 2026-06-18
Next step: send recap by Friday

A short, descriptive opening line does double duty: it titles the note and makes it scannable in a list.

2. Group files into projects (your stable buckets)

A project is a folder by another name, and a folder is a hierarchical container where a file lives in exactly one place at a time (directory)). That single-location property is a feature, not a limit: it forces you to pick the one bucket each note primarily belongs to, which keeps the whole structure honest.

Keep projects broad and few. Good projects are the stable areas of your life or work that rarely change — Work, Personal, a named client, a book you are writing. If you're spinning up a new project every week, you're probably reaching for what tags are meant to do.

3. Add tags for the themes that cross projects

A tag is non-hierarchical metadata: a keyword you attach to a note, with no parent and no fixed location, and one note can hold many tags at once (tag)). That's exactly the part folders can't do. A single meeting note might live in the Acme project and still be tagged meeting, billing, and follow-up, so it surfaces alongside every other meeting or billing note regardless of which client it came from.

Use tags for the themes that recur everywhere: status (draft, done), type (meeting, idea, reference), and context (urgent, someday). These are the cross-cutting questions a folder tree answers badly.

4. Pick a tag convention and keep it small

Decide your format once and hold to it: lowercase, singular or plural but not both, hyphens for phrases (follow-up, not Follow Up or followups). Before inventing a new tag, check whether you already have one that means the same thing. A deliberately small vocabulary is what separates a useful tag set from a long, noisy one, and our notes and Markdown guides go deeper on conventions that last.

Common problems and fixes

Tag sprawl. The most common failure is an uncontrolled vocabulary: idea, ideas, and Idea all coexist, and the tag list grows faster than your notes. Tagging is people-driven and the keywords are freely chosen, which is its strength and its weakness — a folksonomy drifts unless you impose a few conventions on yourself. Fix it by reusing tags before creating new ones and pruning synonyms when you spot them.

Treating tags as a replacement for structure. Tags work best as a complement to organized buckets, not a substitute for them. The Nielsen Norman Group makes this point directly: tagging supplements structured navigation rather than replacing it. Keep your projects doing the structural work and let tags add the flexible cross-cutting layer on top.

The junk drawer. If you tag everything notes or misc, you have a label that points at your entire collection and therefore at nothing. A tag only earns its place if it splits your notes into a useful subset. When a tag applies to almost everything, delete it.

Folders nested five levels deep. Deep hierarchies hide notes and force you to remember the exact path. Flatten to two levels at most and push the detail into tags, which you can combine at search time instead of navigating to.

Doing this with Carets

This three-layer system only works if your editor treats files, projects, and tags as first-class — and that mapping is exactly how Carets is built. Carets is a fast, native notes and code editor for iPhone, iPad, and Mac that keeps your work in Markdown, plain text, and code rather than a proprietary database.

Three things make it a good home for this system. Your notes are real files in plain text, so the "one note, one file" layer stays portable and is not locked to one app. Projects and tags are built in, so the single-project-plus-many-tags rule is the native way to organize rather than a workaround. And because Carets handles Markdown and code with syntax highlighting in the same editor, the same setup holds whether you are filing meeting notes, drafts, or config snippets. You can browse more guides on notes and Markdown as you refine your own conventions.

Carets is on the App Store for iPhone, iPad, and Mac — get Carets and set up files, projects, and tags that still make sense a year from now.

Frequently asked questions

Should I use a folder or a tag?

Use a project (folder) for the one stable bucket a note belongs to, and tags for every cross-cutting theme it also touches. The folder answers "where does this live?" and the tags answer "what else is this about?" Most notes need one of the first and a few of the second.

How many tags should one note have?

Usually two to four. That is enough to find the note by theme later without making every note look identical. If you're adding eight tags, some of them are probably describing the project, not the note.

Do tags replace folders?

No. They do different jobs and work best together. Projects give you stable, mutually exclusive structure; tags give you flexible retrieval across that structure. A system with both is easier to keep tidy than one leaning entirely on either.