Search-Friendly File Naming: Habits That Work Anywhere

Every search tool, from a Finder window to a review platform, has to match what you type against what's in the name. Tools differ in the details, but the habits that help them are the same. A search-friendly name is one that someone else can guess and type without seeing the file first. This guide covers the habits that make that possible. The examples use a fictional client, ACM.

What makes a file name easy to search?

A name is easy to search when it has three things:

• Words someone would actually type. Real words and codes your team uses, not private shorthand.

• One way of writing each thing. The same code, spelling and word order every time.

• Something unique. At least one part of the name that points to this asset and nothing else.

Most search failures come from the second point. The file exists and the name describes it, but it uses a different word, spelling or form than the person searching.

Should words in a file name be separated?

Yes. Many search tools match from the start of a word, so a word buried inside a run-together name can be missed. Separators make each word its own.

ACMLaunchTeaserV3.mov is one long word. ACM_HERO01_launch-teaser_v03.mov has separate parts for the client, the asset, the description and the version, and each one can be searched on its own. Our file naming best practices guide covers which separators to choose. For search, what matters is that you use them, and use them the same way every time.

Why does a unique asset ID help so much?

Descriptive words are shared by many files. Search for hero or logo and you’ll get every hero and every logo across every client. A short, unique ID such as HERO01 or KV02 narrows that to one asset, and still returns every version of it.

A few habits keep IDs useful:

• Make them distinct. HERO01 is unlikely to appear by accident. A bare 01 matches dates, versions and frame numbers too.

• Keep them for the life of the asset. The ID stays the same from first draft to final delivery. Only the version changes.

• Use them everywhere the asset appears. Project files, renders, stills and review uploads all carry the same ID, so one search gathers the whole family.

Why does one shared vocabulary matter?

Search tools are literal. If one person writes teaser, another trailer and a third promo, a search for any one of them finds only a third of the files. Agree on one word per thing, and write the list down:

• Deliverables: teaser, cutdown, bumper, lower-third, not a mix of synonyms.

• Spelling: pick color or colour, gray or grey, and keep it.

• Singular or plural: still or stills, not both.

• Abbreviations: only if they’re on the list. lt means nothing to a new freelancer. lower-third means the same to everyone.

A short glossary on one page is often enough. It does more for search than any search feature.

Should specs like aspect ratio and length go in the name?

If people search by them, yes. Deliverable specs are some of the most common things a producer looks for: “all the verticals”, “every 15-second cut”, “the Spanish versions”. Put them in fixed fields, written one way:

• Aspect ratio: 16x9, 9x16, 1x1, not a mix of 916, vertical and 9-16.

• Duration: 15s, 30s, 60s.

• Language or region: a short code such as EN or ES, always in the same place.

ACM_HERO01_launch-teaser_9x16_15s_ES_v02.mov can be found by any of those facts. ACM teaser spanish vert short.mov can only be found by someone who guesses the same words.

Do version and date formats affect search?

They can. Some search tools match parts of words, so a search for v3 can also return v30 through v39. Zero-padded versions with a fixed width (v03, not v3) make the version you want easier to pick out, and they sort correctly too.

Dates written year first, like 2026-11-12 or 261112, also work as search terms in tools that match the start of a word: 2026-11 can pull up a whole month. Use one date format per project so the search pattern is always the same. Our sort order guide covers padding and dates in more detail.

Should the meaning live in the name or the folder?

In the name. Folders give useful context, but files leave their folders all the time: they’re uploaded for review, attached to emails, pulled into a DAM or downloaded to someone else’s desktop. Client, asset and version should survive that trip. If a file only makes sense inside ACM/Launch/Teaser/, it stops making sense the moment it’s shared.

Tags, keywords and comments are a helpful extra layer, but they depend on someone filling them in, and they don’t always travel with the file. The name moves with it.

How can I test whether a name is searchable?

Try it the way a teammate would. Close the folder, open whichever search box your team uses, and type what you think someone would type to find the file: the client code, the asset, the spec. If it doesn’t come up first, or comes up buried among near-identical names, the name needs work. Do this once for a few typical files when you set up a new project, and the convention gets tested before it’s relied on.

Before and after

For how Finder, Spotlight and Project panels search, see our guide to everyday search on the Mac. For shared drives, Frame.io and DAMs, see our guide to team search. For AI search tools, see Why Consistent Names Help AI Search Tools Find the Right File.

A short search-friendly naming checklist

• Separate the parts of every name, the same way every time.

• Give every asset a short, unique ID and keep it for life.

• Write down one word for each kind of deliverable, and one spelling.

• Put searchable specs, such as aspect ratio, length and language, in fixed fields.

• Zero-pad versions and write dates year first.

• Keep the key facts in the name, not only in the folder or tags.

• Test a few names in a real search before the project gets busy.

Check your names

Prisma: file-naming and folder-structure tools for creative studios. To see how your current names hold up, paste a few into the free Prisma Scanner, which needs no signup and gives a score plus recommendations on where names break good practice.

Open Prisma Scanner

Your studio defines its own rules.

Finder and Spotlight are trademarks of Apple Inc., registered in the U.S. and other countries and regions. Frame.io is a trademark of Adobe in the United States and/or other countries. Prisma is not affiliated with, sponsored by or endorsed by Apple or Adobe. ACM is a made-up client code used for illustration only.