Finder tags: the setup order that holds up

Nearly every walkthrough of Finder tags begins in the same place: select a file, right click, pick a colour. That instruction is correct and it is also the reason most tag systems are abandoned by the second month. Applying a tag takes two seconds. Deciding what the tag means takes longer, and skipping that decision produces a list of forty names, half of them near duplicates, none of which reliably returns the right set of files.

The order below puts the decisions first and the clicking last. It assumes the reader already has a Mac full of files, already knows how to right click, and wants a structure that is still working in March. Each step exists because the step after it fails without it.

Step one: write down the questions before naming anything

A tag is only worth creating if it answers a question that gets asked repeatedly and that a folder path cannot answer. So the first artefact is not a tag list. It is a list of questions, written in plain language.

Useful questions look like this. Which files still need a reply. Which files belong to the client whose work is spread across four project folders. Which files are finished and safe to archive. Which files are reference material that will be opened again next year.

Unhelpful questions look like this. Which files are PDFs, since the Finder already knows the file type. Which files are in the invoices folder, since the folder already answers it. Which files are important, since the definition drifts within a week and the tag ends up on everything.

Once the questions exist, each one becomes at most one tag, and the tag gets the shortest name that cannot be confused with another. Singular or plural, capitalised or not: pick one convention and hold to it, because the tag field completes existing names as they are typed and an inconsistent convention produces two tags where one was intended.

The realistic starting number is five. Not twenty. A list of five that is applied consistently returns useful sets from the first week. A list of twenty is a filing job that gets skipped whenever there is any pressure, and a tag applied to sixty percent of the files it should be on is worse than no tag at all, because the incomplete result still looks like a complete one.

Step two: set up the seven favourite slots

Finder Settings, Tags section. This is the screen that decides whether the system gets used, and it is the one most guides skip.

The list holds every tag on the machine. Ticking a tag shows it in the Finder sidebar. Dragging tags into the Favourite Tags area at the bottom determines which ones appear in the right click menu and in the tag row of the Save dialog, and there is room for seven.

The reason those slots matter is friction. A tag in the favourites is applied with one gesture from a menu that is already open. A tag outside them requires the Get Info panel or typing into a tag field, which takes long enough that people stop doing it when busy. So the five questions from step one should occupy five of the seven slots, and the remaining two stay empty until something earns them.

Order inside the favourites area is not decorative either. Apple documents that the keys Control plus 1 through Control plus 7 add or remove the favourite tags, in the order they are arranged, and that Control plus 0 strips every tag from the selected file. That means the sequence in that little box becomes a set of keyboard shortcuts, so the tag applied most often belongs in the first slot rather than wherever the colour order happens to put it. Knowing the zero key exists also removes the main hesitation about tagging quickly, since a wrong tag is undone in one keystroke instead of a trip through the Get Info panel.

Colours are assigned in the same screen. Seven colours exist, they cannot be extended, and their only job is to make a state recognisable without reading. Attaching a colour to a state that changes, such as waiting or done, pays off because the change is visible in a list view. Attaching a colour to something permanent, such as a client name, mostly produces visual noise, and those tags work better as plain names.

Step three: move the tagging to the moment of saving

Tagging as a separate chore never survives. Tagging as part of an action already being performed does.

The Save dialog in any macOS application has a Tags field directly under the filename, and whatever sits in the favourite slots is offered there. A file tagged at the moment it is created is tagged at the only moment when its purpose is completely obvious, which is also the moment that costs nothing, because the dialog is already open and the hands are already there.

The same principle applies to the Downloads folder, which is where most untagged sprawl originates. A file downloaded and left alone will not be tagged later. A file downloaded and immediately given one tag from the right click menu takes one second and never needs revisiting.

For anything that arrives automatically, Automator folder actions attach a workflow to a folder so that it runs as files land in it, and the Shortcuts app can run file actions from the Finder's Quick Actions menu. Both are worth setting up only after the vocabulary has proved itself over a few weeks, since automating a tag name that then gets renamed means editing the workflow too.

