File naming conventions are a short set of agreed rules for how everyone in your business names documents, images and design files. They sound like admin trivia until you spend twenty minutes hunting for the latest proposal among “proposal_final”, “proposal_final2” and “proposal_FINAL_use_this”. A consistent naming pattern makes files easy to find, sort and share, and it stops the version confusion that leads to the wrong file being sent to a client. This guide explains how to design simple file naming conventions for a small team and roll them out without a big clean-up project.

Who this guide is for

This guide is for small business owners, office managers, founders and small creative teams who share folders on Google Drive, Dropbox, OneDrive or a shared server, and who work with freelancers or subscription designers who send files back and forth. If your team regularly asks “which one is the latest?”, these rules are for you.

What good file naming conventions do

The research data management guidance from Harvard Medical School’s data management team puts the goal simply: a file name should be descriptive and provide just enough contextual information. The guide was written for research labs, but the principles carry over directly to business files. A good name tells you, without opening the file:

• What it is, such as a proposal, invoice, logo or social post.
• Who or what it relates to, such as the client or project.
• When it was made, in a format that sorts correctly.
• Which version it is, so nobody works from an old copy.

The core rules

1. Put dates in year-month-day order

The Harvard guide recommends writing dates as YYYYMMDD, for example 20261005, so files sort in chronological order automatically. Year-first dates line up correctly in every file browser, while day-first or month-first dates scatter across the list. Some teams prefer hyphens, such as 2026-10-05, which keeps the same sort order and is easier to read.

2. Avoid spaces and special characters

The same guide warns that many computer systems cannot handle spaces in file names. Use underscores, hyphens or camelCase instead, and avoid characters such as slashes, ampersands, question marks and accents. File names that work on every system are easier to upload, link to and back up.

3. Track versions at the end of the name

Harvard suggests adding the version at the end of the file name, such as _v2. When you number versions or sequences, use leading zeros, for example 001, 002 and 010 rather than 1, 2 and 10, so they sort in the right order.

4. Keep names short

The guide recommends keeping names reasonably short and including only the information people need. Long names get cut off in file browsers and email attachments, which defeats the point.

5. Write the convention down

Harvard stresses that naming conventions should be documented so others can follow the same standard, for example in a README file that explains any abbreviations. A rule that lives only in one person’s head is not a rule.

A simple pattern for a small business

Most small teams can cover nearly every file with one pattern:

date_client_project_description_version

Some examples:

• 20261005_brightdental_website_homepage-copy_v03.docx
• 20261012_brightdental_website_hero-banner_v01.fig
• 20261020_internal_marketing_october-newsletter_v02.pdf
• 20261031_greenleaf_brand_logo-primary_final.svg

Use short, agreed codes for clients and projects, and list them in your README so new team members and freelancers can pick them up quickly.

Handling versions and “final” files

The word “final” is a common source of confusion. A few rules keep versions under control:

• Increase the version number with every shared change. v01 for the first draft, v02 after the first round of feedback, and so on.
• Use “final” only once, for the approved file, and never add numbers after it. If the “final” changes, it becomes the next version number instead.
• Move superseded versions into an archive folder inside the project, so the main folder shows only the current file and its predecessor.
• Let your cloud tool track minor edits. Most shared drives keep version history, so you do not need a new file for every small typo fix.

Extra rules for design and marketing files

Design assets often exist in several sizes and formats, which multiplies the confusion. Add one or two optional elements at the end of the name, after the description and before the version:

• Size or placement, such as 1080×1080, story or banner-wide, so the right crop goes to the right channel.
• Colour or variant, such as dark, light or mono, for logos and icons.
• Language, such as en or es, if you publish in more than one.

For example: 20261012_brightdental_social_october-offer_1080x1080_v02.png. Keep editable source files and exported files in separate subfolders, named “source” and “exports”, so nobody accidentally edits a flattened PNG.

A folder structure that does half the work

Names and folders should share the load. A simple structure for a services business might be:

• Clients, with one folder per client code, then one folder per project inside it.
• Internal, for your own marketing, finance and operations work.
• Templates, for proposals, briefs and checklists everyone reuses.
• Archive, for finished projects you rarely need but must keep.

Because the client and project live in the folder path, file names can stay short while still being unique when someone downloads or emails them.

Rolling out file naming conventions without a big clean-up

1. Agree the pattern in one short meeting. Show three or four example names and settle the order of elements.
2. Write a one-page README with the pattern, the client and project codes, and the version rules. Pin it in the shared drive’s top folder.
3. Apply it to new files only. Renaming years of old files rarely pays off. Start from today.
4. Rename active projects as you touch them. When you next open a live project folder, tidy its file names then.
5. Share the rules with freelancers. Add the README link to your briefs so files come back already named correctly.
6. Review after a month. Ask what was confusing and adjust the codes or pattern before the habit sets.

Common mistakes to avoid

• Too many elements. If a name needs six parts to be unique, the folder structure is probably doing too little work. Let folders hold the client and project, and keep names focused.
• Inconsistent codes. “BD”, “Bright” and “brightdental” for the same client make search harder. Pick one code and list it.
• Dates that mean different things. Decide whether the date is when the file was created or the date it relates to, such as a meeting or publish date, and stick to it.
• Relying on memory. Without a written README, the convention fades within weeks.

Where naming fits in your business systems

File naming conventions work best alongside a simple, consistent folder structure and short standard operating procedures for handoffs, approvals and archiving. Our business systems articles cover how to set those up so your team spends less time searching and more time doing the work.

Key takeaways

Good file naming conventions tell you what a file is, who it is for, when it was made and which version it is, without opening it. Put dates in year-month-day order, avoid spaces and special characters, add versions at the end with leading zeros, and keep names short. Write the rules in a one-page README, apply them to new files from today, share them with freelancers, and review the pattern after a month.

Written by the Design Productive Editorial desk. Disclosure: this guide contains no affiliate or sponsored links.