How to Add Tags in Obsidian Markdown: A Complete Guide
Tags in Obsidian are one of the simplest — and most powerful — ways to organize your notes without relying on rigid folder structures. Whether you're building a personal knowledge base, managing research, or tracking projects, understanding how tags work in Obsidian helps you connect ideas across your entire vault.
What Are Tags in Obsidian?
In Obsidian, tags are labels you attach to notes (or specific sections within notes) to group related content regardless of where it lives in your folder hierarchy. A note about "sleep habits" inside a Health folder can share a tag with a note about "productivity routines" inside a Work folder — because tags cut across structure.
Obsidian renders tags as clickable links. Click any tag and Obsidian opens a search showing every note in your vault that carries it.
The Two Ways to Add Tags in Obsidian Markdown
1. Inline Tags (In the Note Body)
The most direct method: type a hashtag followed immediately by a word, anywhere in the body of your note.
#productivity #project-management #book/fiction Rules for valid inline tags:
- No space between
#and the tag name - No special characters except hyphens (
-), underscores (_), and forward slashes (/) - Numbers are allowed, but a tag cannot be all numbers —
#2024reviewworks,#2024does not - Tags are case-insensitive in search, though Obsidian preserves the case you type
2. Frontmatter Tags (YAML Metadata)
Frontmatter sits at the very top of a note, enclosed in triple dashes. This is the preferred method when you want tags to be clean metadata rather than mixed into your prose.
--- tags: - productivity - project-management - book/fiction --- You can also write frontmatter tags on a single line:
--- tags: [productivity, project-management] --- Note that in frontmatter, you do not include the # symbol — Obsidian handles that automatically.
Nested Tags: Creating Tag Hierarchies 🗂️
Obsidian supports nested tags using the forward slash as a separator. This lets you build a lightweight taxonomy without creating folders.
#project/active #project/archived #book/nonfiction #book/fiction In the Tags panel, #project/active and #project/archived both appear under a collapsible project parent. This is especially useful when your vault grows large and flat tag lists become hard to navigate.
Where nested tags shine:
- Status tracking (
#status/draft,#status/published) - Content types (
#type/article,#type/meeting-note) - Topic hierarchies (
#health/nutrition,#health/sleep)
Finding and Managing Your Tags
Once tags are added, Obsidian gives you several ways to work with them:
| Feature | What It Does |
|---|---|
| Tags panel (left sidebar) | Lists every tag in your vault with note counts |
Search operatortag:#name | Filters search results to tagged notes only |
| Graph view filter | Visually isolates notes sharing a tag |
| Dataview plugin | Queries notes by tag in table or list format |
The built-in Tags panel updates in real time as you add or remove tags across your vault.
Common Tag Mistakes to Avoid
Mixing inline and frontmatter inconsistently — both work, but picking one convention per workflow keeps things predictable. Many users prefer frontmatter for primary topic tags and inline tags for contextual callouts within a note.
Using spaces in tag names — #meeting notes won't work as a single tag. Use #meeting-notes or #meeting_notes instead.
Over-tagging — adding dozens of tags to every note sounds thorough but quickly degrades tag usefulness. Tags become meaningful when they're selective.
Forgetting the # rule difference — inline tags need #, frontmatter tags don't. Mixing this up is the most common source of tags not appearing in the Tags panel.
How Tag Behavior Varies Across Setups 🔍
How useful tags are in practice depends on a few real variables:
- Vault size — In small vaults, folders may be sufficient. As note counts grow into the hundreds or thousands, tags become significantly more valuable for cross-cutting organization.
- Plugin usage — Users running the Dataview plugin can query tags like database fields, unlocking dashboards, task tracking, and dynamic indexes. Without plugins, tags work well but stay within Obsidian's native search.
- Mobile vs. desktop — Obsidian's mobile app fully supports tags, but editing YAML frontmatter on mobile is less ergonomic. Some mobile users lean toward inline tags for speed.
- Sync and publishing workflows — If you use Obsidian Publish or third-party sync tools, frontmatter tags are often more reliably parsed by external systems.
- Team vs. solo use — Shared vaults benefit from agreed tag taxonomies upfront. Solo vaults can evolve organically, with tags renamed later using a find-and-replace or the Tag Wrangler community plugin.
A Note on Tag Consistency Over Time
Tags are only as useful as your consistency in applying them. A #reference tag used in 300 notes and a #ref tag used in 12 notes are functionally separate — Obsidian won't merge them automatically. Establishing a short list of core tags early, and sticking to it, pays off more than an elaborate taxonomy that drifts over time.
What that list looks like — how many tags, how deeply nested, whether frontmatter or inline — depends entirely on the kind of thinking and work your vault is meant to support.