When you save a file for yourself, the name only has to make sense to you, today. When you send it to someone, it lands in their Downloads folder next to forty other files, and they have to figure out what it is and which version is current.

Good file names are a small courtesy that saves real time. Here's a set of habits that work well.

Start with what it is, not who it's for

"For John.pdf" tells John nothing he doesn't already know. "2026 Q3 Budget Proposal.pdf" tells him exactly what he's opening, and it still makes sense six months later when he searches for it.

A pattern that works for most things:

Project or client – what it is – date or version

Acme – Brand Guidelines – 2026-09-10.pdf
Kitchen Remodel – Floor Plan – v3.dwg
Annual Report – Draft for Review – v2.docx

Use YYYY-MM-DD for dates

Dates written as 09-10-2026 or 10.09.26 are ambiguous, since different countries read them differently. They also sort badly. Year-month-day sorts correctly in every file browser and nobody misreads it:

2026-08-30
2026-09-02
2026-09-15

Put the date at the start if you want files to line up chronologically, or at the end if the project name matters more.

Version numbers beat "final"

Everyone has seen this:

report_final.docx
report_final_v2.docx
report_final_FINAL.docx
report_final_FINAL_use this one.docx

"Final" is a prediction, and it's usually wrong. Use version numbers instead, with a leading zero so they sort properly past nine: v01, v02 ... v10. When something really is the delivered version, you can add "approved" or "delivered" to that one file.

Characters to avoid

Some characters cause trouble when files move between systems:

Windows forbids these in file names: \ / : * ? " < > |
Slashes are path separators on every system, so never use them in a name.
Leading or trailing spaces can make files hard to open or delete.
Emoji and unusual symbols usually work, but occasionally break in older software, zip tools or when uploaded to the web.

Letters, numbers, spaces, hyphens and underscores are safe everywhere.

Spaces: fine for people, awkward for the web

Spaces in file names are readable and generally fine for documents shared with people. In web addresses, though, a space turns into %20, so "My Report.pdf" becomes "My%20Report.pdf" in a link. It still works, it just looks messier.

For files that will be linked publicly or used on a website, hyphens are cleaner: my-report.pdf.

Keep names reasonably short

Very long names get cut off in file browsers and email previews. Windows also has an old limit of about 260 characters for the full path, including all the folders. A long file name inside a deeply nested folder can hit that limit, especially after someone unzips your archive into their own folder structure.

Aim for names you can read at a glance. Under 60 characters is a good target.

Name the archive, too

Zip files often get named after whatever folder you right-clicked, like "New folder.zip" or "Export.zip". Rename it before sending. "Acme – Photo Selects – 2026-09-10.zip" makes it easy to find later.

Mind what the name reveals

A file name is visible to whoever receives it. Internal shorthand like "client-difficult-revised-pricing.xlsx" can be awkward if it lands in the client's inbox. Rename anything that's going outside the team.

A naming checklist

Describes what the file is
Includes a date (YYYY-MM-DD) or version (v01)
No special characters
No "final"
Short enough to read in a list
Nothing you wouldn't want the recipient to see

The recipient probably won't comment on a well-named file. They'll just open it, find it again later, and not have to ask you which version is current.

Name Your Files Like Someone Else Has to Find Them