A file naming scheme that survives three years

File naming is what survives when a filing system fails, and filing systems fail predictably. The folder tree is beautiful for six months, then two categories overlap, then something belongs in both, then you stop filing and everything lands in Downloads.

Naming survives that, because a name travels with the file. Move it, email it, restore it from a backup years later — the name still says what it is, and no folder structure has to be reconstructed for it to make sense.

The pattern

2026-06-17_acme_invoice-march_v2.pdf
2026-06-17_acme_contract-draft.docx
2026-07-02_internal_expenses-q2.xlsx

Four parts, in this order:

1. ISO date first: `YYYY-MM-DD`. This is the whole trick. Because the components run largest to smallest, alphabetical sorting is chronological sorting, in every file manager, on every operating system, with no configuration. 17-06-2026 and June 17 2026 both sort into nonsense.

Use the date the file is about when that differs from the day you saved it — an invoice dated March, saved in June, is more useful as 2026-03.

2. A short project or client code. Three to eight characters, lowercase, always the same. This is what makes search work: typing acme finds every file for that client regardless of where it ended up.

3. A description, lowercase, hyphen-separated. Enough words to be unambiguous a year later. invoice-march rather than invoice, contract-draft rather than draft.

4. A version, only when versions exist. _v2, _v3. Not final, and certainly not final-final-v2-actual, which is a real pattern that exists because final was never a version number.

Why lowercase and hyphens

• Case is unreliable. macOS and Windows treat filenames case-insensitively; Linux does not. Mixed case produces duplicates that look identical and behave differently.
• Spaces break things. They need quoting in every command line, they become %20 in URLs, and they survive email attachments badly.
• Underscores separate the fields, hyphens separate the words. Adopting this consistently means you can split a filename programmatically later, which matters the day you have four hundred of them.
• No punctuation beyond those two. Slashes, colons and question marks are illegal or reserved somewhere, and you will find out during a migration.

What folders are still for

Not categories — stages. A small number, and the same everywhere:

active/      work in progress
archive/     finished, by year
reference/   things you consult but do not change

Three top-level folders and good names beats a fifteen-level tree, because a stage is unambiguous — a thing is either finished or it is not — while a category is a judgement call you will make differently next month.

Renaming what you already have

Do not do it by hand.

• macOS Finder: select files, right-click, Rename — it does find-and-replace, sequential numbering and text insertion across the selection.
• Windows PowerToys PowerRename offers the same with regular expressions and a live preview of the result.
• Command line: rename on Linux, or a short loop, for anything the graphical tools cannot express.

Whatever you use, preview before applying and work on a copy the first time. Batch renaming is fast in both directions and there is no undo once it has run.

Do not convert your entire history. Rename what you actually reopen, and apply the scheme to everything new. The archive can stay as it is; you are optimising for the files you will look for, and those are mostly recent.

The dates that break the pattern

Some files carry their own natural identifier that beats a date: an invoice number, an order reference, a case number. When a canonical identifier exists, use it after the client code — 2026-03-14_acme_inv-40122.pdf — so you keep chronological sorting and gain exact search.

The measure of a naming scheme is not how it looks in the folder today. It is whether you can find one file in five thousand, in three years, by typing two words you would actually remember.

What makes a file naming scheme work?

File naming is a rule for constructing names so that sorting and searching do useful work without a folder structure. It works when the name alone answers three questions — when, what, and whose — because a name travels with the file and a folder does not.

Why does the date go first?

Only rows 1 and 5 sort correctly in every file manager on every system, and row 1 stays readable. That is the whole argument for ISO 8601, and it is why the date leads.

What breaks a naming scheme?

• Mixed case. macOS and Windows treat names case-insensitively; Linux does not. The result is duplicates that look identical.
• Spaces. They need quoting on every command line and become %20 in URLs.
• `final`. It is not a version number, which is how final-final-v2 happens.
• Punctuation beyond hyphen and underscore. Slashes, colons and question marks are illegal or reserved somewhere.

How do you rename what you already have?

Not by hand. macOS Finder renames a selection with find-and-replace and sequential numbering; PowerRename does the same on Windows with a live preview and regular expressions.

Preview before applying, and work on a copy the first time — batch renaming is fast in both directions and has no undo. Then rename only what you actually reopen and apply the scheme to everything new. See digital workflows, file tools and guides.

What folders are still for

Not categories — stages. A small number, the same everywhere: active for work in progress, archive for finished work by year, reference for things you consult but do not change.

Three top-level folders and good file naming beats a fifteen-level tree, because a stage is unambiguous — a thing is either finished or it is not — while a category is a judgement you will make differently next month.

When a file has its own identifier

Some documents carry a canonical reference that beats a description: an invoice number, an order reference, a case number. Use it after the project code — 2026-03-14_acme_inv-40122.pdf — so you keep chronological sorting and gain exact search.

The measure of a file naming scheme is not how tidy the folder looks today. It is whether you can find 1 file among 5,000, in 3 years, by typing 2 words you would actually remember. Everything above is in service of that single test, and nothing else about the scheme matters.

Why this survives three years

Because a name travels with a file and a folder does not. Move it, email it, restore it from a backup in 2029 — the name still says when, what and whose, with no tree to reconstruct.

That is the whole argument for putting effort into file naming rather than into filing. Folders describe where you decided something belonged on the day you saved it; names describe what the thing is, which does not change.