A simple file naming system that still makes sense six months later

Quick answer: Choose a short, consistent order for the information you search for most. For personal document exports, try YYYY-MM-DD_subject_version.ext. Keep the real extension and test the pattern on a few copies first.
Choose the question your filenames should answer
For receipts, the first question may be “When did I buy it?” For a project, it may be “Which client or room is this?” There is no single best naming rule for every collection. The useful rule is the one that helps you distinguish similar files without opening all of them.
This guide is a suggested organization method for your own standalone documents. Do not bulk-rename system files, application libraries, linked project assets or shared team files without checking their dependencies.
A small example set
| Unclear name | More useful example | Reason |
|---|---|---|
| scan003.pdf | 2026-10-04_desk-receipt.pdf | Date and purpose are visible. |
| final-new.docx | room-plan_v03.docx | A numbered revision avoids repeated “final”. |
| photo-copy.jpg | window-measurement_02.jpg | Subject and sequence distinguish the image. |
These are illustrative names. Use a document’s meaningful date consistently: creation date, purchase date or event date. Do not silently mix those meanings within one collection.
Try the system on five files
- Copy five non-sensitive sample files into a practice folder.
- Write a one-line rule, such as “date, subject, revision”.
- Rename the descriptive portion while preserving the extension.
- Sort by name and check whether the order is useful.
- Search for a subject word and open the result to confirm it is the expected file.
If names become unwieldy, move repeated context into the folder name. A folder called kitchen-renovation does not need every contained filename to repeat that entire phrase.
Handle revisions deliberately
Use v01, v02 and v03 for revisions that you want to keep separately. Record which version was sent in a short delivery note. A file called “final” can become outdated the next day; a version plus a delivery date gives you a clearer record.
Do not put passwords, government identifiers or private account numbers into filenames. Names often appear in screenshots, email attachments and shared links even when the document itself is not open.
Decide when to stop renaming
Once a file has been linked from another document or handed to collaborators, a rename can create extra coordination work. Preserve established names when the benefit is small. For a large archive, begin with new incoming documents instead of reorganizing everything at once. A naming system succeeds when you can maintain it on a busy day.
Related: Keep filename extensions intact · Prepare a delivery folder