Finder tags: how they work, and why almost nobody uses them

Finder tags are one of the more complete systems Apple has ever built into macOS, and one of the least used. You can apply one from almost any menu, rename the defaults into real words, and pull up everything carrying a tag from any folder on the Mac. All of that is genuinely well made. Most people who have used a Mac for years have still never touched it, or tried it once and quietly stopped. That gap is worth explaining properly, because the reasons turn out not to be about the feature at all.

How do you actually apply a tag to a file?

A tag can be applied from three places, and none of them require planning ahead.

1. Control-click the file, or select it and open the File menu. A row of seven coloured circles appears above a search-style Tags field.
2. Click a colour to apply it straight away, or type into the field below the circles to use an existing tag or start a new one, then press Return.
3. Or click the Tag button in a Finder window's toolbar, if you have added it there, which opens the same field without a menu at all.

A Save dialog carries the same field. Every standard macOS save panel, the one that opens with Command-S in almost any app, has a Tags box next to Where. Add a tag while you are already naming the file and there is no second pass to remember later.

The seven coloured circles are not fixed to Red, Orange, Yellow and so on. Open Finder Settings, then the Tags tab, and every tag you have ever used is listed there. Double-click a name to change it to something that actually means something, Client or Reference rather than Green, and click its swatch to give it a different colour if you want one.

Turn on tags in the Finder sidebar, also set in Finder Settings, and each one becomes a saved search sitting a click away in every window. Click Client and you see every file carrying that tag, wherever it actually lives on disk.

Where does a tag actually live, and how do you search for one?

A tag is not a copy of the file, and it is not stored in a separate list somewhere else. It is written directly into the file's own extended attributes, the same hidden layer of metadata macOS uses for things like where a downloaded file came from. Apple's own name for the tag attribute is com.apple.metadata:_kMDItemUserTags, and because it lives on the file itself, Spotlight indexes it the moment a tag is applied.

Two places actually search it. Type a tag's name or colour into the search field at the top of any Finder window and choose the tag from the suggestions Finder offers, the method Apple documents directly. And Spotlight itself, the search you open with Command-Space, treats tag as a search operator: type tag: followed by a name, for example tag:Reference, and it filters straight to files carrying it without opening a Finder window at all.

Does a tag survive being sent somewhere else?

Sometimes. This is the part worth getting right, because getting it wrong is how a tagging habit quietly falls apart.

Copy a tagged file to another Mac over AirDrop, restore it from a Time Machine backup, or move it between two folders on the same disk, and the tag comes with it. Both filesystems modern Macs use, APFS and its predecessor HFS Plus, store extended attributes as part of the file itself, and Apple's own transfer tools carry that layer across intact.

Upload the same file almost anywhere else and the tag is usually the first thing to go. Google Drive, OneDrive and Box do not preserve extended attributes at all, so a tag never arrives on the other end. Dropbox is the exception among the big three, but only when both ends use Dropbox's own desktop app, since its web uploader does not carry tags either. Attach a tagged file to an email, or send it through a chat app like Slack or WhatsApp, and it goes through the same kind of generic upload those cloud services use, which strips the tag along with almost everything else that is not the file's actual bytes.

So why did a genuinely useful system barely catch on?

None of the mechanics above are the problem. Four things are, and they compound.

The first is the seven coloured circles themselves. Tags did not appear from nothing when OS X Mavericks introduced them in 2013: they replaced an older feature called Labels, which went all the way back to System 7 in 1991 and were nothing but seven named colours, Red through Grey, tinting an icon on a colour screen. Tags carried that exact palette forward as the default. Everyone who ever met the feature met it as colours first and words a distant second, and most people never got as far as the rename field sitting one settings pane away.

The second is timing. Applying a tag takes three or four clicks, right at the moment you are trying to finish saving a file and move on to the next thing. That is precisely the wrong moment to ask someone to stop and categorise, which is why the habit is so easy to start and so easy to drop in the first busy week.

The third is that a tag is invisible almost everywhere except Finder. Open the same file in a browser, a chat app, an image editor, or on someone else's machine, and there is nothing to show it was ever tagged. The label only exists inside the one app built to display it, so a tag set with real care is often simply absent exactly when you go looking for the file somewhere else.

The fourth is the worst kind of incentive: the payoff arrives months later, or not at all. Tagging a file well pays back the day you search for it, which might be a Tuesday six months from now, if it happens. There is no immediate reward for doing it properly, and very little visible cost for skipping it, so most people skip it.

Who should actually use Finder tags?

For one kind of person, none of this is a real problem. Someone who works mostly inside Finder, saves through the standard dialog rather than dragging files around after the fact, and keeps a library in the low hundreds rather than the tens of thousands, can build a tagging habit that costs nothing extra. Add the tag while the Save dialog is already open, keep the list to a handful of renamed colours rather than dozens of new ones, and search by clicking the sidebar instead of trying to remember exact names. Used that way, tags are free, quick and genuinely reliable, right up to the limits above.

What changes is the payoff, not the tagging

A visual library does not solve the click-timing problem or the third-party-app problem by making tagging easier. Muse tags what arrives automatically, so there is no menu to open and no moment to remember. The bigger difference shows up later, at the exact point Finder tags were always weakest: what you get back when you go looking. A saved search returns a list of filenames. A visual library returns the actual things you saved, arranged so you recognise the right one on sight rather than reading through names you gave them six months ago.