Step four: turn each question into a Smart Folder

A tag with no saved query attached is a tag nobody looks at. The sidebar entry for a tag is a start, but it returns everything carrying that tag across the whole machine, which is usually too wide.

File, then New Smart Folder, opens a query builder. Adding a tag condition and then narrowing by kind, by date range or by enclosing folder produces the answer to an actual question rather than a raw tag dump. Saving that search puts a .savedSearch file in ~/Library/Saved Searches, and ticking the option to add it to the sidebar turns a recurring question into one click.

Three saved searches are usually enough to cover a working week. Everything waiting on a reply. Everything for the current client, modified in the last thirty days. Everything marked finished but still sitting outside the archive.

One thing to know before relying on them: a Smart Folder shows files, it does not contain them. Deleting an item from that view deletes the real file from its real location. Removing something from the list is done by removing the tag, not by pressing delete.

Step five: backfill in batches, and only where it pays

Existing files are where the plan usually collapses, because tagging several thousand of them one at a time is not going to happen. The way through is to accept that most of them never need a tag.

Files that get searched for are worth backfilling. Files that are already archived and only opened by accident are not. A reasonable cut is the last twelve months, plus any folder that gets opened weekly.

Way to apply a tag	Best suited to	Scale it handles
Right click menu, favourite tags	Single files, as they arrive	One at a time
Control plus a number key, on a selection	Repeated tagging without the mouse	Tens
Drag a selection onto a sidebar tag	A visible group in one folder	Tens
Get Info with several files selected	Mixed selections across a window	Tens
The Tags field in a Save dialog	New files, at creation	One at a time
tag and similar command line tools	Whole directory trees by pattern	Thousands

The drag method is the one most people have never tried, and it is the fastest of the manual options. Select a range in a list view sorted by date, drag it onto the tag in the sidebar, and every file in the selection receives it.

For anything larger, the command line is the honest answer. Third party tools installed through Homebrew can add and remove tags across a directory tree in a single command, matched by extension or by path pattern, and mdfind can generate the list of files to feed them. Whether that route is available depends on comfort with a shell, which is the real dividing line between an afternoon of backfilling and a week of it.

Step six: a fifteen minute check, once a month

Tag lists rot in a specific and predictable way, and the repair is cheap if it happens before the list reaches thirty names.

Open Finder Settings and read the tag list top to bottom. Anything that appears twice in different spellings gets merged by renaming one to match the other, which rewrites the tag on every file carrying it. Anything that has not been applied since the last check gets deleted, and deleting a tag removes it from files without touching the files themselves.

Counting is the other half. Running mdfind "kMDItemUserTags == 'waiting'" | wc -l returns how many files carry a given tag right now. A count that keeps climbing means the tag marks a state that nothing ever clears, which is the classic failure of a waiting tag with no matching habit of removing it once the reply arrives. A count near zero means the tag was a good idea that never became a habit, and it can go.

The check also catches the slow drift where a tag changes meaning without anyone deciding to change it. If the files under one name no longer answer the question from step one, either the name or the question needs rewriting.

What happens after the list is narrowed

Every step above is about getting from several thousand files down to the dozen that matter. That part the Finder does well. The part that follows is where the time actually goes: renaming those twelve consistently, moving them somewhere, checking what is inside them, comparing them against last month's set.

Doing that work in the Finder means a lot of repeated gestures. Doing it in a terminal means rebuilding the same query a second time, in a different syntax, because the selection made in one window does not exist in the other. A file manager that keeps the folder view, a terminal and an assistant in the same window removes that handoff, since the narrowed set is already in the place where the next command runs. The feature list describes what that covers, the comparison puts it beside the tools built around dual panes or transfers, and the FAQ answers what comes up in the first week.

What to change first

Write the five questions down before creating a single tag, then put those five into the favourite slots and tag nothing older than today for two weeks. If that habit holds, backfill the last twelve months and not a day further. If the friction turns out to be the work after the search rather than the search itself, that gap is what Atriens was built to close.