Productivity27 May 2026· 5 min read· Nagy Rudolf

A File Naming System That Still Works in Three Years

Search only helps if you remember a word from inside the file. Naming is what makes documents findable when you do not.

final_v2_REALFINAL_updated(3).pdf is a system too — a bad one. A good convention costs nothing per file and pays back every time you look for something.

The convention

YYYY-MM-DD_project_document_version.ext

2026-03-14_northwind_contract_v2.pdf

Why each part:

  • ISO dates sort chronologically in every file listing, in every operating system.
  • Project before document type groups related files together alphabetically.
  • Lowercase and underscores avoid case-sensitivity and URL-encoding problems.
  • Explicit version numbers beat "final", which is never final.

Use v1, v2, v3 for iterations and reserve a _signed or _approved suffix for the definitive copy.

Folders: shallow and few

Three levels is the practical maximum: area → project → year. Deeper hierarchies mean nobody can predict where a file lives, so everything gets saved to the desktop instead. Anything more granular should be handled by naming, not nesting.

Handling the existing mess

Do not reorganise everything. Create _archive and move all current content into it, then start the new convention today. Files you actually need will surface within a month and can be renamed as they do; the rest can stay archived and searchable forever.

Documents specifically

Standardise on PDF for anything shared or final — convert with Word to PDF — and keep the editable source alongside it with the same base name. Merge related documents into one file rather than keeping five fragments: Merge PDF does it in seconds and halves the number of things to name.

Retention

Decide, once, how long each category is kept: tax documents by statutory period, project files for the contract term plus a year, drafts until the final is approved. Deleting on a rule is much easier than deciding file by file, and less storage means faster search.

FAQ

Spaces or underscores? Underscores or hyphens — spaces break URLs and command-line tools.

Where do dates go? At the front for chronological sorting, unless the project name matters more for grouping.

Should I add tags? Only if every tool in your workflow preserves them; filenames survive everywhere.

Keep reading