Blog Image
Build an asset naming convention that works across teams, vendors and local partners: elements, order, separators, versions, examples and a rollout plan.

Asset Naming Conventions: A Guide for Marketing Teams

Author Image

An asset naming convention is a fixed pattern for file names, so anyone can tell what a file is, which campaign it belongs to and whether it is the current version without opening it. The pattern that works has three parts: a set order of elements, one separator and case style, and a rule for versions and approval status. It only holds if one system, with one owner, applies it to everyone who touches the brand, including dealers, franchisees, agencies and vendors. This guide gives you the elements, the rules, working examples and a rollout plan for a team that markets through other people.

Irisnow
Keep Brand Assets Organized
Explore how GearBox brings brand assets, campaigns, orders and partner marketing tools together behind one login.

TL;DR

  • Put elements in a fixed order, from stable to variable: brand or project first, version last.
  • Choose one separator, one case style and one date format (YYYYMMDD sorts correctly), and write them on a single page.
  • Keep names short, around 50 characters or fewer, with no spaces or special characters.
  • Keep version and approval status separate: v04 can still be a draft.
  • A convention fails without adoption, so enforce it where assets are uploaded, ordered and approved, not in a PDF nobody opens.

Table of Contents

What a naming convention does for a marketing team

A file name is the first piece of metadata every asset gets. Search, sorting, reporting and handoffs all start from it. When names follow no rule, you get the problems every marketing team knows: the old logo gets used on a local flyer, two people rebuild the same banner, and nobody can say which version legal approved.

For a brand that sells through dealers, distributors or franchisees, the cost multiplies. Corporate may create a few hundred assets per campaign, and local partners create or customize thousands more. A partner who cannot find the approved file in under a minute will build their own or pull something off an old drive.

A naming convention is not the same as a taxonomy or metadata, and it helps to keep the three apart:

  • Taxonomy is how you classify assets: categories, campaign types, product lines.
  • The naming convention is the human-readable label on each file.
  • Metadata is the searchable detail beneath, such as usage rights, expiry dates, owner or photographer credit, which a name cannot hold.

The name should carry only what people need to recognize a file at a glance. Everything else belongs in metadata. Trying to cram usage rights and approval history into a filename is the fastest route to 120-character names that nobody follows.

The elements a name should carry

Most marketing conventions are built from the same handful of elements. Pick the ones your teams actually search by, not the ones that sound thorough.

Element What it answers Example value
Brand or business unit Whose asset is this? acme, acme-pro
Campaign or project What initiative is it for? springsale26
Asset type What kind of file is it? banner, flyer, video, email
Descriptor What does it show? pool-hero, install-team
Format or size Where will it run? 1080x1080, 9x16, 300x250
Audience or market Who and where is it for? dealer, en-us, fr-ca
Date When was it created or launched? 20270115
Version Which iteration is it? v03

You will not need all eight. A name that uses six elements for every file is a name people abbreviate wrongly. Start with the four questions someone asks when hunting for a file: which campaign, what type, what format and market, which version.

Put the stable parts first

Order matters more than most teams expect. A sound principle is to go from broad to specific, and from stable to variable. The brand or campaign code almost never changes, so it goes first and groups files together when sorted alphabetically. The version number changes most often, so it goes last.

Once you fix the order, never change it between campaigns or teams. Changing order is one of the most common ways a convention quietly breaks, because search filters, reports and any automated parsing depend on each element sitting in the same position.

Formatting rules that keep names consistent

The formatting rules are small, but they are where conventions usually fall apart. Two public standards, one from a university digital assets office and one from a city government, agree on most of them, and they are a good model.

Cornell University’s digital assets guide calls for YYYYMMDD dates, underscores between elements and hyphens within an element, names under 50 characters, periods only before the extension, and only letters, numbers, hyphens and underscores. It also recommends zero-padded numbers of at least three digits, so 001, 002 and 010 sort in the right order. The City of Philadelphia’s digital standards recommend names of 50 characters or fewer, lowercase, no special characters, ISO-style dates, and zero-padded versions such as v01 and v02 placed at the end.

They differ on one point: Cornell separates elements with underscores, Philadelphia uses hyphens. Either works. What matters is that you choose one and never mix them in the same library.

