TAGS & METADATA

The AI can see the photo. It cannot see who it was for.

Tagbox.io helps you build a simple, consistent tagging system on top of the AI - so you can search by the client, the venue and the campaign, not only by what is in the picture.

ClientBay Hotel Group
VenuePier 27
CampaignSpring 26
PhotographerDana R.
Cleared untilMarch 2027
Venue pier
Pier 27 61 photos
Pier27 merged
pier 27 sf merged
Create "pier" not allowed

ONE VOCABULARY

EVERY TAGGING SYSTEM STARTS CLEAN. THIS ONE STAYS CLEAN.

When anyone can type a new tag you get "Pier 27", "pier27" and "Pier 27 shoot" for one place. Build one clear tagging language for your whole organization - and the platform keeps it that way: the field offers existing tags first, new tags are a permission, duplicates merge in one click.

TAG CATEGORIES

10 CATEGORIES OF 15 TAGS, NOT ONE LIST OF 150

You can skim this in a couple of seconds and see everything the library holds. Someone who has never opened it picks the category first, then the tag inside it.

Client
NorthlineBay Hotel Group+13
Venue
Pier 27The Armory+13
Campaign
Spring 26Launch+13
Usage rights
Web onlyPaid social+13

GETTING STARTED

YOU'LL START FROM AN ORGANIZED WORKSPACE ON DAY ONE. WE'LL MAKE SURE OF IT.

We build your tagging system out of your existing folder names and the rest of your business data - so the library is sorted the way your team thinks before you have uploaded anything.

FREQUENTLY ASKED QUESTIONS

"Who is allowed to invent a new tag?"

Whoever you say. Adding to the shared vocabulary is a permission; everyone else picks from what already exists. That one setting is what stops a tag list sprawling.

"We already have a folder structure that works. Do we lose it?"

No - it becomes the starting vocabulary. Your categories get built out of your existing folder names and business data before you upload anything, and migration is included from Basic up.

"Two people tagged the same thing 'Client' and 'client'. Now what?"

Capitalisation merges on its own. And when a new tag is close to one that already exists - a synonym, a different spelling - we suggest the existing one before it gets created. Anything left over you merge yourself in a couple of clicks, and it applies across the whole library.

"Can tags hold usage rights and expiry dates?"

They don't have to. Usage rights are their own feature rather than a tag, so terms and expiry live on the asset itself and filter alongside everything else. How copyrights work in Tagbox.

"How many tags is too many?"

There is no limit. In practice we'd keep it under about ten categories of thirty tags - past that a list stops being readable. We help you set that structure up as part of onboarding.

"Do we need a tag for everything?"

No - and you shouldn't. Anything we can detect already, don't tag: people are found by face recognition, and file type, quality and plenty more are built-in filters. Tags are for what only you know - the client, the campaign, the rights.