How to Name Files So You Can Find Them Later
A simple file naming system for work, school and shared projects. Learn what to include, which separators to use and how to avoid names that break across devices.
Published November 14, 2026 · By Sudip Bhowmick
A file called final.docx tells you very little a week later. A name like 2026-11-14-client-proposal-v2.docx tells you when it belongs, what it contains and which draft you are looking at. A small naming habit saves time every time you search, share or sort a folder. Here is a system that works for ordinary documents as well as team projects.
Put the Most Useful Details in the Name
Start with the information you are most likely to search for: a project, client, subject or document type. Add a date when timing matters, then a short status or version if you expect revisions. Keep the words specific enough to tell similar files apart.
- ▸Good: 2026-11-14-website-copy-homepage-draft.docx
- ▸Hard to scan: new copy latest final2.docx
- ▸For recurring reports, use a consistent order such as date, team, subject and version.
Use Dates That Sort Correctly
Write dates as YYYY-MM-DD when you want files to sort chronologically by name. The year comes first, followed by month and day, so 2026-02-03 sorts before 2026-11-14. A format such as 03-02-26 can be ambiguous and may sort in an unexpected order.
For a file that is not tied to a specific day, leave the date out. A date that adds no useful context just makes the name longer.
Choose Separators for People and Software
Spaces are comfortable for documents opened by people. For files used in websites, code, URLs or command lines, lowercase words joined with hyphens are usually easier to handle. Avoid mixing separators within the same project unless there is a reason.
If you need a code-friendly version, turn a phrase into kebab-case, such as product launch notes becoming product-launch-notes. The Kebab Case Converter can do this for a list of names at once.
Avoid Characters That Cause Trouble
Some punctuation is accepted by one operating system and rejected by another. Keep names portable by avoiding characters such as \, /, :, *, ?, ", <, > and |. A colon in a file name may work on one computer but fail when the same file is moved to Windows.
Accents and non-English letters are fine in many modern systems, but simpler names can be easier to type into older tools or URLs. Keep the original title inside the document when a plain filename would lose important meaning.
Replace Confusing Version Names
Names such as final, final-new and final-revised do not tell you which copy is current. For files with frequent edits, use a numbered version or a clear status: proposal-v03.docx, proposal-approved.docx. If several people edit the same file, a shared document history is safer than sending renamed copies back and forth.
Do not rename a file approved by a client or a system that expects an exact name without checking first. Some processes depend on the original filename.
A Quick Naming Checklist
Before saving or sharing, check that another person could identify the file without opening it.
- ▸Does the name say what the file contains?
- ▸Is the date in a consistent, sortable format, if needed?
- ▸Can someone tell a draft from an approved copy?
- ▸Will the name work on the devices and services your team uses?
- ▸Can you remove a filler word without losing useful context?
Conclusion
A dependable filename is short, specific and predictable. Put searchable details first, use sortable dates when they help, and choose separators that match how the file will be used. Apply the same pattern to a whole folder and finding the right copy gets much easier.
Free Tool
Convert words to kebab-case