How to Choose File Names That Help Everyone

A file name is a small piece of documentation

Names such as “final-final2” or “document-new” make sense only while the surrounding conversation is fresh. Files are copied into downloads folders, attached to email, and opened months later by people who were not part of the original work. A useful name carries enough context to survive that journey.

Start with the subject and purpose, then add a date or version when it matters. Use a consistent date format such as `2026-08-27` so files sort naturally. Prefer words that someone else would search for. Avoid private abbreviations, unexplained initials, and characters that cause trouble across operating systems.

Make versions unambiguous

Choose either a date-based history or explicit version numbers for a project and use it consistently. If a file is approved, say so in the name only when approval is a meaningful state. Do not label a working copy “final” simply because it is the latest one on your computer. Keep the authoritative location clear so attachments do not become competing sources.

• Use one separator style, such as hyphens or underscores.
• Keep names readable and avoid unnecessary filler words.
• Put the most searchable subject near the beginning.
• Use a short README or index when a folder needs special rules.

Test the name outside its home

Copy a few files into a blank folder and ask whether you can identify them without opening each one. Check how they sort, how they appear in email, and whether the extension remains visible. For shared work, document who owns the source and how changes are approved.

Good file names do not require a complicated system. They make the next action obvious and reduce the number of questions people need to ask before using a file.