A Simple File Naming System for Campaign Assets
Campaign folders can have a way of collecting files that look almost identical. One is the new export, one is the earlier crop, and one has “final” in its name despite being several rounds from the finish. Opening each file to work out what it is isn’t a system so much as a small administrative hobby.
A shared naming pattern can make the useful details visible at a glance. It doesn’t need to explain the whole brief. It just needs to help a teammate identify the campaign, channel, asset, version, date, and approval status without guessing.
Start with one repeatable pattern
A straightforward pattern is:
campaign_channel_asset_version_date_status.ext
For example:
spring-launch_social_story-v1_v03_2026-09-25_review.png
In practice, the asset field doesn’t need to include “v1” if the version field already does that job. A cleaner example is:
spring-launch_social_story-1080x1920_v03_2026-09-25_review.png
Each field has a set place. That consistency is the point: when filenames follow the same order, people can scan them quickly, and sorting by name groups files in a more predictable way. A naming pattern won’t rescue a folder with no structure at all, but it can make the files inside it a lot less mysterious.
Give each part a clear job
Campaign: Use a short name that distinguishes this work from other projects. “spring-launch” is more useful than “spring,” which could refer to a product release, an event, or the season the folder was last cleaned.
Channel: Pick a brief, familiar label, such as social, email, or web. If a team needs to distinguish placements, it can add that detail to the asset field: story-1080x1920, homepage-hero, or email-header.
Asset: Say what the file is, using the detail that helps someone choose the right one. That might be its placement, format, or dimensions. The goal isn’t to pack every production note into the filename; it’s to make the file recognizable before it’s opened.
Version: Number versions in one consistent format, such as v01, v02, and v03. Leading zeros keep the numbers in a tidy order when a folder is sorted alphabetically. If a team uses descriptive labels like v03-copy-update, it should agree on where that extra detail belongs.
Date: Use year-month-day, written as YYYY-MM-DD. A date like 2026-09-25 is unambiguous and sorts chronologically. The team should decide what the date means—often the date of the export or update—and apply that choice consistently.
Status: Keep the list short. Labels such as draft, review, and approved cover many workflows. A status should describe where the file stands now, not preserve its entire history. If the file moves from review to approved, update the status as part of the agreed process.
See how it works on real files
Here are a few illustrative filenames using the same pattern:
spring-launch_social_story-1080x1920_v01_2026-09-22_draft.pngspring-launch_social_story-1080x1920_v02_2026-09-24_review.pngspring-launch_social_story-1080x1920_v03_2026-09-25_approved.pngspring-launch_email_header-1200x600_v02_2026-09-25_review.jpg
The first three files share a campaign, channel, and placement, so their versions and dates show how that particular asset changed. The fourth makes clear that it’s a different placement, even though it belongs to the same campaign. A teammate can narrow down what to open without inspecting every thumbnail or relying on someone remembering which export went where.
In this example, approved identifies the approved version of the social story, while the email header is still in review. That distinction only helps if the status is maintained. A filename that says “approved” after the file has changed is a confident-looking source of confusion—which is still confusion.
The fields can be adapted to fit a team’s work. A video edit might need an aspect ratio or cut length in its asset label; a print placement might need a size. The order should stay stable even when the details vary. If every channel invents its own order, the pattern stops being a pattern and becomes several small dialects.
Set a few rules before the folder fills up
Choose one separator and stick with it. Underscores between fields and hyphens within a field make the example filenames easy to read. Spaces can also work if the team prefers them, but mixing spaces, underscores, and several other separators makes names harder to scan.
Keep labels brief, spell them the same way, and decide whether they use lowercase. Agree on channel abbreviations before a folder fills with variations like social, soc, and Social. Avoid vague labels such as new, latest, and final-final. They sound informative until someone has to choose between three files that all claim to be the last one.
It also helps to settle two questions in advance: when does a file get a new version, and when does its date change? A team might create a new version for a meaningful revision and use the date of each export. Another team might follow a different rule. Either can work if people know what the numbers and dates represent.
Approval deserves its own rule. Decide who can mark a file approved and whether approval applies to that exact export or to the broader creative. When a substantial change creates a new version, the team should make sure the status still reflects what’s actually been reviewed. A tidy filename is no substitute for a clear approval process, but it can make that process easier to follow.
Make the system easy to keep using
A naming convention works best as a shared team habit, not a puzzle each person solves alone. Put the pattern and a few examples where people can find them when they start a project. Keep the list of channel and status labels short enough to remember. Then use the same convention across the campaign’s working files and exports, adjusting only the details that genuinely need to change.
The best system isn’t the one with the most fields. It’s the one that answers common questions quickly: Which campaign is this for? Where will it appear? Which version is this? Has it been approved? If a filename can answer those without becoming a miniature brief, it’s doing its job.
Inspire Studio provides a workspace for agencies and their clients to help manage asset workflows. Visit Inspire Studio to learn more about its workspace.