What Makes a Good File Naming Convention?

You should be consistent and descriptive in naming and organizing files so that it is obvious where to find specific data and what the files contain.


It's a good idea to set up a clear directory structure that includes information like the project title, a date, and some type of unique identifier. Individual directories may be set up by date, researcher, experimental run, or what makes sense for you and your research.   

Consider the following… 

  • index.doc

  • final.pdf

  • family.jpg


  • 20200528-ThesisTOCV001-DOC.doc

  • 20190519-S515FINALV001-PDF.pdf

  • 19780130-FAMILYVACATION-JPG.jpg

The second lets the user know quickly the date, subject, and file format making it easier to locate files quickly and easily. 

What Should I Include in a File Naming Convention?

Filenames should have a precise name that allows you to quickly identify what the file contains.

Some information may include:

  • Project name or acronym

  • Location/spatial coordinates

  • Researcher name/initials

  • Date or date range of project

  • Type of data

  • Conditions

  • Version number of file

  • Three-letter file extension for application-specific files

A good format for date designations is YYYYMMDD or YYMMDD. This format makes sure all of your files stay in chronological order.

What Should I Avoid in a File Naming Convention?

Do not make file names too long, since long file names do not work well with all types of software. Also, file names that are too long can easily be corrupted increasing the risk of losing your work.

Do not use special characters such as  ~ ! @ # $ % ^ & * ( ) ` ; < > ? , [ ] { } ' " and |.Do not use spaces. Some software will not recognize file names with spaces, and file names with spaces must be enclosed in quotes. Recommended options include:

  • Underscores: file_name

  • Dashes: file-name

  • No separation: filename

  • Camel case: FileName