What a good name does
A file name has two jobs. It lets you recognize the file without opening it, and it helps the computer put related files together. Names like “scan0042” or “Document final” do neither. A good name answers a few questions at a glance: what is it, what is it for, and which version is it?
The payoff shows up at predictable moments: when you search for a file you made last year, when you attach the right document to an email, or when a colleague needs to find something while you are away. A few seconds spent at the moment of saving can save minutes later.
None of this requires strict rules. It requires a pattern you can follow without much thought, and the willingness to use it most of the time.
Put the date first, in a sortable format
Dates are the most useful element for sorting. Most systems sort names alphabetically, so a date written as month-day-year, such as 03-15-2026, will not line up chronologically across years. Writing the year first fixes it. The widely used pattern is year, month, day, such as 2026-03-15, which sorts from oldest to newest when the names are listed.
You can shorten it when day-level detail is not needed. A monthly statement might begin with 2026-03, and an annual document might use just 2026. The key is to use the same format everywhere. Mixing styles defeats the sorting.
Not every file needs a date. For documents that are updated in place and replaced over time, such as a template or a reference sheet, a date may only add noise. Use one when the date is part of what makes the file distinct, such as meeting notes, invoices, statements and photos.
Add the project or subject
After the date, include a word or two that places the file in context: a project name, a client, a subject or a category. This part is what you will most likely type into a search box. Choose words that you would naturally think of when looking for the file, rather than internal labels that may be forgotten.
For example, a name might read:
2026-03-15_kitchen-renovation_contractor-quote
Here the date tells you when, the project tells you what it belongs to, and the last part tells you what the document is. Even without opening it, you know what you have.
Choose a separator and stick with it
Spaces work on most systems, but some programs and web services handle them awkwardly. Many people use hyphens between words in the same part and underscores between parts, as in the example above. Others prefer capitalizing each word. Any of these is fine as long as you apply it consistently.
A few extra habits tend to help:
- Avoid special characters such as slashes, colons, asterisks and question marks, which many systems do not allow or treat in unexpected ways.
- Avoid very long names. Folders and paths have length limits on some systems, and long names get cut off in lists.
- Keep to one capitalization style, since inconsistent capitalization can make sorting less predictable.
- Skip words that add nothing, such as “new,” “latest” and “copy.”
Handle versions without losing track
Versioning is where file names fall apart the quickest. Most people have a folder containing a report with names like “final,” “final2” and “really-final.” The words describe your mood, not the order.
Two simple approaches are common.
Version numbers. Add “v01,” “v02” and so on at the end of the name. Using two digits keeps v10 sorting after v09. When you make a significant change, save a new copy with the next number. Minor edits can stay in the same version.
Dates in place of numbers. If you save a new version on separate days, the date at the front already tells you the order. This works well for documents that change on a regular basis, but it can be unclear when you make several revisions in a day.
Avoid the words “final” and “draft” entirely if you can, because they tend to stop being true. If a document goes through approval, you might add a short status such as “approved” at the end, and treat only that one as the reference copy.
When several people edit the same document, agree on a versioning approach together. Some tools keep their own history, in which case saving many copies with different names is unnecessary and can create confusion about which is current.
Match names to folders, without repeating yourself
Names and folders work together. If a file already sits in a folder called “Kitchen Renovation,” you do not need to repeat every detail in the name, but including the project word still helps when the file is attached to an email or downloaded and separated from its folder. A good compromise is to keep the project word and shorten everything else.
A broad folder structure gives files a home, and naming is the part that keeps individual items readable inside it. Between them, the two do most of the work of file organization.
Write the rules down once
A pattern you have to remember is harder to follow than one you have written down. Keep a short note with your template, such as:
YYYY-MM-DD_project_description_v01
and two or three examples. For shared files, put the note in the folder or in a place where everyone can reach it. This is the same idea as team working agreements: a small amount of shared clarity prevents repeated confusion.
A realistic standard
Perfect consistency is not the goal. If you manage to follow your pattern for new work, most of the benefit comes immediately. If a name is awkward or you are in a hurry, save the file first and correct the name later. A slightly imperfect name is still far more useful than “Untitled.”