Rule Recommended choice Why it matters
Dates YYYYMMDD (or YYYY-MM-DD) Sorts chronologically and reads the same in every country
Separators One style between elements, optionally another within an element Lets people and systems split the name reliably
Spaces and special characters None; avoid # % & and similar They break URLs, uploads and file systems
Case Lowercase, or one fixed style Prevents duplicates that differ only by capitals
Length About 50 characters or fewer Long names get truncated in tools and email
Numbers Zero-padded (v01, 001) Keeps v10 after v09, not after v1
Extension Lowercase, one period only Avoids upload and parsing errors

Two more habits pay off. First, use agreed abbreviations from a short written list, so “Spring Sale” is never springsale in one file and spr-sale in another. Second, keep the list of allowed values for repeated fields (asset types, regions, channels) in one place. A name that says “banner” in one folder and “display” in another cannot be searched reliably.

Example conventions you can adapt

These examples are illustrations, not standards. Adjust the elements to match how your teams search.

A national campaign asset

acme_springsale26_banner_pool-hero_300x250_en-us_v03.png

The order is brand, campaign, asset type, descriptor, size, locale, version. Underscores separate elements and hyphens join words inside one. The name is 55 characters, so you might drop the descriptor or shorten the campaign code to stay near 50.

A video cut for social

springsale26_video_install-walkthrough_9x16_en-us_v02.mp4

The aspect ratio sits in the name because vertical and horizontal cuts are easy to confuse, and posting the wrong one wastes a media slot.

A co-branded dealer piece

Printed dealer promotion brochure on reception counter

springsale26_flyer_dealer-cobrand_midwest_en-us_20270115_v01.pdf

Here the region element tells you which partner group the file serves, and the date marks the launch.

A document-style file for a folder archive

AAP_20250328_Dragon-Day_001.tif

This is the pattern from Cornell’s own guide: unit code, date, subject, sequence number. It suits photo shoots and event libraries, where a running number matters more than a campaign code.

Whichever you choose, test it with a real example before you publish it. Take twenty files from your last campaign, rename them under the draft rule and see where people hesitate. Every hesitation is a missing rule.

Naming across regions, languages and partners

Global-to-local programs strain a naming convention more than anything else. One national asset may spawn dozens of versions: translated, resized, co-branded, with a local address or offer added. If each region invents its own labels, central reporting becomes guesswork.

Four rules help:

  1. Use codes, not free text, for market and language. Standard locale codes such as en-us, fr-ca and es-mx are short and unambiguous. Decide whether the locale sits in the name at all, or only in metadata, and apply that to every region.
  2. Keep one approved name per campaign and product. Local teams may translate a campaign title in the copy, but the file name keeps the global code, so reporting rolls up cleanly.
  3. Decide what stays global and what may be local. The brand, campaign and asset type are global. The market, language and any local-partner identifier are the variable elements.
  4. Name the partner version as a variant, not a new asset. A dealer’s customized flyer is a variant of the master, so it keeps the master’s campaign code and descriptor and adds a market or partner element.

This is also where a library of loose files starts to strain. A local partner who customizes an asset needs to start from the approved master, change only what is allowed, and send the result through approval. If those steps happen over email, the convention is the first thing to go. Our guide to global brand control without losing local impact covers how the control and flexibility fit together.

Version and approval status

Version numbers and approval status answer different questions, and mixing them is a classic mistake. A version says which iteration this is. Status says whether the right person has approved that exact iteration. A file called v04 can still be a draft, and nothing should be marked approved until the authorized reviewer has signed off on that specific version.

A workable approach:

  • Use simple sequential versions with zero padding: v01, v02, v03. Avoid v1.1 or v1a, because they sort badly and invite argument. Record minor edits in metadata or version history instead.
  • Never reuse or reset a version number for the same asset.
  • Allow only a short, fixed list of statuses, such as draft, review, approved and live.
  • Allow only one approved file per asset and format at a time. When v05 is approved, v04 moves to the archive with a downgraded status.
  • Let the person who publishes set “live”, not the person who approves, because mistakes often slip in between approval and publication.

Status changes more often than anything else about a file, so many teams keep it out of the filename and in metadata or workflow, so a rename never breaks a link. That is a sensible choice if your system tracks status reliably. If you work in plain folders, a status in the name is better than no status. For a wider look at how teams structure review stages, this brand engagement workflow guide is a good companion read.

Rolling the convention out to partners and vendors

