File names

Using consistent, straight forward, and well thought out file names will help you and others make sense of your files.

File names should have meaning

Files names are the fastest way to identify what is inside a file and how it differs from similar files. You should name your files based on important elements of your project such as:

• Specimen or sample designation
• Date, time, location
• Conditions or variables
• File version number
• Other relevant information

You can combine elements as needed to create a file naming convention that you can use during the entire project. An explanation of what each element of the file name means should be documented. One easy way to do this is to create a readme text file in the project's top folder.

Sorting

Consider how you want to track the files (i.e. chronologically, by location, by sample, etc.). The most important elements should be at the start of your file names so that you can sort by these elements.

Standards

Don't reinvent the wheel. Use existing standards whenever possible! This will make it easier for others to understand the file names.

For example, there is a standard that defines how dates and times should be recorded: ISO 8601. Using this standard eliminates common points of confusion such as the difference between US and European dates which swap the order of day and month.

Avoid special characters

Just because you can use something doesn't mean you should. There are two big reasons to avoid special characters, punctuation marks, and symbols in filenames:

1. Special characters and punctuation marks are often reserved characters for computer operating systems. These character are used in a very specific way by the operating system and using them file names can cause errors. 
2. Not all operating systems and programs support the same characters. A common example is how the modern Mac OS (9 and above) supports a number of special characters (/ \ : * ? < > |) that are not supported by Windows. 

And never use emojis (😱). There are multiple problems with using them in file names so the best recommendation is don't.

Limit the use of periods

Periods (.) should only be used to separate the file name from the file extension. Do not use periods to separate different elements of a file name, use a dash (-), an underscore (_), or space instead. 

The same rule applies for multiple periods (i.e. .. and ...). Don't do it!

Avoid spaces

The last practice we'll cover is avoiding spaces in file names. Spaces are not supported by all operating systems or by command line applications. A space in a filename can cause errors when loading a file or when transferring files between computers. Common replacements for spaces in a filenames are dashes (-) or underscores (_).

Alternatively you can also use a technique called camelCase which uses letter case to separate name elements.

If you have many files you may want to test your computer or storage system search to see if dashes and underscores are treated as spaces or if you have to search for files by their exact name. For example, will searching for "2018 final paper" find the file named "final_paper_2018.docx"?

Or use spaces

Spaces are often preferred by people with low-vision or dyslexia because they're easier to read than dashes (-), underscores (_), and camelCase. As the majority of modern computer systems and programs can read spaces, and programs like Advanced Renamer can easily replace spaces with a different character, the argument to avoid spaces in file names isn't as strong as it used to be.

More information

Joseph Scott's "Things That Shouldn’t Be in File Names for $1,000 Alex." is a good summary of file naming practices to avoid.

Help icon by Icons8