The most useful file naming conventions best practices come down to three goals: files should sort in a sensible order, open on any computer, and be recognizable without opening them. In practice that means putting a date in YYYY-MM-DD format first or near the front, using only letters, numbers, hyphens, and underscores, and adding a version number with leading zeros.
The rest is consistency. A simple rule that everyone follows beats a clever rule that nobody remembers. Below are nine practices, a comparison of good and bad names, and a template you can adapt in five minutes.
Good and bad file names side by side
| Weak name | Better name | What changed |
|---|---|---|
| final report NEW (2).docx | 2026-11-03_quarterly-report_v03.docx | Date first, clear topic, real version number |
| IMG_4821.jpg | 2026-10-14_kitchen-renovation_before_012.jpg | Context and sequence added |
| Invoice?.pdf | 2026-09_invoice_acme-supplies_00482.pdf | Reserved character removed, supplier and number added |
| notes.txt | 2026-11-05_client-onboarding_meeting-notes.txt | Recognizable in search results |

The 9 best practices
1. Use YYYY-MM-DD dates
Year, month, day is the ISO 8601 order, and it is the only date format that sorts correctly as plain text. “2026-01-15” lands before “2026-02-01” in every file manager. “15-01-2026” or “Jan 15” do not. If you need time too, Harvard Medical School’s file naming guidance suggests the compact form YYYYMMDDThhmm.
2. Put the most important element first
Whatever you sort by most should lead the name. For photos and meeting notes that is usually the date. For client work it may be the client or project code: “acme_2026-11-03_proposal_v02.pdf” groups all Acme files together.
3. Avoid spaces and special characters
Spaces turn into “%20” in web links and cause trouble in scripts. Symbols such as # % & and accents break some upload forms and sync tools. Use hyphens between words and underscores between elements, or camelCase if your team prefers it.
4. Never use characters Windows reserves
Microsoft’s documentation on naming files in Windows lists characters that cannot appear in a file name: < > : ” / \ | ? *. It also reserves names such as CON, PRN, AUX, NUL, COM1, and LPT1, even with an extension, and says a name should not end with a space or a period. A file named on a Mac with a colon or a question mark can fail to copy to a Windows machine or a shared drive.
5. Keep names reasonably short
Long names inside deep folder structures can hit path length limits. Older Windows setups cap a full path at 260 characters unless the limit has been lifted. Harvard’s guide recommends 40 to 50 characters for the name itself, which is a sensible target rather than a rule.
6. Number versions with leading zeros
Use v01, v02, v03 rather than v1, v2, v10, which sort as v1, v10, v2. The same logic applies to sequences: 001, 002, 010. Reserve the word “final” for nothing. There is always a later version.
7. Use words people would search for
Name files with the terms you would type into a search box months later: “lease-renewal” rather than “doc-for-landlord”. This matters more than folder structure on cloud drives, where most people search instead of browsing.
8. Stick to lowercase, or one clear case rule
Some systems treat “Report.pdf” and “report.pdf” as different files and others do not. Lowercase everywhere avoids duplicates when files move between Mac, Windows, Linux servers, and cloud storage.
9. Write the convention down
A short README file in the shared folder, with the pattern and two examples, keeps a team consistent. New people copy what they see, so fix the oldest badly named files first.
A template you can copy
For most personal and small-team files, this pattern covers nearly everything:
YYYY-MM-DD_project-or-client_description_v01.ext
- 2026-11-13_website-redesign_homepage-copy_v02.docx
- 2026-10-30_taxes_property-tax-receipt.pdf
- 2026-11-01_garden_tomato-bed_004.jpg
Drop the parts you do not need. A receipt rarely needs a version number; a design file almost always does. If you want a quick way to generate names in this format, the article on organizing files and tasks for productivity includes a small file name builder.

Applying a convention to old files
- Start with active projects only. Archives can wait or stay as they are.
- Rename as you touch files rather than in one exhausting session.
- For photos, use the batch rename tools built into your system: on a Mac, select files in Finder and choose Rename; on Windows, select files and press F2 to give them a shared base name with numbers.
- Compress finished project folders once they are renamed, following our notes on file compression techniques, so archives stay small and tidy.
Shared drives add one more consideration: renaming a file that others link to can break their shortcuts on some platforms. Our comparison of cloud platforms for file management notes how each service handles shared links and versions.
FAQ
Should I use underscores or hyphens in file names?
Both are safe. A common approach is hyphens between words and underscores between the main parts of the name, which keeps each part readable.
What is the best date format for file names?
YYYY-MM-DD or YYYYMMDD. Both follow ISO 8601 and sort chronologically in any file manager.
How long should a file name be?
Short enough to read at a glance, often under 50 characters. Very long names inside deep folders can exceed path limits on some Windows systems.
Which characters should never be used in file names?
Avoid < > : ” / \ | ? * entirely, and avoid spaces, accents, and symbols such as # % & if files will move between systems or be uploaded.
Start with one folder
Pick the folder you open most this week, apply the template to new files only, and see whether search feels faster after a few days. If it does, extend the rule to the next folder. Naming is one part of a calmer system; the guide to building a high-efficiency daily workflow shows how it fits with capture, focus time, and an end-of-day reset.

Roger Simas is the researcher and editor behind SHP Digital Atelier. He has no formal IT certification; his work is reading official documentation, plan pages, and help centers, comparing limits and real costs, and turning what he finds into practical guides about files, workflows, and SaaS tools. Corrections from readers are welcome at contact@ateliershp.com.
