filesA practical file library

02 / File names

A name that explains the file

A subject, a date and a version number are more useful than a chain of "new" and "final". Agree on a pattern before you have dozens of copies.

One pattern for one collection

A useful name answers the questions you ask when scanning a list. For invoices, that might be a date and number; for illustrations, a subject and variant; for notes, a topic. A file name does not need to contain the entire catalogue record.

2026-04-18_reading-room_notes_v03.txt
reading-room_layout_v02.svg
reading-room_summary.txt

These are invented examples. A date at the start helps when chronological order matters. The YYYY-MM-DD format avoids ambiguity between month and day, and leading zeros preserve sorting. If a date does not help you find anything, there is no need to add it automatically.

Choose portable characters

Use descriptive words and a consistent separator. Hyphens within a subject and underscores between fields are one workable convention, not a universal standard. Modern systems support Cyrillic and other scripts; Latin names can be easier to exchange with tools that handle Unicode poorly.

  • Avoid / \ : * ? " < > | when sharing files across systems.
  • Do not end names with a space or a full stop.
  • Do not rely on case alone: Notes.txt and notes.txt may resolve to the same name.
  • Keep the real extension. Renaming .jpg to .png does not convert an image.

Names such as CON and NUL are reserved on Windows, including with some extensions. A short descriptive name is more portable than one running to hundreds of characters.

A version is not an output

While work is changing, use a number: v01, v02, v03. If version control already records the history, do not duplicate every step as a separate file without a reason. For delivery, create a clearly named export and retain the source it came from.

The word "final" does not make a file immutable. Note in the README which file was delivered and what was checked. If approval is still pending, label it as a draft. Do not call an unapproved copy final just to make the directory look tidy.

Rename without losing context

Test the pattern on five files first. Make a CSV with old and new names. Check that two source files will not map to the same destination. Keep the table for bulk changes so you can work out what happened later.

Renaming can break links in presentations, editing projects and notes. Close working applications, keep a backup and open the result after the change. Do not rename application-managed files just to enforce a visual style.

The minimum rule

A name should make sense to someone who does not remember the conversation. Put any remaining context in a README rather than turning the name into a paragraph.

Download the file-sorting checklist