A file naming convention is a defined, logical framework for naming files so each name summarizes the file's contents and stays consistent across the whole team. It is not the same as metadata, but the file name is the simplest, most portable form of metadata: it travels with the asset to every platform, export, and hard drive.
Why it matters
Most platforms sort by file name, and unlike tags or folders, names are searchable no matter where the asset lives. A standard name reorganizes a library the moment it is applied and lets any user understand an asset's purpose and origin before opening it. It is the cheapest findability an organization can buy.
How it shows up in practice
The Baltimore Ravens name game photos by date, week, team abbreviation, and sequence: 20190908_Week_1_BR_001.JPG. A corporate events team uses date, event, photographer initials, and sequence: 20220212_LeadershipBrunch_JS_0001.jpg. Both lead with a year-first date so files sort chronologically, separate components with underscores, and cap length around 25 characters. Batch-rename tools like Adobe Bridge and Photo Mechanic apply a convention to whole folders at once, and some DAM platforms enforce naming rules at upload.
Common mistakes
- Using spaces or special characters that some systems reject or fail to open.
- Packing too many components in, so names get long and inconsistent.
- Putting the date last, so files do not sort in a useful order.
- Designing the convention without the stakeholders who have to apply it.
See the Stacks file naming guide.