File Naming Conventions: Best Practices That Scale

Final.docx, final-v2.docx, final-REALLY-final.docx. Every shared folder ends up like this unless someone agrees on a naming convention. Good file names make documents easy to find, sort correctly by date and travel safely between Windows, macOS, Linux and cloud storage. This guide covers the rules that matter, the case styles developers use, and how to test that your app copes with whatever names people throw at it.

Pick one case style and stick to it

Most conventions differ only in how words are joined:

• kebab-case — quarterly-report.pdf. Common for web assets and URLs, because hyphens read well in links.
• snake_case — quarterly_report.pdf. Popular in Python projects and data files.
• camelCase — quarterlyReport.pdf. Often used for source files in JavaScript projects.

None is objectively best. What matters is consistency inside a project, so that searching, sorting and scripting behave predictably. Lowercase names also avoid trouble moving between systems that treat case differently: Linux distinguishes Report.pdf from report.pdf, while Windows and macOS usually do not by default.

Dates and numbers that sort themselves

Write dates in ISO 8601 order — year, month, day — as in 2026-03-14-meeting-notes.md. Alphabetical sorting then equals chronological sorting, with no special software needed. Formats like 14-03-2026 or 3-14-26 scatter files randomly.

Pad numbers with leading zeros: photo-001.jpg to photo-120.jpg. Without padding, photo-10 sorts before photo-2. For versions, prefer -v02 over words like “final”, which never stay final.

Characters and names to avoid

• Forbidden on Windows: / : * ? " < > |. A file created on another system with these can fail to sync.
• Reserved names on Windows: CON, PRN, AUX, NUL, COM1 and LPT1, even with an extension.
• Spaces work, but they need quoting in the terminal and become %20 in URLs.
• Leading or trailing dots and spaces cause odd behavior in several tools.
• Very long paths can hit limits in older software, so keep names concise.

How to create test file names with the generator

Upload forms, storage buckets and file browsers need realistic names to test with. The generator above makes them in seconds:

1. Choose a File type — images, documents, code, audio and video, or archives — or leave it on “Any” for a realistic mix.
2. Choose a Naming style: snake_case, kebab-case, camelCase, or the style that includes a date, which is ideal for testing sorting and archiving.
3. Generate up to 100 names, such as friendly-waterfall.png or silent-tower-v6.pdf.
4. Export the list and use it to seed a mock directory, a spreadsheet or a UI prototype.

Only names are created — no files are written or downloaded.

Write the convention down

A naming rule that lives in one person’s head will not survive the next deadline. Put a short note in the folder or project README: the case style, the date format, the version suffix and two or three examples. Then rename the worst offenders once, so the folder demonstrates the rule instead of contradicting it.

Example conventions for common folders

Here is how a team might apply the rules in practice:

• Meeting notes: 2026-03-14-design-review.md — date first, because notes are usually found by time.
• Contracts: acme-supply-agreement-2026-v03.pdf — client first, then subject, year and version.
• Photos: 2026-06-02-harbor-trip-014.jpg — date, event and a padded sequence number.
• Code: user-profile-card.tsx — named after what the file exports, in the project’s chosen case.
• Data exports: orders-export-2026-05-31.csv — the content, then the snapshot date.

Notice that every example is lowercase, uses one separator, and puts the most useful sort key first. Once people see a few examples, they copy the pattern without needing to read the rules.

Pro tips

• Put the date first when files are mainly found by time, and the topic first when they are found by subject.
• Never rely on the folder name alone to explain what a file contains.
• Avoid words like “new”, “old” and “final”; use dates or version numbers instead.
• Test your upload form with names that contain spaces, accents and very long words.
• When you rename old files in bulk, keep a simple list that maps old names to new ones, so links and references can be updated later.

Frequently asked questions