A File Naming Convention That Makes Files Easy to Find

You know the file exists. You made it last month, you remember roughly what was in it, and now you are scrolling through a folder of "final_v2", "final_FINAL" and "Document (3)" trying to find it. A consistent file naming convention fixes this, and it takes about ten minutes to set up.

The aim is simple: any file you save today should be findable in a year by search or by sorting alone, without opening anything. Below is the convention I use for my own work and for the small teams I help, plus the rules that make it stick.

Why most file names fail

File names fail in three predictable ways. They describe the file only from the point of view of the moment it was saved ("notes", "new draft"). They put the least useful information first, so alphabetical sorting is meaningless. And they track versions with words like "final", which stop being true the moment someone asks for one more change.

Search tools help, but they are not a substitute. Windows and macOS search both rank file names heavily, and a name like "scan0042.pdf" gives search almost nothing to work with.

A file naming convention that works for almost everything

Use this pattern:

YYYY-MM-DD_project_description_v01.ext

For example: 2026-10-14_kitchen-refit_quote-brightway_v02.pdf. Each part has a job.

Part	Example	Why it is there
Date (ISO format)	2026-10-14	Sorts in true date order on every system
Project or area	kitchen-refit	Groups related files when sorted or searched
Description	quote-brightway	Says what the file is in two to four words
Version	v02	Shows order of drafts without "final"

Use the ISO date format

Year, month, day, with leading zeros: 2026-03-07, not 7-3-26. This is the only date format that sorts correctly as plain text, and it avoids the confusion between US and European day-month order.

Separate parts with underscores, words with hyphens

Underscores split the main parts and hyphens join words inside a part. That way "kitchen-refit" reads as one unit. Avoid spaces: they break some command-line tools, become "%20" in links and confuse sync software on older systems.

Pad version numbers

Use v01, v02 through to v10. Without the leading zero, v10 sorts before v2 in many file managers.

Stick to safe characters

Letters, numbers, hyphens and underscores only. Slashes, colons, asterisks, question marks, quotation marks, angle brackets and the pipe symbol are blocked on Windows and cause sync failures when files move between Mac, Windows and cloud storage. Keep names under about 60 characters, since long paths can exceed the 260 character limit that still affects some Windows apps.

The counter-take: you do not need a date on every file

Many guides insist that every single file starts with a date. I think that is overkill and makes some files harder to find.

Dates belong on files that are events or snapshots: invoices, meeting notes, quotes, reports, photos, exports. They do not belong on living reference documents that you update constantly, like "household-budget.xlsx" or "brand-guidelines.pdf". Putting a date on those creates a new question every time you edit them: do I rename it? Most people do not, so the date ends up wrong, which is worse than no date at all.

A practical rule: if the file would make sense as a row in a timeline, date it. If it is a tool you keep coming back to, give it a stable, plain name and let the system's "date modified" column do the rest.

Setting it up in ten minutes

Write the rule down. Put the pattern and three examples in a short text file called "naming-rules.txt" at the top of your main documents folder. If you work with others, pin it in the shared drive.
Pick your project words. List the 5 to 10 areas you work in most, each as one short hyphenated term: "tax-2026", "client-harlow", "house". Reuse them exactly so they group together.
Rename forward, not backward. Apply the convention to every new file from today. Do not spend a weekend renaming old files. Rename an old one only when you open it for another reason.
Change your scanner and phone defaults. Most scanning apps let you set a name template. Set it to start with the date so scans at least sort correctly.
Add a text shortcut. A snippet that types today's date in ISO format saves effort every time you save. Our guide to text expander snippets shows how to set one up.

Folders still matter, but less than you think

A good file naming convention reduces how much you depend on folders, but it does not replace them. Keep the structure shallow: three levels at most, such as "Work", then "client-harlow", then "invoices". Deep trees of nested folders are where files go to be forgotten, because nobody remembers which branch they chose six months ago.

Once names carry the date and project, you can afford broader folders. A single "invoices" folder holding 300 well-named files is easier to use than twelve monthly folders, since sorting by name already gives you the order. When in doubt, choose fewer folders and better names.

Handling versions and shared files

If your files live in Google Drive, OneDrive or Dropbox, the service already keeps version history, often for 30 days or more. In that case you can skip the version number on files that only you edit and rely on the history instead.

For files that go back and forth with other people, keep the version number and add initials when someone else edits: 2026-10-14_kitchen-refit_quote-brightway_v03-jm.pdf. When something is signed off, do not rename it "final". Move it to a folder called "approved" and leave the name alone. That keeps every link to it working.

Naming is one part of keeping digital work under control. Fewer tools and fewer places to save things make it much easier, which is the idea behind minimalism in tech. And if a messy inbox is where most of your files start their life, setting up email filters keeps attachments sorted before they reach your downloads folder.

Frequently asked questions

What is the best date format for file names?

The ISO format, YYYY-MM-DD, is the best choice. It sorts in true date order as plain text on every operating system and avoids the day-month confusion between countries. Always use leading zeros, so March is 03.

Should I use spaces or underscores in file names?

Use underscores or hyphens instead of spaces. Spaces turn into "%20" in web links, break some scripts and command-line tools, and occasionally cause sync errors. A common pattern is underscores between parts and hyphens between words.

How do I rename lots of files at once?

Windows PowerToys includes a free tool called PowerRename, and macOS Finder can rename a selection of files from the right-click menu. Both let you replace text or add a prefix to many files in one step. Test on a copy of the folder first.