Skip to main content
Guide

A Simple Finder Tag System You Can Actually Maintain

Start with tags for the project, the kind of material and the next action. Use only the tags that help answer a question you regularly ask.

You do not need a complete naming system before you begin. A short list you use consistently is a better starting point than a large list you keep avoiding.

Work backward from a search

Think of a file you recently struggled to find. What did you remember about it?

Perhaps it was for a particular client. Perhaps it needed a response. Perhaps it was a reference you wanted to reuse.

Those are useful candidates for tags. Details you never search for do not need to become labels just because they are available.

For a general work folder, try this starting point:

Group of ideasStarter tagsUse them for
Work areaWork, PersonalA broad distinction you actually need
MaterialReference, Invoice, Receipt, NotesWhat the file is or why you kept it
Next actionTo Review, In Progress, Waiting, DoneOne clearly defined current stage
ProjectYour project namesConnecting related files across folders

The table is a planning aid. These are ordinary tag names, not a hierarchy that Finder creates automatically.

Give each status one meaning

The most useful part of a small system is often its status list. Write down what each status means before applying it widely.

For example, "To Review" means you need to inspect the file. "Waiting" means progress depends on someone else. "Done" means the action you were tracking has been completed.

Avoid using "Done" for both "I read it" and "The client approved it" in the same workflow. When those distinctions matter, use more precise words.

Only apply an exclusive status where that makes sense. A reference file may not need a status at all.

Choose one spelling

Decide between "Invoice" and "Invoices". Choose "To Review" or "Needs Review" for the same purpose, rather than using both interchangeably.

Keep names readable. Prefixes and abbreviations can help in a very large list, but do not start with codes you will have to look up.

Colors can make a familiar list easier to scan. Keep the meaning in the name as well, so the system does not depend on remembering which shade means what.

Download the plain-text tag planning sheet to write down your choices. It is a worksheet, not an importable Little Tagger preset.

Try the list on real files

Choose one active folder and apply only the tags you need. Do not begin by tagging every file you own.

Use the system through a few normal tasks. Notice when a tag makes retrieval easier and when it only adds another decision. Remove the unnecessary choices before expanding the list.

Finder already provides controls for creating, editing and removing tags. Apple's Finder settings guide describes the built-in tag settings.

If you mostly use a few tags on occasional files, that may be enough.

Save the combinations you repeat

When the same tag choices keep coming back, save them as Little Tagger presets. A project preset can add its shared tags. A separate status action can update only the stage of the work.

Use a workflow when the sequence matters. For files you have finished reviewing, remove "To Review" and then add "Done". Keep unrelated project and subject tags intact.

Little Tagger also provides groups to arrange the tag list inside the app. Those groups are an organizational aid, not extra Finder tags or a folder structure on disk.

Review names before merging them

A similar name is a reason to look, not a reason to merge automatically. "Contract" and "Contract Draft" may be related but mean different things.

Check how each tag is being used. Little Tagger's usage and cleanup views depend on the locations it can access and has scanned. A tag that has no use in those results is not proof that it is unused on every disconnected drive or inaccessible folder.

Start with the obvious duplicates. Preserve distinctions you still use.

How many tags should I have?

There is no useful universal target. Begin with the smallest list that answers your real questions, then add a tag when you can explain how it will help you retrieve files.

Should every file have a project, type and status?

No. Those are prompts, not required fields. Apply the dimensions that help with that file and leave the rest out.

Make your conventions repeatable

Build a small system first. When repeating it becomes the problem, Little Tagger can help with presets, workflows and tag-library maintenance. The Finder comparison explains when another app is worth adding.

Related reading

Master your tags.

Tag files in seconds, automate recurring tagging work and take control of your entire tag system. Private, native, built for Mac.

Download on the Mac App Store

Free for 7 days · No account required · macOS 15+ · Apple Silicon