What a file name is for
A file name has two jobs. It should tell you what is inside without opening it, and it should place the file sensibly when a list is sorted. Most people only think about the first job, and end up with folders full of names like “essay”, “essay2”, “essay new” and “essay FINAL”. After a few weeks nobody, including the author, knows which is which.
A naming convention is simply an agreement with yourself about the pattern to use. It does not have to be elaborate. It has to be consistent.
Put the date first, in year-month-day order
Computers sort file names alphabetically, character by character. If you write dates as day-month-year, such as 28-10-2026, the files sort by day number first, which scrambles the timeline. If you write them as year-month-day, such as 2026-10-28, the alphabetical order matches the chronological order automatically.
Use a fixed length: two digits for the month and two for the day, so that March is 03 and not 3. Without the leading zero, a name starting “2026-10” can sort in an unexpected place relative to “2026-9”.
When a date is useful at the start of the name, it keeps related files in the order you made them. When it is not, such as for a document you always want to find by subject, put the topic first and the date later. Either is fine; just choose one and apply it.
Use version numbers with leading zeros
For documents that change over time, a version number is clearer than the word “final”. Compare:
- essay-v1, essay-v2, essay-v10
- essay-v01, essay-v02, essay-v10
In many systems the first set sorts as v1, v10, v2, because the characters are compared one at a time and “1” comes before “2”. Zero-padding fixes this: v01, v02 and v10 sort in the right order. If you expect more than 99 versions, which is unusual for coursework, use three digits.
Do not rely on words like “final”, “latest” or “new”. They stop being true as soon as you make another change. If you need to mark a submitted copy, add something specific, such as “submitted” with the date, and then stop editing that file.
Where you need detailed change tracking over a long project, tools built for version control exist for exactly this purpose, and many word processors keep a version history of their own. File names still help for the milestones you want to be able to find quickly.
A pattern that works
A flexible pattern for course work is:
date_course_topic_version.extension
For example, a hypothetical essay for a biology course:
2026-10-28_biology_cell-membranes-essay_v02.docx
Reading from left to right, you can see when it was saved, which course, what it is and which draft. Sorted by name, all your biology essays stay together in date order.
Other examples:
2026-11-05_history_reading-notes_week-06.pdf2026-11-12_maths_problem-set_v01.xlsx2026-12-01_writing_reference-list_v03.txt
You can change the order to suit yourself. Someone who works in folders by course might drop the course word from the file name. The key is that the same pattern is used every time.
Characters and length
A few practical rules help files travel safely between systems and programs:
- Avoid spaces where practical. Use hyphens or underscores instead. Spaces are allowed, but they can cause awkward behavior in some web addresses and command-line tools.
- Avoid special characters such as slashes, colons, question marks, asterisks and quotation marks. Several are not allowed in file names on some systems.
- Be careful with capital letters. Some systems treat “Notes” and “notes” as different, and others treat them as the same. Lowercase throughout is simplest.
- Keep names reasonably short, though long enough to be meaningful. Very long names can be cut off in lists and may hit path length limits on some systems.
- Avoid accented or non-Latin characters if the file will be shared with systems or people that may not handle them well. If your language needs them, test that they work where the file will go.
- Keep the extension. The part after the last dot, such as .pdf or .docx, tells the computer which program opens the file. Do not rename or remove it unless you mean to convert the file properly.
Use one separator and stick with it
A common approach is an underscore between the main parts, and hyphens within a part. In the example above, underscores separate date, course, topic and version, while hyphens join the words inside the topic. This lets you see the parts at a glance.
Names work best with folders
File names are only half of the picture. A good folder layout does a lot of the work, so the file name does not have to repeat everything. The two habits support each other, and the approach to organizing files and folders covers the structure side. If you are backing up your work, tidy names also make it easier to confirm that the right version has been copied.
Renaming existing files
Do not try to rename everything at once. Start from today: name new files properly. When you open an old file to use it, rename it then. Some operating systems also have bulk renaming tools, but they can make mistakes, so try them on a copy first.
A final check
When you save a file, ask:
- Would I know what this is in a year?
- Will it sort next to related files?
- Is the version obvious?
- Does it avoid awkward characters?
A convention takes a week or so to feel natural. It will not make your work better by itself, but it removes a surprising amount of daily confusion.