File naming conventions that actually last

The three-block rule

An effective file name is made of three blocks, always in the same order: the date, the context, the type. For example: 2026-03-15-atlas-quote.pdf.

Putting the date first guarantees that alphabetical sorting produces chronological order. The context identifies the project or the person. The type says what it is. Three blocks, never more: beyond that, the name becomes unreadable in a File Explorer column.

The date format: YYYY-MM-DD, and nothing else

The ISO format 2026-03-15 is the only one that sorts correctly alphabetically. The common US format 03-15-2026 groups every March together regardless of the year; March 15 2026 puts April before January.

It is also unambiguous internationally, whereas 03/04/2026 means March 4 to an American reader and April 3 to a European one.

Separators and forbidden characters

Use hyphens to separate words, and underscores to separate blocks if you want to distinguish them. Avoid spaces: they complicate command lines, URLs and scripts.

Some characters are simply forbidden by Windows and will make a ZIP extraction fail: ban them, even if your current system tolerates them.

• Forbidden on Windows: \ / : * ? " < > |
• Avoid: accented letters, curly apostrophes, emoji
• Avoid: spaces at the start or end of a name, which are invisible and cause errors
• A safe limit: 80 characters for the name, under 200 for the full path

Handling versions without “final_really_final”

Number versions with two digits: v01, v02, v03. Sorting stays correct beyond ten versions, which is not the case with v1, v2, v10.

For the version you send to a client, do not use “final” — there is always an “after”. Use the date it was sent: 2026-03-15-atlas-proposal-v04.pdf says exactly what was sent and when.

Before and after

The payoff is immediate, and you really feel it six months later, when none of the context is left in your head.

• Scan_20260315_0001.pdf → 2026-03-15-coned-bill.pdf
• final quote v3 (2).pdf → 2026-03-15-atlas-quote-v03.pdf
• IMG_4821.JPG → 2026-07-04-fireworks-003.jpg
• New document.docx → 2026-03-15-atlas-meeting-notes.docx

A convention for a whole team

A team naming convention fits on one page, and that is exactly what makes it workable. Write it down, with three real examples, and pin it at the root of the shared drive.

It must settle the questions that spark debate: the order of the blocks, the separator, how versions are written, the abbreviations allowed for clients. Anything not written down will be done five different ways.

• Block order: date, client or project, type, version
• Separator: hyphens between words, never spaces
• Versions: v01, v02… plus the date sent for delivered versions
• Abbreviations: a fixed list for recurring clients

Names that help search

Windows and macOS search index file names first. A name containing the words you will type later — the sender, the type of document, the project — is found instantly.

Think about the words you will search for, not the ones that describe the file today. “coned-bill” will get searched; “doc-received-this-morning” never will.

What about existing files?

Do not retroactively rename ten years of files: the effort-to-benefit ratio is poor. Apply the convention from today on.

For older files, organizing by date or by topic delivers most of the benefit without touching a single name: location does the job of providing context.