Vault

Tag Cleaner: Audit & Merge Messy Tags

Scan a notes vault for messy tags: case collisions, plural splits, typos, and nesting issues, then copy a ready rename plan. Runs entirely in your browser.

Runs 100% in your browserUpdated Jul 6, 2026
Live · runs on your deviceNothing leaves your browser

Drop your notes folder here

or choose a folder from your computer.

Only .md and .markdown notes are read. Nothing is uploaded. Files are read entirely in your browser.

Overview

A tag cleaner scans a notes folder for four kinds of tag-taxonomy rot: case collisions like Project and project, singular/plural splits like book and books, near-miss typos such as recieve versus receive within an edit distance of two, and nesting inconsistencies where the same leaf tag sits under different parents. It suggests a merge target for each and builds a rename plan.

How it works

  1. 1Drop your notes folder onto the tool, or choose it with the folder picker. Nothing is uploaded; every file is read locally in your browser tab.
  2. 2The tool reads every inline #tag and every frontmatter tags: list across your notes and tallies each exact tag string into a frequency table.
  3. 3It flags four independent issues: case collisions (Project vs project), singular/plural pairs (book vs books), likely typos (tags within a Levenshtein edit distance of 1 or 2, when at least one side is used twice or more), and nesting mismatches (the same leaf tag under different parents, or no parent at all).
  4. 4Each issue comes with a suggested merge target, picked as the tag with the higher usage count; you can change the target or leave an issue unchecked to skip it.
  5. 5Check the issues you want to merge, then copy the plain rename map or the Obsidian-ready instructions and apply them in your vault.

Worked example

A 9-tag vault after a year of loose tagging

Across 75 tagged notes, nine distinct tag strings turn up: Project (4 uses) and project (26) are the same tag split by case; book (3) and books (9) are a singular/plural pair; recieve (2) and receive (12) sit two edits apart, a clear typo; and todo (6) sits alongside work/todo (8), the same leaf nested under a parent in some notes and not others. The tool reports exactly four issues from those nine tags, each suggesting the higher-count tag as the merge target: project, books, receive, and work/todo.

Methodology & privacy

Four checks run independently over the tags in your scan, and each produces a suggested merge target equal to whichever tag in the group has the higher total usage count (ties prefer the lower-case form, then break alphabetically). Case: tags are grouped by their lowercased form; any group with two or more distinct casings in use is a case collision. Plural: lowercased tags are checked for an exact x-to-xs pair or a y-to-ies pair (book to books, policy to policies) in a single pass per tag, not a full pairwise scan. Typo: every remaining pair of lowercased tags is compared with Levenshtein edit distance, the number of single-character insertions, deletions, or substitutions needed to turn one into the other; a distance of 1 or 2 counts as a likely typo, but only when at least one of the two tags is used 2 or more times, so two genuinely rare, coincidentally similar tags are never flagged as typos of each other, and a pair already reported as plural is never also reported as a typo. Nesting: tags are grouped by their final slash-separated segment (the leaf); any leaf shared by two or more full tags with different parents, including a tag with no parent at all, is a nesting inconsistency. The tool only ever reads your files to build this report; it never writes to them. You review each issue, pick or accept a target, and apply the rename yourself.

Your notes never leave your browser. The tag scan runs entirely on the folder you drop in or select, locally in your browser tab; nothing is uploaded, and closing the tab clears everything.

FAQ

My tag pane is not of any use right now. How do I clean it up?

+

Drop your notes folder into this tool and it builds a frequency table of every tag in the vault, plus four kinds of issues: case collisions, singular/plural splits, typos, and nesting mismatches, each with a suggested merge target. Review the list, check the merges you want, and copy a rename map or Obsidian-ready instructions to apply them.

If I take identical words with different casing, why do they get treated as unique tags?

+

Obsidian's own search treats tags as case-insensitive, but the Tags pane still displays whichever casing was typed first, so a vault can end up with both Project and project live at once, which confuses plugins, Dataview queries, and exports that do compare tags case-sensitively. This tool groups every casing of the same tag together, shows the usage count for each, and suggests the higher-count form as the merge target.

How do I rename or delete a tag across my whole vault?

+

Obsidian's core Search plugin can find every note containing a tag but cannot replace it in bulk. This tool cannot rewrite your files either, it only reads them, but it generates a copyable rename map and, for a one-click fix, points you to the free Tag Wrangler community plugin, which adds a rename option to the Tags pane.

How does this tool catch typo tags like recieve versus receive?

+

It compares every pair of tags using Levenshtein edit distance, the number of single-character insertions, deletions, or substitutions needed to turn one tag into the other. A distance of 1 or 2 counts as a likely typo, but only when at least one of the two tags is actually used 2 or more times, so a pair of rare, one-off tags that merely look similar is not flagged.

What counts as a singular/plural tag pair?

+

Two lowercased tags where one is the other plus an s, like book and books, or where one ends in y and the other swaps that y for ies, like policy and policies. Only these two common English patterns are checked; unrelated words are left alone.

What is a nesting inconsistency?

+

It is the same tag name used both as a top-level tag and as a nested one, or nested under two different parents, for example todo next to work/todo, or work/todo next to personal/todo. Obsidian treats these as entirely different tags, so notes tagged one way never turn up when you browse the other.

Does this tool rename my tags automatically?

+

No. It only reads your notes to build the frequency table and issue list. You choose which merges to accept, then apply the rename yourself, either by hand, with the copyable search instructions, or with the Tag Wrangler plugin.

This tool fixes one moment. recal handles the whole day.

recal is a private brain for your Mac. It watches how you work, on device, and starts doing your busywork itself. You approve every action.

Get early access