File-naming conventions that make files findable

File organization · 5 min read

Most file chaos is not a storage problem — it's a naming problem. When filenames are vague, inconsistent, or full of "final" and "final2," the only search strategy left is opening things one by one. A simple naming convention fixes most of it, and it costs nothing.

What a good filename does

A good filename answers three questions at a glance: what is this, when is it from, and which version is it. If you can answer those without opening the file, your naming is working.

The anatomy of a solid filename

Pick an order for the parts and keep it the same everywhere. A pattern that works well for most documents:

YYYY-MM-DD_project_description_v01.pdf

• Date first (YYYY-MM-DD): files sort chronologically in every file browser, no custom sorting needed. Never use MM-DD-YYYY or DD-MM-YYYY — they sort wrong and confuse people across regions.
• Project or topic: one or two words that say what the file belongs to.
• Short description: what the file actually is. Be specific enough that you don't have to open it.
• Version number: v01, v02, and so on. Numbers beat words — everyone knows v03 is newer than v02, while "final" vs. "final_v2" vs. "final_FINAL" tells you nothing.

A real example: 2026-09-20_garage-sale_inventory_v03.xlsx is instantly understandable. Book1 (2).xlsx is not.

Versioning rules that actually hold

Decide one versioning scheme and use it for everything:

• Use v01, v02 (two digits, leading zero, so files sort correctly).
• Only the newest version keeps the version number if you prefer — some teams rename the current draft without a version and only number the milestones. Either way, pick one.
• Never use "final" in a filename. There will always be another final.
• When a version is superseded, either move it to an archive subfolder or mark it clearly — don't leave five competing versions in the same folder.

Characters to avoid

Stick to letters, numbers, hyphens, and underscores. Avoid:

• Spaces: they work on modern systems but still break older tools and make command-line work annoying. Use hyphens or underscores instead.
• Slashes, backslashes, colons, asterisks, question marks, quotes: these are reserved or problematic on some operating systems.
• Special characters and emoji: they don't survive every transfer method and they break search in unexpected ways.
• Excessive length: some systems and cloud sync tools struggle with very long paths. Keep names descriptive but compact — under 60 characters is a safe habit.

Folders carry the big structure; names carry the detail

Don't repeat the folder name in every filename — that's what the folder is for. If the folder is 2026-taxes, the file doesn't need to be 2026-taxes_2026-09-20_receipt.pdf. It can just be 2026-09-20_receipt.pdf. The folder provides the context; the filename provides the specifics.

Write it down, then actually use it

A convention nobody can see isn't a convention. Write your scheme in one short document — a few lines with two or three examples — and put it somewhere people will find it:

• For a household: tape it to the inside of the file cabinet, or pin it in a shared note.
• For a team: put it in the shared drive's top-level folder as a readme.
• Include examples for the file types you actually use: invoices, photos, contracts, receipts.

Then the harder part: rename new files as you create them. Don't try to rename ten years of backlog in one weekend — apply the scheme going forward, and rename old files only when you touch them. Consistency from today onward beats a perfect archive.

Back to all guides →