How to name files so you can find them again
You know you saved it. You remember what it was for. But the filename is something like Document (3) or proposal_final_REVISED, and now you’re opening files just to see what’s inside.
Good file names close that gap. They connect what you’ll remember later with what you can actually search for.
If you’re wondering how to name files, start with this: describe what the file is, add a meaningful date when useful, and include a version only when you need to distinguish revisions. Keep the pattern simple enough to use on a busy day.
You don’t need to rename your entire digital life. Start with the files you struggle to find regularly.
Put the words you remember in the name
A filename should make sense without opening the file. It should also make sense outside its current folder, because files get downloaded, emailed, and moved.
Notes.docx tells you almost nothing. Maple-Street-Kitchen-Planning-Notes.docx tells you the project and the purpose.
Choose words you would naturally type into a search box:
The client, project, property, or person involved.
The type of document, such as invoice, agreement, or meeting notes.
A distinguishing detail, such as the room, event, or reporting period.
Skip private shorthand unless everyone using the files understands it. MS-KP may feel efficient today, but “Maple Street kitchen” will probably be easier to remember later.
Be specific without turning the filename into a paragraph. Include enough to separate it from similar files, not every fact inside it.
Use a small pattern, not a complicated code
A useful starting pattern is:
Topic-Document-Type-Date-Version.ext
Not every file needs every part. For example:
Maple-Street-Kitchen-Measurements.pdf
Maple-Street-Meeting-Notes-2026-04-09.docx
Maple-Street-Kitchen-Proposal-v03.docx
Consistency matters more than whether you prefer spaces, hyphens, or underscores. Pick a readable separator and use it consistently within the same collection.
For names that travel well between computers and cloud services, stick mostly to letters, numbers, and simple separators. Avoid punctuation such as slashes, colons, question marks, and asterisks, which some systems won’t accept. Keep names reasonably short; long folder paths can also cause problems.
Leave the file extension alone. The ending, such as .pdf, .jpg, or .xlsx, helps software recognize the file type. Changing it doesn’t convert the file. If your computer hides extensions, don’t add another one while renaming.
Choose dates that mean something
When a date helps identify a file, use YYYY-MM-DD. That format avoids confusion between month-first and day-first dates and sorts chronologically when placed at the beginning of a filename.
But decide what the date means. Is it the meeting date, invoice date, event date, or reporting period?
For meeting notes, use the meeting date. For a monthly statement, the year and month may be enough:
2026-04-Bank-Statement.pdf
Don’t automatically use the day you downloaded something. A statement downloaded in May may still belong to April. Future searches will probably follow the statement period, not the download date.
Put dates first when you usually browse a sequence, such as monthly reports. Put the topic first when you usually look for a project or document type.
Also, don’t rely entirely on “date created” or “date modified.” Those details can change when you copy, download, or edit. A meaningful date in the name gives you another way to recognize the file.
Try the pattern on one real problem
Before renaming a large collection, test your pattern on a small group you actually use. Recent invoices, an active project, or household records are good candidates.
Ask yourself: could I identify each file from its name alone? Would I know what to search for next month? Does the pattern still make sense when the file leaves its folder?
If the naming decision keeps getting tangled up with duplicate copies, shared drives, or competing folder systems, that’s a useful sign that names are only part of the problem.
Take the 2-minute organization test or book a free 20-minute discovery call at Tidy Haus. A digital organizing consultant can share a few hints or quick fixes and help you shape a clear plan or proposal you can use with Tidy Haus or on your own, at your pace and with your resources.
Replace “final” with versions and clear status
“Final” describes an intention, not a reliable version. Once another change arrives, you’re stuck with final-new, final-final, or a file whose name no longer matches reality.
For separate working copies, use a simple sequence:
Kitchen-Proposal-v01.docx
Kitchen-Proposal-v02.docx
Kitchen-Proposal-v03.docx
Leading zeros help filenames sort predictably as the sequence grows.
When a real milestone matters, name that status rather than calling everything final:
Kitchen-Proposal-Approved-2026-04-09.pdf
Kitchen-Agreement-Signed-2026-04-12.pdf
Only use “approved” or “signed” when it’s true. Keep signed or issued documents separate from editable working drafts so you don’t accidentally overwrite the record.
If you collaborate in a cloud document with version history, you may not need a new file for every edit. Agree on one working document and use its history for revisions. Verify that history is available to the people who need it; downloaded copies may not include it.
Know when folders beat search
Search is useful when you remember a distinctive word. Folders are useful when you need to see a complete set, understand context, or separate active work from records.
A folder often beats search when you need:
Everything for a tax year, rather than one receipt.
All documents for a property sale or project handover.
A clear boundary between current work and archived material.
A shared place where other people know what belongs.
Use folders for broad context and filenames for the details. A Home / Kitchen Renovation / Agreements folder gives you a place to browse. Maple-Street-Kitchen-Agreement-Signed-2026-04-12.pdf still identifies the document when it’s attached to an email.
Avoid building so many nested folders that saving a file becomes a guessing game. If you repeatedly hesitate between two locations, the categories may overlap too much.
And remember: a folder name is not access control. Calling something “Private” doesn’t restrict sharing. Check actual permissions, and avoid putting sensitive identifiers in filenames that may appear in notifications or shared links.
Make the rule easy to keep
Write your naming pattern somewhere visible in the folder or shared workspace. Include an example and explain what the date represents. For shared files, agree on who updates versions and where approved copies live.
Apply the rule to new files and the older ones you touch regularly. Leave a large archive alone unless its names are causing a real problem.
Before renaming files used by other software, check whether their names are required. Renaming linked spreadsheets, website assets, or application-managed files can break references. If you’re unsure, test changes on copies.
The practical test is simple: can you recognize the file, distinguish it from nearby versions, and put it somewhere predictable? A naming rule that does those things is useful—even if the rest of your drive still needs attention.
Still struggling? Let's find your next step
You don't have to figure everything out alone. Take our 2-minute organization test, or book a free 20-minute discovery call with Tidy Haus.
Here is what you get from your discovery call:
20 minutes with a digital organizing consultant, at no cost to you.
A plan/proposal with solutions for moving forward that you can use with Tidy Haus or without us.
A couple of hints or quick fixes we can show you on the call.
A clear, coherent, and organized plan for moving forward at your pace, with your resources.
Book your free discovery call and let's work out a way forward that fits you.
