Hashtags in note-taking feel almost too simple. You type `#marketing` at the end of a note, and now that note belongs to a category. No drag-and-drop, no nested folder navigation, no renaming hierarchies. Just a word with a `#` in front of it.
But the simplicity is deceptive. A hashtag system that starts clean can quietly grow into a tangled mess of overlapping, redundant, and inconsistent tags — unless you design it intentionally from the beginning.
This guide covers how hashtags work in a note-taking context, where they outperform folders, where they fall short, and how to build a hashtag taxonomy that stays useful as your note collection grows.
Hashtags vs. Folders: The Fundamental Difference
A folder is a location. A note goes into a folder. It can only be in one place at a time.
A hashtag is a descriptor. A note can have as many hashtags as make sense. `#client-a #q3 #decision #legal` — four tags, one note, instantly findable from four different angles.
This is the core advantage: hashtags let a note have multiple identities simultaneously, without duplicating it. A meeting note with `#team-sync #product #q4-planning` can be found when you're reviewing team sync notes, when you're in product mode, and when you're doing quarterly planning — all without living in three separate folders.
The trade-off: folders impose structure on you. Hashtags require you to impose structure on yourself. That's easier when you're disciplined, harder when you're in a hurry or your tagging is inconsistent.
When Hashtags Work Best
Cross-cutting themes. Some topics show up across all your work — `#legal`, `#budget`, `#decision`, `#blocked`. These don't belong to a single project or time period; they're characteristics that apply to notes everywhere. Hashtags handle these perfectly. A folder can't.
Fast capture. When you're capturing a thought quickly, typing `#idea #product` at the end is faster than navigating a folder hierarchy. Speed at the point of capture matters — friction kills the habit.
Evolving categories. Projects end; themes continue. A folder for "Project Phoenix" becomes a dead archive when the project closes. A tag like `#phoenix` can persist and be reused — or deprecated — without leaving an orphaned folder in your system.
Surfacing patterns. Click on `#decision` and you see every significant decision you've made across all your projects. Click on `#blocked` and you immediately see everything waiting on someone or something else. That cross-project view is impossible with folders.
Designing Your Hashtag Taxonomy
This is where most people go wrong. They start using hashtags spontaneously, and six months later they have `#work`, `#Work`, `#work-stuff`, `#professional`, and `#job` all meaning the same thing — and they can't find anything.
Intentional design from the start prevents this. Here's a framework.
Layer 1: Context Tags
Context tags answer "where does this belong in my life?" They're the broadest categories — the equivalent of top-level folders, but used as tags.
Examples: `#work`, `#personal`, `#side-project`, `#learning`
Rule: Pick three to five, use them consistently, and don't add new ones without a good reason. These are your organizing anchors.
Layer 2: Project or Topic Tags
Project tags are specific to a thing you're working on or a subject area you actively engage with.
Examples: `#notly`, `#q4-launch`, `#competitor-research`, `#javascript`
Rule: Create these only when you have more than three notes on a topic. One note doesn't need a tag — you'll find it in search. Three-plus notes is when a tag starts earning its keep.
Layer 3: Type Tags
Type tags describe what kind of note it is, regardless of context or topic.
Examples: `#decision`, `#idea`, `#template`, `#reference`, `#draft`, `#blocked`
Rule: These are reusable across all contexts. A `#decision` in a work note and a `#decision` in a personal note can both be filtered at once — useful for things like a weekly decision review.
Layer 4: Status Tags (Optional)
Status tags describe where a note is in a workflow.
Examples: `#in-progress`, `#needs-review`, `#archived`, `#waiting`
Rule: Only add this layer if you actually review note status regularly. Status tags go stale fast — a note marked `#in-progress` from three months ago might be done, abandoned, or irrelevant. If you won't maintain them, skip this layer.
The Naming Rules That Will Save You Later
Lowercase, always. `#Marketing` and `#marketing` are two different tags in most systems. Pick lowercase and stick with it.
Hyphens over spaces. `#client-a` not `#client a` (which usually breaks). `#q4-planning` not `#q4 planning`.
Specific enough to be useful, generic enough to reuse. `#facebook-ad-campaign-march-2024` is too specific — it'll never be used again. `#paid-ads` is probably the right level. Test: will this tag have at least five notes in it over the next year? If not, it might be too specific.
Avoid overlap. `#tasks`, `#todo`, and `#action-items` all mean the same thing. Choose one. When creating a new tag, ask: "Does a tag that means this already exist?"
Singular vs. plural: Pick one convention and apply it everywhere. `#idea` or `#ideas` — not both.
Practical Tagging Patterns for Common Workflows
The Weekly Review Setup
Use a combination of type and status tags to make weekly review effortless:
``` #review-weekly + any note you want to revisit on a weekly cycle #decision + any significant choice you've made #blocked + any task waiting on external input ```
Every Friday, filter by each of these in sequence. Weekly review becomes a tag-by-tag walkthrough rather than an anxious scan through everything you've written.
The Project Launch Pattern
When starting a new project, establish three tags immediately:
- `#[project-name]` — the project tag, goes on every note related to this project
- `#[project-name]-decision` — significant choices made for the project
- `#[project-name]-reference` — background material you'll need throughout
This gives you a project-specific view and two instantly filterable sub-views without creating any folders.
The Idea Capture Pattern
Ideas come fast and die fast if you don't catch them. Keep the tagging minimal at capture:
``` #idea #[rough-topic] ```
That's it. Two tags maximum at the moment of capture. You can enrich later. The goal at capture is speed.
Set a recurring monthly note with `#idea-review` to go through all your `#idea` notes and either develop them further, link them to relevant projects, or archive them.
When Hashtags Alone Aren't Enough
Hashtags are powerful, but they have limits.
Deep hierarchy: If your work involves nested structure — sub-projects within projects within programs — hashtags get unwieldy. You'll end up with `#program-a-project-b-subteam-c`, which nobody types consistently. For deep hierarchy, combine hashtags (for cross-cutting themes) with project notes that act as containers (for structured hierarchy).
Sequential relationships: Hashtags can't express order. They can't say "step 2 of 5" or "this note comes after that one." For workflows with sequence, use note threading or explicit numbering within the note, not tags.
Large teams with inconsistent tagging habits: One person's `#client` is another person's `#customer`. In team environments, hashtag taxonomies need governance — a shared reference document that everyone uses. Without it, shared tag spaces become chaotic quickly.
Starting from Scratch: A 10-Minute Setup
If you're starting a new hashtag system today:
- Write down your three to five context tags. Don't agonize — you can rename later.
- Write down five to ten type tags that reflect how you think. `#decision`, `#idea`, `#reference`, `#task`, `#blocked` are a solid starting set.
- Create a note called `#tag-index` — a running list of your tags with one-line explanations of when to use each one. Update it whenever you add a new tag.
- Start using tags on new notes only. Don't try to backfill your entire note collection.
- After 30 days, look at which tags you actually used. Delete or merge the ones you created but never used again. Promote the ones you used constantly.
A hashtag system that you actually maintain is better than a perfect one you abandon after two weeks.
Hashtags are a tool for thinking, not just for finding. When you tag consistently, you're not just labeling notes — you're creating a map of how your ideas relate to each other over time. That map becomes valuable in ways that are hard to predict until you've been using it for a while.
Start simple. Stay consistent. Let the system show you what it's good at.
Notly supports inline hashtag tagging with autocomplete — type `#` anywhere in your note feed and your existing tags appear as suggestions. Filter your entire note feed by any tag in one click. Try it free.