Introduction
Consistency is key. It's important to develop, implement and consistently maintain your naming conventions, folder structures and workflow. Just as important is developing a workflow that makes sense to you and that you can actually maintain over time — if it's too complicated, you're not going to stick to it.
What Is a File Naming Convention?
A file naming convention (FNC) is a logical framework for naming your images in a way that plainly describes and identifies what they contain and how they relate to other files. A good FNC identifies important distinctions and similarities between your files through easily readable key elements such as date, project or client name, location, format, or intended use. Using unique, standardised filenames keeps you organised, maximises searchability, speeds up retrieval, and lets you quickly determine the contents and relevance of a particular image.
Project Folders
Within your archive, every client, every job, every event, every location — every thing that you shoot — should be separated into its own distinct project folder.
One useful approach is to split your files (and hence your archive and workflow) in two: one side for personal projects, the other for business or paying clients. It's a simple way to narrow things down — did you shoot it for yourself, or did someone pay you to shoot it?
So within your archive you might have two top-level folders: Personal and Business. Within each of these sit your project folders. Some people like to add a further layer, sorting by year, or year then month, or state and city. How far you organise down by subfolder depends on your volume — scale up or down as needed.
Project folders are best named something like:
[2023-05-15] John and Jane Smith Wedding, or [2021-05-01] Rushworth Easter Heritage Festival, or [2022-11-21] 12 Apostles Sunset.
It's essential to be consistent with your naming and formatting: include the date of the shoot and other pertinent information (client name, location) in plain, human-readable form, and even a job reference number if you want to get fancy — this could tie into your invoicing system. The reverse date in square brackets means you can simply sort your folders by name and they'll drop into a clean ascending or descending date order, while still staying logical and quickly readable (as opposed to, say, 20221121, which at a quick glance can look like a jumble of numbers). Human-readable names and locations support both plain-text searching and quick identification when browsing a list of project folders.
While tagging within software is certainly useful, it's good practice not to be entirely dependent on it — software changes and updates, companies go out of business, and a tool you rely on today could stop working tomorrow, especially in a world of subscription software. That's why it's important to keep names human-friendly and your organisation robust enough to survive a change of tools.
Within each project folder, use subfolders to organise what the files inside are for. At a bare minimum, two folders labelled RAW and FINAL work well — all captured RAW files go into RAW, and all fully edited, exported files go into FINAL (with a few steps in between, of course). That's a bare minimum; it's also common to add folders like WEB (low-resolution sRGB files for online use), WM (watermarked versions), and PRINT (files set up and laid out ready for printing).
RAW Files (Camera Capture)
There's some debate around renaming RAW files, mainly centred on uniqueness, filename collision avoidance, and searchability. It's best practice for every RAW file you capture to be uniquely identified, and unfortunately camera-generated names don't guarantee this — IMG_1234 or DSC_1234, for example, will repeat every time the camera's counter passes 9999.
To avoid filename collisions across multiple cameras, it helps to modify each camera's internal three-character alphanumeric prefix to reflect the specific camera — for example, 5D4_XXXX.CR2 for a 5D4 and 06D_XXXX.CR2 for a 6D, or 810_XXXX.NEF for a D810 and D8E_XXXX.NEF for a D800E. Multiple cameras of the same model can be labelled A and B (5DA and 5DB, say). Note that some cameras set to capture in Adobe RGB colour space will force the first character to an underscore — adjust your prefix accordingly.
A combination of approaches works best: modify the prefix in-camera as above, and also batch-append your RAW filenames with a date at file ingestion (more on this below). Combining date, camera prefix and original image number creates enough uniqueness that, unless you're shooting more than 10,000 images per camera per day, you'll never run into a collision — every RAW file you produce will be uniquely named.
For example: 20220705_5D4_4268.CR2 or 20230217_D8E_1249.NEF.
Because RAW filenames need a higher level of uniqueness and brevity than the project folder naming above, human readability matters less here, so we omit the square brackets and hyphens from the date.
FINAL Files (Digital Client Supply)
For final edited files you deliver to clients, they should never see your original imported image filenames — only the derivatives, named with their own scheme. Aim to balance brevity, readability and completeness: a good default is the same name as your project folder, plus the date, plus a unique numeric identifier.
Example: JoshEmilyWedding_20220613_001.jpeg.
If you're producing WEB or WM versions, add that at the very end.
Example: JoshEmilyWedding_20220613_001_WEB.jpeg.
Print File Naming
Naming files specifically for printing — and particularly for supply to a fine art printer like us — has some further considerations worth taking into account. These are covered thoroughly in our companion article, Practical Tips for Print File Naming.
Best Practices
Some general filename best practices:
- Use reverse dates, ordered from the largest to smallest unit of time — YYYY-MM-DD, YY-MM-DD, YYYYMMDD, or YYMMDD. This is actually a defined international standard: ISO 8601.
- Use CamelCase (the first letter of each word capitalised, no spaces).
- Between elements, use underscores rather than spaces.
- Within an element, use hyphens.
- Try to keep filenames shorter than 50 characters.
- Only use periods in the file extension (.jpeg).
- Only use alphanumeric characters (A–Z, 0–9), hyphens and underscores.
- Don't use special characters or punctuation (e.g. "!#*^%@|'?/<>).
- When suffixing multiple files with numbers, use preceding zeros so they sort correctly — "01, 02, 10" will sort in order, whereas "1, 2, 10" will sort as "1, 10, 2".
Resources
Harvard University has an excellent article on file naming conventions here, and eXadox has a good article on the reasoning behind why we name things the way we do here.
Next Steps
A naming convention is only half the picture — the file management software you use day to day matters too. See our review of Directory Opus, the file manager we rely on in-house, and our detailed guide to print file naming for the specifics of preparing files to send to a printer.