Why names matter
A file name is the label you see first, in folders, in search results, in email attachments and in the list of files someone else receives from you. Names like “Document1,” “scan0023” or “final_v2_REAL” tell you almost nothing. A clear name lets you identify a file without opening it, and it makes search far more effective.
You do not need an elaborate system. You need a pattern you can apply quickly and consistently, because consistency is what allows files to sort and search predictably.
Start with what you want to know at a glance
Before choosing a pattern, think about what you usually need to tell files apart. Common pieces of information include:
- Date: when the file was created, or the date the content refers to.
- Subject or project: what it is about.
- Type: invoice, notes, report, draft, photo.
- Version or status: draft, reviewed, final.
- Person or organization: who it came from or is for.
Pick the two or three that matter most for the kind of file. Receipts might need date, vendor and type. A project document might need project name, description and version.
Use dates that sort
The most useful trick is writing dates in year-month-day order, such as 2026-11-02. When files are sorted alphabetically, they then appear in chronological order. Formats like 11-02-2026 or “Nov 2” group by month or even by letter, which scrambles the sequence. Use two digits for months and days so that 2026-03 comes before 2026-11 rather than after it.
If a date is part of the name, put it at the start when chronological order matters, as with meeting notes or scans, and later in the name when the subject matters more, as with project files you want grouped together.
Be descriptive but short
A name should describe the content in a few words that you would search for. “2026-11-02_meeting-notes_budget-review” is more helpful than “notes.” But very long names are hard to read and can be cut off in some views, so aim for a short phrase. Avoid filler words and repeated information that the folder already provides. A file inside a folder called “Invoices 2026” does not need “invoice” and “2026” in every name, though some people keep them so the file stays identifiable if moved or sent.
Pick a separator and stick to it
Choose how to separate words and be consistent. Common choices are:
- Hyphens: budget-review-draft
- Underscores: budget_review_draft
- Capital letters at the start of each word: BudgetReviewDraft
Many people use underscores to separate the main parts of the name and hyphens within a part, as in 2026-11-02_budget-review_v02. Spaces are allowed on most systems, but they can cause trouble in web addresses and some software, so separators are a safer habit when files may be shared or uploaded.
Handle versions carefully
Version names are where file naming often goes wrong. “Final,” “final2” and “final_revised” quickly lose meaning. Better options:
- Use numbers: v01, v02, v03. Two digits keep them in order past nine.
- Or use dates: the date of the last change shows which file is newer.
- Reserve words like “draft” and “approved” for status, and use them consistently.
- Keep only the versions you need. Move older ones to an archive folder, or delete them if they serve no purpose.
If you work in tools that keep version history automatically, such as shared documents, you may not need version numbers in the name at all. Use the built-in history instead, which avoids duplicate copies.
Characters to avoid
Some characters cause problems when files move between systems or are uploaded online. It is safest to avoid slashes, colons, question marks, asterisks, quotation marks, angle brackets and the vertical bar, since some operating systems do not allow them. Accented letters and symbols can also display incorrectly on certain systems. Plain letters, numbers, hyphens and underscores work almost everywhere. Also keep the file extension, the part after the final period, since it tells the computer how to open the file.
Write your convention down
A short, written rule removes guesswork. For example:
Date (YYYY-MM-DD) _ subject _ short description _ version
Keep it somewhere you can find it, such as the top of a project folder. If you work with others, agree on it together; a shared convention matters more than which one you pick. This is especially useful for team files and shared documents, where each person’s habits can otherwise create a mess.
Rename in batches when you need to
Most computers offer bulk rename tools that can add prefixes, numbers or dates to many files at once. These are handy for photos and scans. Test on a few files first, and make sure you have recent file backups before renaming a large set.
Pair names with structure
Good names work best alongside a sensible folder structure. Folders give broad grouping, and names give detail. When your names are consistent, you can often skip deep folders and rely on search, because typing a project name and a year will bring up exactly what you want.
Start from now
You do not need to rename your whole history. Apply the convention to new files, and rename older files only when you open them or when they are important. Over time, the portion of your files that follows a consistent pattern will grow.