Year first, and the folder sorts itself
Name a file 2026-08-29-lease.pdf and the folder becomes a timeline. Why year-month-day beats the date column, which changes when files move.
Assembled from filing arguments spanning thirteen years — office workers, students with rejected submissions, people who scan old family paperwork. No software is endorsed here; the one standard cited is public.
There is a way to name a file so that it files itself. Put the
date at the front — year, then month, then day —
2026-08-29-lease-renewal.pdf — and stop. No app, no system, no
weekend of reorganizing. Just that.
Start a file’s name with its date — four-digit year, then two-digit month, then two-digit day — and an ordinary alphabetical sort will list your files in date order, on any computer, decades from now.
The trick is entirely in the ordering. Alphabetical sorting
compares names left to right, so date order and alphabetical order
only agree when the biggest unit comes first: year, then month,
then day. Write the month first and January 2025 files in with
January 2019. Year first, every folder becomes a timeline. It also
ends a quieter problem: 03-01 means January 3rd in one country
and March 1st in another, but 2026-03-01 means one single day
everywhere on earth. This isn’t a folk convention — year-month-day
is the international date standard, ISO 8601, and it holds that
title in 2026.
The deeper reason to do it is that the alternative is quietly broken. Your computer already shows a “date modified” column, and it feels like the same thing for free. It isn’t, because those dates belong to the file system, not to the file — and routine operations rewrite them. Copy files to a new laptop and the copies may all be “created” today. Cloud sync, backup restores, even opening a file in the wrong program can stamp fresh dates over the old ones. People who managed files across machines for years describe the same discovery: the column they trusted had been silently rewritten in transit. And some dates were never in the metadata at all — one person who scans old family paperwork put it simply: a letter written in 1938 and scanned in 2022 gets filed as 2022 unless the name itself says otherwise. The name is the one date field no sync engine or copy operation rewrites behind your back.
A few placements matter. The date goes at the front when time is how you’ll look for things — receipts, statements, scans, assignments. When what the file is about matters more, the date can trail the name instead: one person who photographs people puts the person’s name first with the date behind it, and another keeps the date at the end as a version marker so drafts of the same document still group by title. Both keep the habit’s core: the date lives in the name, where nothing can rewrite it.
Two kinds of files sit outside this page. If your files are a phone camera roll and a dozen documents a year, this solves a problem you don’t have — the trick earns its keep at volume, for people juggling recurring reports, scans and versions over years. And if the files are source code, don’t date the names at all: version control exists precisely to keep changes with their history, and filename dating there is the amateur version of a solved problem.
The habit costs ten seconds at the save dialog, which is the whole price. Files named this way need no software to organize them and no memory to find them — the folder does it, every time it opens.
The community disagrees on this one
People who care about finding files later split on whether the date belongs in the name at all.
Write the date into the name
This camp has been burned: the computer's date fields changed under them when files were copied to a new machine, pulled down from cloud storage, or restored from a backup — and the original order was gone. A date in the name survives the moves and syncs that scramble metadata, travels across systems, and means the file explains itself even when it's alone in an email attachment.
3 independent accounts
The date column is already there
This camp points at the file window itself: one click on the date header sorts everything chronologically with no typing at all, and holding shift while clicking headers can sort by several columns at once. To them, date prefixes clutter the name and wreck alphabetical browsing by title — the name should say what a file is, not when.
3 independent accounts
What separates the camps is travel. Files that live and die on one machine can lean on the date column. Files that cross machines, clouds, backups or inboxes lose their metadata in transit — and files whose meaningful date isn't their save date (paperwork scanned years after it was written) never had a trustworthy column to begin with.
Common questions
Dashes or no dashes — 2026-08-29 or 20260829?
Both sort correctly, and the standard behind this (ISO 8601) allows both, so this is genuinely a taste question — the one place here where you can't go wrong. The case for dashes: a human eye picks out 2026-08-29 as a date instantly, where 20260829 reads as a serial number until you stare at it. The case for bare digits: shorter names, nothing for a fussy program to choke on, and people who use it daily say the reading problem disappears with habit — one person had it taught to them by a coworker and calls it a game changer. Dots also technically work as separators, though one camp avoids them because the dot's day job is marking the file extension. Pick one form and stay with it; the mixing is what hurts. The two classic wrong moves: starting with the month or day (files from different years interleave) and skipping the zero-padding — it must be 2026-03-07, not 2026-3-7, or the sort order breaks past single digits.
What about the hundreds of files I already have?
Leave them, mostly. Start the convention with the next file you save, and rename an old file only when you happen to touch it — retroactive reorganization is the version of this project that gets abandoned in an afternoon. One cheap triage that helps a messy archive without renaming anything: a folder per year, and old files dropped into their year. Two honest gaps: bulk-renaming tools exist that can stamp dates onto old files, but picking one is beyond this page — and if your files need sorting along several dimensions at once (date and client and project), a name can only carry so much; that's what folders are for, and past a point this trick stops being the answer.
Does this help with junk files — the ones I mean to delete?
The same conversations argue about exactly that, in two camps that both work. One camp names the junk: a prefix like ToDelete (or zzz, which sorts to the bottom, or a suffix like delete-after-March) makes throwaway files announce themselves, and it plays well with the way programs keep saving into the last folder you used. The other camp gives junk a place instead of a name: one working folder — or the desktop itself, which is hard to ignore — that you empty on a schedule. Worth hearing both ways: some people report the catch-all folder works as a buffer that keeps the workspace clean, and others report it quietly becomes permanent — a black hole with a tidy label. And an honest dissent runs through these conversations: if you need a trick to remember what to delete, the naming habit upstream is the real fix. Take the version that matches how you actually behave, not the one that sounds most disciplined.
Full tip: https://findangel.org/tips/year-first-and-the-folder-sorts-itself · FindAngel.org — free, always.