How long should a file name be?

Under 25 characters in most cases. Past that, some systems truncate or fail to recognize the asset, and the name stops being scannable. Length is a constraint, not a place to store the whole story; that is what metadata is for.

Should the date go first in a file name?

Almost always, and start with the year in YYYYMMDD or YYMMDD format. Folders sort by name, so a date-first name sorts chronologically by default. You can flip the sort to show newest first whenever you need to.

What characters should I avoid in file names?

Anything beyond letters, numbers, underscores, and dashes. Skip spaces and symbols like @ # $ % ^ & * ( ) and punctuation. Many systems reject them or fail to open the file. Use underscores to separate fields and capitals to keep names readable.

How many components should a file name have?

Four to five, including the date, a descriptor, and the extension. More than that and the name gets long and inconsistent. Decide the components with stakeholders, then document them with real examples.

Do file names still matter if we have a DAM with search?

Yes. Unlike metadata tags or folder structure, file names travel with the asset to every platform, every export, every hard drive. They are the one searchable handle that survives a migration. A good name is the cheapest findability you will ever buy.

File naming conventions that actually get used

The simplest, most durable way to make a library searchable. Build a convention your whole team will follow, then make it stick.

A file naming convention is a defined, logical framework for naming digital files so the name summarizes what the file is. It is the simplest and most durable way to bring order to a content library. Names travel with assets across every platform, export, and migration, which is why they outlast almost every other organizing system you put in place.

Get this right and a stranger can find a known asset in seconds. Get it wrong and your team re-uploads files they already own, because nobody can tell 20220214leadershipbrunchjohnsmith0001.jpg apart from the version sitting in someone else's download folder.

Why file naming conventions matter

Three benefits do most of the work:

Organization. Most platforms, servers and cloud DAMs alike, sort files by name. A standard name reorganizes a library the moment you apply it.
Search that works anywhere. Metadata tags and folders are platform-specific. File names are searchable no matter where the asset lives, so users always know how to find one.
Universal understanding. A standardized name tells any user the purpose, origin, and content of an asset before they open it, regardless of which department created it.

How to build a convention in three steps

Step 1: Design the convention

Pull a representative from every team that uses the library; different file types need slightly different names, and you want buy-in from the people who will apply them. Identify your core components. Every name shares a creation date, a sequence number, and an extension. Beyond those, pick from creator initials, location, project name or number, channel, and version. Then cap it: four to five components total, names under 25 characters.

Step 2: Apply names that read cleanly

Separate each component with an underscore and capitalize as needed, so 20220212_LeadershipBrunch_JS_0001.jpg beats a run-on string. Put the date first, starting with the year, so files sort chronologically on their own. Use batch-rename tools like Adobe Bridge, Photo Mechanic, or your DAM to rename whole folders at once and preview the result before committing.

Step 3: Document and govern

Write the convention down in one place everyone can reach, with visual examples. Then match your descriptive fields to a controlled vocabulary so the same concept is not named five ways. If a sports team uses an Action field, the values should come from a fixed list, not from whatever word the photographer reached for. Otherwise you get both 20211231_Throw_PD_0001.jpg and 20211231_Pass_JS_0001.jpg, and searchers have to guess.

The rules for effective names

Keep each name under 25 characters.
Start with the date in YYYYMMDD or YYMMDD.
Use specific, consistent keywords that describe the asset.
Use capitals, underscores, and dashes; never spaces.
Avoid special characters entirely.
Preserve the file extension.
Put a sequence number at the very end of visual assets.

Two real examples

The Baltimore Ravens name game photos by date, week of season, team abbreviation, and sequence: 20190908_Week_1_BR_001.JPG. A corporate event team names by date, event, photographer initials, and sequence: 20220212_LeadershipBrunch_JS_0001.jpg. Both are instantly legible to anyone on the team.

This article adapts and expands a guide originally published on the Stacks blog, drawn from naming systems built for real DAM programs.

Key takeaways

A naming convention is the cheapest, most portable findability you can buy.
Design it with stakeholders, cap it at four to five components, document it with examples.
Date first, underscores between fields, no special characters, extension preserved.
Tie descriptive fields to a controlled vocabulary so names stay consistent.