What Is a File Naming Convention?

TL;DR

• A file naming convention is an agreed format for naming files.
• It helps people identify, sort, and find related files without opening each one.
• Use stable fields, a clear date format, version labels, and documented rules that the whole team can follow.

What is a file naming convention?

A file naming convention is a shared format for naming files so that the name describes what a file contains and how it relates to other files. It gives a team a repeatable way to identify files in folders, search results, downloads, and handoffs.

Harvard’s data management guidance describes a naming convention as a framework that helps users understand file contents and relationships. It recommends deciding on the convention before a backlog of disorganized files grows. Read the Harvard guidance on file naming conventions.

Why file naming conventions matter

Without a shared approach, related files can end up with names such as “final,” “final-final,” or “new version.” Those names do not say which asset is approved, when it was created, or how it differs from other files.

A clear convention makes names more useful in everyday work. It can help teams:

• Sort files consistently in a folder or library
• Recognize a campaign, market, asset type, or date at a glance
• Distinguish versions without relying on memory
• Reduce confusion when files move between people and tools

How to create a file naming convention

Start with the information people need most often when looking for a file. A marketing team may need brand, campaign, asset type, market, date, and version. A simple pattern might look like this:

Brand_Campaign_AssetType_Market_YYYYMMDD_v01.ext

For example: Northstar_SpringLaunch_EmailHeader_UK_20261026_v01.jpg

The right fields depend on the work. Keep the format useful rather than trying to put every possible detail in the filename. Larger descriptive details can live in metadata fields.

File naming best practices

• Use dates that sort correctly. A YYYYMMDD or YYYY-MM-DD format keeps dates in chronological order.
• Use predictable separators. Choose underscores, hyphens, or another simple pattern, then use it consistently.
• Make versions clear. Use labels such as v01, v02, or a documented date rule rather than “final.”
• Avoid unclear abbreviations. If codes are needed, define them in a shared reference.
• Document the standard. A convention works only when people can find and apply it.

File names and metadata

File names are useful, but they are only one part of a findable library. Digital asset metadata can hold additional information such as asset owner, approval status, campaign, usage rights, or region. Those fields make it easier to filter and govern files when a filename alone is not enough.

Teams that manage a growing library should pair a naming convention with a file management system and a documented metadata framework. For more detail on structured fields and search behavior, see the DAM metadata search guide.

Frequently asked questions

How long should a file name be?

Use enough detail to identify the file, but keep it readable. If a name needs many details, store the rest in metadata instead of making the filename hard to scan.

Should a file naming convention include spaces?

Teams often avoid spaces because some systems and URLs handle them inconsistently. Underscores or hyphens are common alternatives. The key is to choose a rule and document it.

Does a naming convention replace version control?

No. Version labels can help people recognize files, but system-based version control provides a stronger record of changes and current status when it is available.

Sources

Harvard: File naming conventions · BrandLife: Digital asset metadata · BrandLife: DAM metadata search