Name Files So Future You Can Find Them
Most file organization problems do not begin with too many folders.
They begin with names like these:
final.pdf final-final.pdf new version.docx image 2.png notes updated.txt
The name makes sense while you are working. A week later, it tells you almost nothing.
A useful file name should answer three simple questions:
What is this?
When was it made or updated?
Which version is it?
A simple pattern works well:
YYYY-MM-DD_project_topic_version
For example:
2026-07-16_website-content-outline_v1.docx
You do not need to use this exact format for every file. The important part is consistency.
Put the Important Word First
If you have several versions of the same kind of file, start with the information you will search for later.
Instead of:
draft_july_website_article.docx
Try:
website-article_2026-07_draft.docx
When files are sorted alphabetically, related items stay together. When you search, the useful words are easier to spot.
Avoid “Final” Until It Is Truly Final
“Final” is one of the least useful file names because it often becomes outdated quickly.
Use version numbers while you are working:
v1 v2 v3
When the work is truly complete, make the name clear:
website-article_2026-07_published.docx
This is easier to understand than trying to remember whether final-final-2 is the real final version.
Make the Name Useful to Someone Else
A good file name should still make sense if you send it to another person or open it six months later.
That means avoiding private shortcuts that only you understand.
“notes for thing” may feel fast today. “customer-support-notes_2026-07” will be much easier to recognize later.
A file name is a small message to your future self.
Write it that way.













