Should every file name really start with a date?

No — only when you’ll want to scan or sort that folder by time, which covers most documents that arrive on a schedule (invoices, statements, notes, job photos). For reference material, templates, or a CV, lead with the subject instead. The rule is “date first when time is the axis,” not “date on everything.”

Why year-month-day instead of the way I write dates?

Because computers sort names as text, and only YYYY-MM-DD makes the text order match the time order. 15-03-2026 sorts by day, and a spelled-out month sorts alphabetically — both scramble a folder. ISO order also reads the same in every country, so no one mistakes the 3rd of April for the 4th of March.

What do I do about versions, then, if I can't write "v2"?

Let dates carry the history. Keep dated snapshots side by side — 2026-03-15_report.docx, 2026-03-20_report.docx — and the newest sorts to the bottom on its own. The working file’s name stays about what it is; the date says when. That’s cleaner than a chain of “final” that stops being true.

Are spaces in file names actually a problem?

On your own machine, rarely. The trouble starts when a file syncs to the cloud, gets emailed, becomes a link, or passes through a tool that turns spaces into %20. Using a hyphen or underscore instead is a small habit that simply never bites you later — which is the whole test of a good convention.

How do I fix hundreds of badly named files without days of work?

In bulk, not by hand. Select them and use batch renaming to find-and-replace, strip junk, change case, and number them in a single pass — with a preview of every result first. Then set an automatic rule to date-stamp whatever arrives next. The past is cleaned once; the future stays clean on its own. Available now on the Microsoft Store.

File naming conventions: a system that lasts

You already know how to name a file well — today. You give it a name that makes perfect sense right now, because right now you remember the client, the project, the reason. The trouble is that a name has to keep making sense long after “right now” is gone: when a folder of two hundred of them gets sorted by a machine, when a coworker opens the drive, when you come back in three years with none of the context still in your head.

Most naming advice is a habit for today. What you actually want is a system — a small set of rules that keep a name readable when you’re not there to explain it. That’s what this is: the handful of conventions that make names survive sorting, time, and other people, plus how to stamp them onto the files you already have.

What a file name is actually for#

A name is not decoration, and it’s not a description — it’s an address and a label. It has two jobs: help the right file surface when you search or sort, and tell you what’s inside without opening it. Every rule below comes from those two jobs. If a naming choice doesn’t help you find the file or read it at a glance, it’s just typing.

Principle 1 — Let the date lead, and write it backwards#

When chronological order matters — invoices, contracts, meeting notes, photos of a job — put the date at the front of the name, and write it year first: 2026-03-15, not 15-03-2026 or March 15. There’s one reason, and it’s decisive: computers sort names as text, character by character, left to right. Written year-month-day, the text order is the time order. A folder sorted by name falls into perfect chronological order on its own — no “sort by date modified” that a copy or an edit can quietly scramble.

Write 15-03-2026 and the same folder sorts by day-of-the-month — every 1st of every year clumped together, nonsense. Write the month as a word and it sorts alphabetically: April lands before January. The ISO order (YYYY-MM-DD) is the only one that sorts right, reads the same in every country, and never needs a second thought. 2026-03-15_contract-acme.pdf files itself.

When the date genuinely doesn’t matter — a folder of reference material, your CV — don’t force one in. Lead with the subject instead. The date goes first only when time is the axis you’ll want to scan by.

Principle 2 — A name describes the thing, not its history#

This is the rule that saves the most grief. report-final.docx, report-final-v2.docx, report-final-FINAL.docx, report-final-FINAL-actually.docx — everyone has lived this. The mistake is trying to record the file’s history in its name. A name should say what the file is, not what happened to it. “Final” is a claim that turns false the moment you edit again. “v2” is a version number the file itself already tracks with its modified date.

So: no final, no latest, no new, no copy, no v2/v3 baked into the name of your working document. If you truly need to keep old versions, that’s what a dated snapshot is for — 2026-03-15_report.docx and 2026-03-20_report.docx sit side by side, sorted, and the newest one is obvious without a single “final” in sight. The date carries the history; the name carries the meaning.

Principle 3 — Consistency beats cleverness#

A system is only a system if it’s the same every time. Pick one separator and one case, and stop improvising. The safe choices, and why:

Separators: a hyphen - between words, an underscore _ to divide the big blocks — date_subject-detail. Both survive everywhere.
Spaces: skip them for anything you might sync, upload, script over, or turn into a link — spaces get mangled into %20 and trip up other tools. In a purely local folder they’re harmless; the habit of avoiding them just never bites you.
Case: lowercase is the calm default. It sidesteps the fact that some systems treat Report.pdf and report.pdf as the same file and some don’t.
Accents and symbols: fine on your own machine, risky the moment a file crosses to another OS, a cloud, or a colleague. When in doubt, plain letters travel furthest.

None of this is about being fussy. It’s about a name that behaves the same in your folder, in an email, in a backup, and on someone else’s computer.

Principle 4 — Short and specific beats long and complete#

A name is a label, not a summary. Three to five meaningful words is plenty; the file’s contents hold the rest. And front-load the word that sets this file apart from its neighbors — the part your eye, and the search box, reaches first. In a folder of contracts, acme earns the front more than contract does, because everything there is already a contract. Distinguishing word first, generic word later, or not at all.

2026-03-15_acme-lease-signed.pdf beats Signed copy of the final lease agreement for the Acme account March 2026.pdf on every count: it sorts, it scans, it fits, and it says exactly as much as you need.

Do

Lead with an ISO date (2026-03-15) when order matters
Name the thing: subject first, then the distinguishing detail
Pick one separator and lowercase — and keep them everywhere
Keep it to a few specific words

Don't

Bury versions in the name (final, v2, FINAL, copy)
Write dates as 15-03-26 or "March" — they sort wrong
Lean on creative spaces, accents, or symbols
Write a whole sentence when a label will do

One formula you can memorize#

Most files fit a single shape: [date]_[subject]-[detail]. 2026-03-15_invoice-chase-paid.pdf. 2026-02_notes-kickoff-acme.md. Drop the date when time isn’t the axis; drop the detail when the subject is enough. It isn’t a law — it’s a default that makes the next name obvious, which is the whole point of a system: you stop deciding and start typing.

Applying the system to the mess you already have#

Here’s the honest part. Rules are easy going forward; the pain is the thousand files already named badly. You are not going to fix those one at a time — and you shouldn’t. This is exactly where a file explorer earns its keep, in two moves.

For the backlog — rename in bulk. Select the badly named pile and fix it in one pass: strip the -final-FINAL, swap DSC for a real subject, force everything to lowercase, add sequential numbers — all with a live before/after preview, so you approve every new name before a byte moves. The mechanics, and the safe way it can even swap names between two files, are a guide of their own: batch renaming files with rules.

For everything arriving from now on — let a rule stamp the date. The one thing bulk renaming won’t do is insert a date, and dated names are the heart of Principle 1. That’s a job for an automatic rule with a name pattern like {year}-{month}-{day}_{name}, which turns report.pdf into 2026-03-15_report.pdf the moment it lands — and for photos, {capture-date} uses the day the picture was actually taken. The full token list, and the traps, live in the file placeholders guide.

Together they close the loop: the bulk tool cleans the past, the rule keeps the future clean, and your system holds without you policing it. It all runs on your PC — no account, nothing uploaded.

Messy namesRename in bulkRule stamps the dateSorts itselfFound in seconds