File naming conventions for teams: rules and templates you can copy

The short answer: put the date, project, content and version in every file name, always in the same order. For example 2026-10-30_lumen-one_press-release_v02.pdf. Write the date as year-month-day, use hyphens or underscores instead of spaces, avoid the characters \ / : * ? " < > |, and number versions v01, v02. Write the rule down in one paragraph and keep it where the whole team can see it.

Why it matters

A file name is the first thing anyone searching sees. “New presentation FINAL (2).pptx” doesn’t tell you which client it’s for, which month it’s from or whether it’s the latest. When a team has dozens of files like that, you end up opening them one by one or calling the colleague who made them.

A naming convention solves three things:

• order: files sort chronologically on their own;
• search: you find a file by typing the client or project;
• version: you know which is the latest without opening it.

The 6 rules

1. Date first, year-month-day. 2026-10-30 or 20261030, the ISO 8601 format. 10-30-2026 sorts by month and 30.10.2026 by day, so files from different years end up mixed together.
2. The same order of parts. Pick an order once (for example date_client_project_description_version) and don’t change it.
3. No spaces. Use hyphens between words (press-release) and underscores between parts (_). Some software and links handle spaces badly.
4. No forbidden characters. Windows, OneDrive and SharePoint don’t accept \ / : * ? " < > |. No leading or trailing spaces either, and no trailing period.
5. Numbered versions with a leading zero. v01, v02… v10. Without the zero, v10 sorts before v2. Don’t use “final”: “final” is almost always followed by “final2”.
6. Short, with abbreviations everyone knows. University data-management guides recommend short names with abbreviations the whole team understands. If you abbreviate (PR for press release), write the abbreviation into the team rule.

Accented and non-Latin characters work in current systems but can come out garbled in ZIP archives opened on another system or in older software. For files that leave the team, plain ASCII is safer.

Templates to copy

File type	Pattern	Example
Event photos	date_event_photographer_number	2026-10-30_awards-gala_jsmith_0142.jpg
Press release or project document	date_project_document_version	2026-10-30_lumen-one_press-release_v02.docx
Design deliverable	client_campaign_format_size_version	acme_fall26_story_1080x1920_v03.png
Contract	client_type_date	acme_services-agreement_2026-10-30.pdf
Logo	brand_variant_colour.format	nivlo_logo-horizontal_white.svg
Video	date_project_content_length_version	2026-10-30_lumen-one_teaser_30s_v01.mp4

You don’t need every part for every type. What matters is that the same type of file always has the same shape.

Where to write the rule down

Put the convention in a short file (for example README.txt) in the main folder of the project or team: the order of parts, the date format, the abbreviations you use and two or three examples. The University of Oregon guide recommends exactly that: the rule documented next to the files. A new collaborator reads it in two minutes.

How to rename many files at once

On a Mac (Finder): select the files, right-click → Rename. Choose Replace Text (swap part of the name), Add Text (add text before or after the name) or Format (a new name plus a number or date).

On Windows: select the files and press F2. They all get the same name followed by (1), (2), (3). For more complex rules, PowerRename from Microsoft PowerToys does search and replace, zero-padded numbering and renaming by the date a photo was taken, with a preview before anything changes.

For photos, many import tools (Lightroom, Photo Mechanic, Capture One) can rename files on import using a template. That’s the best moment to do it.

When a name isn’t enough

A good name holds one “drawer”: a photo from the gala is also “event”, “sponsor X” and “for press”. A name can’t hold everything. That’s where tags help: you add them once and find the file by any of them.

In Nivlo, search finds files by name, tags and folder names from a single field. You can tag many files at once, and from the Professional plan you can define synonyms, so “logo” also finds “brand mark”. Versions no longer live in the name: you upload a new version over the file and the history is kept, under the same name.

Common mistakes

• “final”, “final2”, “final-good”. Use version numbers.
• Day or month first in the date. Files stop sorting chronologically.
• A colleague’s name as the only clue (“for Anna.pdf”). A month later nobody knows what’s in it.
• The rule lives only in someone’s head. Write it down next to the files.
• Renaming after the file was sent. Whoever has the old link or file can’t find the match. Rename before you send.

For photos prepared for journalists, see our guide to online press kits. For logo files, see brand guidelines.