The parts of a file naming convention
A file naming convention is one agreed pattern for every file you send a client, so instead of “Logo FINAL final (2).pdf” the third round of a logo becomes acme_rebrand-2026_primary-logo_v03_review.pdf (example), and anyone can tell the client, the job, the round and the review status without opening it.
Most naming trouble on client work comes from one gap: nobody agreed what the next version is called. A convention closes it with a few fixed parts in a fixed order. Pick a starting point above, then change any part.
- Pattern
- The order of the parts, such as client, project, deliverable, version and status. Keep the parts that change least on the left, so files for the same job sit together when sorted by name.
- Separator
- The character between parts. An underscore between parts and hyphens between words, as in rebrand-2026_primary-logo, keeps each part readable and lets you split a name back into its parts.
- Client code
- A short, fixed tag for the client, such as acme. Agree it once at kickoff and never change it, even if the client rebrands, so old and new files still group together.
- Version number
- A number that goes up by one every time a file goes to the client. Padding it with a zero (v01, v02 … v10) keeps v10 after v09 in every file list. Rounds and versions do not have to match, but each sent file needs its own number.
- Status word
- A word from a short fixed list, in review order: for example draft, review, approved. Rename to the last word only after the client has said yes in writing, so the name never claims an approval that did not happen.
- Date stamp
- The day a file was made, written year first (20261107 or 2026-11-07) so names sort by date. Useful for video exports and shoots, where many versions are made on the same job over weeks.
- Vague words
- Final, new, latest, copy, updated, use this. They describe a moment, not a version, and stop being true as soon as the next round arrives. The checker flags them.
Messy file names fixed by a naming convention
These made-up file names are the kind that arrive in a shared folder halfway through a project. Each row runs the name through the same checker as the tool above, then rebuilds it from its real parts under one of the starting conventions.
| Name as received (example) | Problems found | Name under the convention |
|---|---|---|
| Logo FINAL final (2).pdf | Has spaces; Uses “final” instead of a version number; No version number like v01; No status word (draft, review, approved); Has capital letters | acme_rebrand-2026_primary-logo_v04_review.pdf |
| acme_rebrand-2026_primary-logo_v03_approved.ai | None: already follows the rule | acme_rebrand-2026_primary-logo_v03_approved.ai |
| Spring Launch NEW edit.MP4 | Has spaces; Extension is not lower case; Uses “new” instead of a version number; No version number like v01; No date in YYYYMMDD form; No status word (rough, review, locked); Has capital letters | 20261106_northwind_spring-launch_hero-cut_16x9_v02_review.mp4 |
| IMG_4471 copy.jpg | Has spaces; Uses “copy” instead of a version number; No version number like v01; No date in YYYY-MM-DD form; No status word (select, retouch, approved); Has capital letters | 2026-10-28_harbor-cafe_menu-flatlay-014_v01_select.jpg |
| Home Hero (use this one).png | Has spaces; Uses “use”, “this” instead of a version number; No version number like v01; Has capital letters | home-hero_1440w_v02.png |
| Fern&Co Catalogue cover – latest.pdf | Has spaces; Has characters that break on some systems; Has accents or symbols outside plain ASCII; Uses “latest” instead of a version number; No version number like v01; No status word (proof, approved, press); Has capital letters | fern-and-co_autumn-catalogue_cover_a4_v03_proof.pdf |
Where a file naming convention breaks down
A naming convention only works if the client uses it too
Send the convention sheet at kickoff and ask that files sent back keep the same pattern. When a client replies with “logo edits.pdf”, rename it on arrival rather than letting two patterns live in one folder.
A file name is not proof of approval
Anyone can rename a file to “approved”. The name helps people find the right file; the record of the client’s yes, with the date and the exact file, is what settles a dispute later. Keep that record next to the file.
Long names break in odd places
Some zip tools, older servers and synced drives fail on very long paths, and a deep folder tree adds to every name inside it. Keep names short, drop parts the folder already says, and stay under the length limit set above.
Changing the naming convention mid-project costs time
Renaming hundreds of delivered files breaks links in emails, tickets and code. If the pattern must change, apply it to new files from the next round only, and note the date of the switch on the convention sheet.
Questions about file naming conventions
What is a good file naming convention for client work?
One that answers four questions from the name alone: which client, which deliverable, which version and what status. A pattern such as client_project_deliverable_v01_status.ext does that, sorts well and is easy to explain to a client in one line.
Should a file naming convention use underscores or hyphens?
Use one for parts and the other for words, so names can be read and split reliably. Underscores between parts and hyphens inside them is the most common choice. For files that end up in website addresses, hyphens alone are easier to read, which is why the tool switches words to camelCase if both would be hyphens.
Where should the date go in a file naming convention?
First, written year-month-day, when the date is what you search by, as with shoots and video exports. Leave it out for design files where the version number already shows the order, so names stay short.
How does a file naming convention handle “final” versions?
It does not use the word. The last version is simply the highest number with the approved status. If a client asks for one more change after “final”, the next file is v05, not “final-v2”, and nobody has to guess which is newer.
Can I check my existing files against the file naming convention?
Yes. Paste file names into the checker, one per line, and each gets a list of problems such as spaces, capital letters, a missing version or a vague word. Nothing is uploaded; it only reads the names you paste.
Should the file naming convention go in the contract or the brief?
The brief or kickoff notes is the usual place, next to who approves and how many review rounds are included. It is a working agreement rather than a legal term, so keep it easy to update.