File Naming Conventions Every Creative Should Follow

Every creative has been there. You open a folder and find files with names like:

• logo_final.ai
• logo_final_v2.ai
• logo_final_REAL.ai
• logo_USE_THIS_ONE.ai
• logo_USE_THIS_ONE_fixed.ai

Which one is current? Which one did the client approve? When was it last modified? Without a naming convention, these questions eat time on every project.

The Core Naming Pattern

A reliable file naming convention follows this structure:

client_project_type_version_date

In practice, that looks like:

• acmecorp_rebrand_logo_v03_2026-03.ai
• acmecorp_rebrand_hero-banner_v01_2026-03.psd
• acmecorp_rebrand_style-guide_v02_2026-03.pdf

Each component earns its place:

• Client: Lets you sort or search by client without relying on folder structure alone.
• Project: Differentiates between work streams for the same client (rebrand vs. campaign vs. website).
• Type: What the file represents — logo, banner, deck, export, storyboard.
• Version: Always zero-padded (v01, v02, v10) so alphabetical sort equals chronological sort.
• Date: Year-month (YYYY-MM) is usually enough. Daily work may warrant full dates (YYYY-MM-DD).

Folder Structure That Scales

File naming and folder structure work together. A consistent folder hierarchy reduces the cognitive load of figuring out where a file lives:

acmecorp/
  rebrand-2026/
    01_briefs/
    02_research/
    03_concepts/
    04_revisions/
    05_approved/
    06_delivery/

The numbered prefixes force folders to sort in workflow order rather than alphabetically. 01_briefs always appears before 06_delivery, which mirrors how the work actually flows.

Version Control for Creatives

Developers have Git. Creatives have folder-based version control, which means discipline matters more.

A few rules that prevent version chaos:

Never delete previous versions during active work. Storage is cheap. Losing the ability to revert to a previous approved state is expensive. Keep v01 through v05 until the project is fully closed.

Promote approved files explicitly. When a client approves a version, copy it to an 05_approved folder. Don't rename it. The original file name preserves context about when it was created and approved.

Use a "working" naming convention for in-progress files. Some studios append _WIP to files actively being modified: acmecorp_rebrand_logo_v03_WIP.ai. When the working session ends and the file is stable, drop the suffix. This avoids accidentally sharing draft files.

Common Naming Mistakes

Spaces in file names. They cause problems in URLs, scripts, and some file systems. Use hyphens or underscores instead.

Special characters. Parentheses, slashes, colons, and question marks create issues on different operating systems. Stick to alphanumeric characters, hyphens, and underscores.

Vague type descriptors. "final", "approved", "use-this" are all relative and become meaningless over time. Versions and dates are absolute.

Inconsistent casing. Mixed case conventions (Logo_Final vs logo-final) make search unpredictable. Pick a convention and enforce it — most studios use lowercase-with-hyphens for readability.

Applying This to Client Delivery

When you send files to clients, the naming convention extends to the delivery package itself. A folder called acmecorp_rebrand_delivery_2026-03 with consistently named files inside communicates the same level of care as your design work. Clients who receive well-organized deliveries refer to files correctly in feedback, find things faster on their end, and associate that competence with your brand.

The file name is often the first thing a client sees when they download your work. Make it tell the right story.