File names are the cheapest organization system there is, and the one most people neglect. A consistent naming habit means you can find any file in seconds, sort a folder into a sensible order, and share files without confusing the recipient. The rules are simple enough to learn in ten minutes.
The four goals of a good name
- Descriptive: the name tells you what the file is without opening it.
- Consistent: the same pattern is used every time, so you know where to look.
- Sortable: files appear in a useful order automatically.
- Portable: the name works on every system and survives being emailed, uploaded or synced.
Put dates first, in year-month-day order
Write dates as year, then month, then day, for example 2026-09-21. This is the international ISO format, and it has a big advantage: alphabetical order and chronological order become the same thing. A folder of files starting with 2026-01, 2026-02 and 2026-03 sorts correctly in every application, whereas dates written as 21-09-2026 sort by day first and scramble the timeline.
Avoid characters that cause trouble
Some characters are forbidden on certain systems, and others cause errors when files are shared, uploaded or used in web addresses. As a rule, avoid the backslash, slash, colon, asterisk, question mark, quotation marks, angle brackets and the pipe symbol. Also avoid leading and trailing spaces, and stick to letters, numbers, hyphens and underscores where you can.
- Use hyphens or underscores instead of spaces. It avoids problems with links and command-line tools.
- Keep names reasonably short. Windows has a default limit of 260 characters for a full file path, and long folder names use it up quickly.
- Don't rely on capital letters to distinguish files. Some systems treat 'Report.pdf' and 'report.pdf' as the same file, and others as different ones.
Before and after
| Before | After |
|---|---|
| Final final v2 (1).docx | 2026-09-21_Acme_Proposal_v03.docx |
| IMG_4432.JPG | 2026-08-15_Goa_0432.jpg |
| scan0012.pdf | 2026-07-03_Rent-Agreement_Signed.pdf |
| notes new.txt | 2026-09-10_CS101_Lecture-Notes_Week4.txt |
| Invoice 5 March.pdf | 2026-03-05_Invoice_1042_Acme.pdf |
Handling versions
'Final' is a myth. The moment you call something final, someone asks for a change. A better approach is to use version numbers for milestones you share outside the team, and rely on your storage service's version history for everything in between.
- Use two-digit numbers, v01, v02 and so on, so that v10 sorts after v09 instead of after v1.
- Reserve version numbers for files you actually send to someone. Drafts stay under version history.
- If you need a status, add it as a word: _draft, _review, _approved.
Number things with leading zeros
Without leading zeros, 10 sorts before 2, because the computer compares characters one at a time. Writing 01, 02 and 10 keeps things in order. The same applies to photo sequences and chapters.
Decide once, write it down
A convention only works if everyone uses it. If you work with other people, put a short note in the root folder that explains the pattern, with two or three examples. It takes five minutes to write and saves endless questions.
Renaming in bulk
- On Windows, the free PowerToys utility includes PowerRename for changing many names at once.
- On macOS, Finder can batch-rename a selection of files from the right-click menu.
- Most photo managers can rename images by date on import, which handles camera files automatically.
Adopt the pattern for new files and don't try to fix your entire archive at once. Rename files when you touch them, and within a few months most of what you use will follow the same simple rules.