Practical notes
A practical file naming guide
File names are tiny interfaces for a future reader. A useful name answers what the file contains, where it belongs and, when relevant, which version it represents. Keep the convention simple enough that it still works when files are moved outside their original folder.
Put stable information first
Use a project or subject followed by a clear description. Include an ISO-style date such as 2026-11-06 for material that is naturally chronological. Avoid replacing meaningful words with abbreviations only one person remembers. Use a consistent separator and avoid characters that behave differently across operating systems.
Make versions explicit
Prefer a version number or revision date to names such as final-final-new. If a document is a published copy, preserve its source separately and record the relationship. When checksums matter, save them in a manifest instead of turning every name into a long hash.
Check the whole path
A good filename cannot rescue an endlessly nested folder structure. Keep paths short, remove redundant subject words, and test the convention on a dozen real files before reorganizing a large archive. Preserve original filenames for source material when provenance matters; use an index to supply clearer descriptions.