Writing the rule takes an afternoon. Getting several hundred people to follow it takes a system. A few practices separate conventions that last from the ones that fade after a quarter.

Build it with the people who use it

Ask the designers, writers, field marketers and agency leads to name a handful of real files under your draft. They will find the awkward spots quickly, and they are more likely to follow a rule they helped shape.

Document it on one page

Write the pattern, the allowed values for each element, three or four real examples and a short list of abbreviations. A convention that lives only in one person’s memory is not a system. Put the page where every contributor, including outside agencies and local partners, can reach it.

Assign an owner

Somebody must own the list of allowed values and approve changes to it. Without an owner, new campaign codes and asset types multiply until the vocabulary is meaningless. In larger organizations this is a small governance group across creative, marketing, IT and regional teams, and its decisions should be built into the tools people use, not left as guidance.

Enforce at the point of entry

People follow rules when the system helps them. The strongest options are upload forms with required fields, controlled picklists for campaign and asset type, and approval steps that reject files that do not conform. Metadata can be mapped from name segments on upload, so the name does double duty. Reviewers should feel free to send back an asset that ignores the template.

Pair names with a simple asset register

For details that do not belong in the name, such as owner, approval status, destination, rights note and expiry date, keep a lightweight register or equivalent metadata fields. The name identifies; the register explains.

Clean up before upload

Work-in-progress names like final-final2 should never reach the shared library. Rename on the way in, and make that a step in your handoff checklist.

Our perspective: names work when the system behind them does

We have spent more than 20 years helping brands that sell through dealers, distributors, franchisees, agents and advisors, and the pattern is consistent. A naming convention is a good idea that many teams cannot hold on to, because the people who must follow it do not work for the brand and rarely sit in the same tool.

That is why we build GearBox® as one platform for campaigns, vendors, co-op funds, orders and brand assets behind one login. When a local partner finds the approved asset, customizes it within the limits corporate sets, orders it and sees it move through an approval hierarchy in the same place, the naming rule has something to attach to. It stops being a document and becomes part of how work moves.

Our asset management module integrates with Adobe DAM and Widen, so teams that already have a library do not have to abandon it. Our Converge® module handles global-to-local marketing, so a master asset and its local versions stay connected. And because GearBox supports multilingual and multicurrency programs, one convention can serve every market.

Our advice: keep the name simple, put detail in metadata, and give every partner one place to work. Steelcase runs 15,000+ users in 9 countries on GearBox, which is the scale at which a loose convention cannot survive and a shared system can.

Client

Put the convention to work in GearBox

If your assets are spread across drives, agency portals and email threads, a naming rule alone will not fix findability. GearBox® brings campaigns, assets, orders, approvals and co-op funds into one login, so corporate keeps control of the brand while each local partner gets what they need to market and sell. See how the digital asset management module fits with Adobe DAM and Widen, or schedule a demo of GearBox.

Irisnow

For more on organizing brand libraries, read our guides on marketing asset management and the digital asset management checklist.

FAQ

Can you give me an example of an asset naming convention?

A common pattern is brand, campaign, asset type, descriptor, size, locale and version, for example acme_springsale26_banner_pool-hero_300x250_en-us_v03.png. Underscores separate the elements, hyphens join words within one, and the version comes last. Adapt the elements to the questions your teams ask when they search.

What is the difference between a naming convention and metadata?

The naming convention is the short, human-readable label on the file. Metadata is the searchable detail stored with it, such as usage rights, owner, expiry date and approval status. Keep the name to what people need at a glance and let metadata carry the rest.

Should dates and versions go in the file name?

If you use a date, write it as YYYYMMDD or YYYY-MM-DD so files sort chronologically. Versions should be sequential and zero-padded, such as v01 and v02, at the end of the name. Keep approval status separate from the version number, since a later version can still be a draft.

How long should a file name be?

Most public standards, including those from Cornell and Philadelphia, recommend about 50 characters or fewer. Long names get cut off in tools and are hard to follow. If a name will not fit, move detail into metadata.

How do you get partners and vendors to follow the convention?

Share a one-page guide with examples, involve a few partners in drafting it, and name an owner for the list of allowed values. Then build the rule into the upload and approval steps with required fields and picklists, so following it is easier than ignoring it.

Sources

See how GearBox® transforms channel marketing and drives measurable results with our innovative platform.

SCHEDULE A DEMO