File Naming Best Practices

‍

What’s in a Filename? More Than You Might Think.

Chances are you already know that filenames are used to reference, organize, and retrieve files. Every time you save a file, you have an opportunity to give it a name that will actually mean something later. But how often do we rush past that “Save As” box, accept whatever default the application suggests, or throw something together that made perfect sense on a Tuesday morning in March, and then nothing six months later in August? Put your hand up if you’ve forgotten by Friday afternoon?

Multiply that habit across an entire organisation, and you end up with a file server that looks like a junkyard.

The good news is that modern Digital Asset Management (DAM) systems can do a lot to help. But filenames still matter more than most people realize, even in a well-configured DAM.

Filenames in the Age of DAM

With a DAM system in place, filenames can seem less important. Most DAMs don’t require unique filenames, and their search features let users find files based on descriptive metadata such as keywords, descriptions, custom fields, AI-generated tags, and more. Hypothetically, you could have 100,000 files named “untitled.jpg” in your DAM, all with accurate metadata, and search would still work just fine.

Modern DAMs have also gotten smarter about this. AI-powered metadata generation can automatically tag images and videos based on visual content, transcribe audio, and make assets discoverable through natural language search — with no manual tagging required. In that environment, it’s tempting to dismiss filenames as a legacy concern.

But not so fast.

Why Filenames Still Matter

Keywords from the Path

Many DAM systems can automatically generate keyword metadata from a file’s path, including both the filename and folder names. A file saved as “product-launch-Q1-2025.jpg” will automatically surface in a search for “Q1 2025” or “product launch” without any manual tagging. Well-constructed filenames are a quiet but powerful timesaver, especially when ingesting large volumes of files at once.

Filenames are the Original Metadata

Long before EXIF data, embedded XMP keywords, or AI tagging, filenames were the only metadata a file had. They remain the one form of metadata that works everywhere, in every application, on every system, with no special tools required. Anyone can read a filename. Not everyone knows how to view embedded metadata.

Filenames, File Path and Consensus

If you’re just moving to a DAM solution and looking to catalog your assets, think first about the existing logic and the way your files are organised today. The logic behind how files are named and where they’re saved in nested folders might not work all the time, but these shared folders have worked up until this point, and the logical naming consensus has some value.

Distribution

Your DAM may have beautifully organized, detailed metadata — but what happens when you send a file to someone outside the system? Does the metadata travel with it? Do they know it’s there? Do they know how to read it? The filename, on the other hand, will always be right there in front of them. A descriptive, well-structured filename communicates something useful the moment the file lands in someone’s inbox or downloads folder — no DAM access required.

Sort Order

In most systems that display lists of files, sort order is driven by filename. This becomes a real issue when dates are embedded in filenames using a MONTH-DAY-YEAR format, which groups files by month rather than chronologically. For files to sort in true chronological order, use a YEAR-MONTH-DAY format with a four-digit year; for example, 20260312.jpg rather than 03122026.jpg. It’s a small habit that prevents a lot of frustration.

Unique filenames

What happens when a client or colleague has a question about a file you sent them and references “DSC_0042.jpg”? If you have hundreds of files with that name, you’re already in trouble. A file-naming convention that produces unique filenames gives every asset a reliable identifier that links back to a single file, making it much easier to sync data between systems that key off filenames. A simple convention for multi-user environments: combine the date, a session indicator, the cataloger’s username, and an incrementing number. For example: 20250413_ASmith_001.jpg.

Cross-platform limitations

Filenames can cause unexpected problems when files move between platforms and systems. Characters that are perfectly acceptable on a Mac may not render correctly on Windows. Spaces in filenames are encoded as %20 in web URLs, making links harder to read and share. As a general rule, avoid spaces and special characters in filenames. The following are particularly worth steering clear of:

/ : * ? " < > | [ ] & $

Underscores and hyphens are your friends.

AI Is Helpful — But It’s Not a Substitute for Good Habits

It’s worth acknowledging that AI-powered DAM features have genuinely reduced the burden of metadata management. Automatic tagging, smart search, and content recognition can compensate for much of the filename inconsistency. But they work best as a complement to good file-naming habits, not as a replacement for them. When files leave your DAM it’s the filename that commonly travels with them. When systems fail or metadata gets stripped in transit, the filename remains.

A well-defined, consistently applied file-naming convention is one of the lowest-effort, highest-return investments your team can make. Use a batch-renaming tool to apply your convention to large volumes of files at ingest, rather than renaming them one by one. Most DAMs include this functionality natively, and standalone tools are widely available.

The scenarios above won’t apply equally to every organization, and many teams successfully use metadata to compensate for inconsistent filenames. But if you’ve ever lost time tracking down a file, untangled a duplicate filename problem, or received a confused email from a partner asking which “final_FINAL_v3.jpg” you meant, a file naming convention is probably overdue.

‍