How to Name Files So You Can Find the Right Version

Choose a predictable pattern

A practical starting point is date-subject-version.ext. For example, 2026-10-01-receipts-v01.pdf sorts predictably and explains what the file contains. Use a consistent year-month-day date when chronological sorting matters. Keep a filename short enough to read in a narrow picker.

Separate work from delivery

A working document and a flattened delivery copy serve different purposes. Put them in clearly named folders or label the delivery file explicitly. Avoid overwriting the only editable project with an export that cannot retain layers or form fields.

For a sequence of pages, use zero-padded numbers such as page-01 and page-02. Before creating a ZIP or PDF, inspect the actual order; filename rules do not guarantee every app sorts identically.

Make collaboration unambiguous

Agree on which person or folder owns the current version. A filename cannot resolve conflicting edits by itself. When sending a correction, say which older file it replaces and use a distinct version number. Remove unnecessary personal identifiers from filenames that may appear in notifications, shared links, or screenshots. Review the resulting folder with search as well as by browsing.