Naming Files Like a Professional
File naming feels like a small thing until you're searching for a specific document six months later among a hundred similarly vague filenames. A consistent convention, applied from the start, is one of the highest-return habits in personal file management.
Start with a date, in a format that actually sorts correctly
Using YYYY-MM-DD (2026-09-14, not 09-14-2026) at the start of a filename means files sort chronologically by default in any file browser, without needing a separate date column or manual reordering. This single habit does more for long-term findability than almost anything else in this list.
Follow the date with a specific, descriptive label
"Report.docx" tells you nothing six months from now; "2026-09-14-q3-marketing-report.docx" tells you everything at a glance, without opening the file. The extra ten seconds spent being specific at save time saves much more time later, across every future search for that file.
Retire "final" and "v2" in favor of real versioning
final, final-v2, final-FINAL, and actually-final are the clearest sign a naming system has broken down — usually because there was never a real plan for how versions would be distinguished. A simple incrementing version number (v1, v2, v3) or, more simply, just relying on the date to distinguish versions (since a later date is unambiguously more recent) both work far better than ad hoc "final" labels that stop meaning anything after the second revision.
Avoid special characters and inconsistent capitalization
Spaces, slashes, and special characters in filenames can cause problems in some software and systems, and inconsistent capitalization (SomeFile.pdf vs somefile.pdf vs SOME_FILE.pdf) makes files harder to scan visually as a group. Picking one consistent style — lowercase with hyphens is a common, safe default — and sticking to it makes a folder of files much easier to read at a glance.
Keep the convention simple enough to actually follow
An elaborate naming scheme with a dozen required fields will get abandoned under time pressure. Date, short description, and (if relevant) a version — that's enough structure to be genuinely useful without being so cumbersome that it stops happening consistently.
Once files are named consistently, they're also easier to combine when needed — Merge PDF is useful for consolidating a clearly-named set of related documents into a single file per project or year.