A filename is a small label, not a history of every conversation about a document. The goal is to identify the subject, the relevant date, and the revision without opening five near-identical files.
The examples below are fictional office scenarios. Download the naming practice ZIP, extract it into a new folder, and open report FINAL final 2.docx. Its reporting date is 2026-11-10, revision 02, with 20 seats. Those content clues—not the old name—identify the copy. The ZIP contains four reports, two workshop notes, and the paired naming table. Keep the table outside the file list while you try the exercise.
Choose what the date means
Decide whether the first date is the meeting date, reporting period, or creation date. Write that rule down for the folder. A monthly report about October can be created in November; those two dates are not interchangeable.
Use YYYY-MM-DD when you need a full calendar date, with two digits for the month and day. Under ordinary ascending name sorting, 2026-02-09 comes before 2026-11-03. A name starting 9-2-2026 does not provide the same useful order. File managers may use natural sorting and group folders separately, so confirm the actual Name sort in your view.
| Part | Rule | Example |
|---|---|---|
| Date | Full year, padded month and day; one meaning per folder | 2026-11-03 |
| Subject | Short, recognizable words with hyphens | ops-report |
| Version | A fixed-width number; increase when you make a distinct revision | v01, v02 |
| Extension | Preserve the real file type | .docx |
A useful pattern is date_subject_version.extension. If a workflow will exceed 99 versions, choose three digits from the beginning rather than mixing widths.
Scenario 1: a recurring operations report
A fictional team prepares a report each Tuesday. Use the reporting date, not the day somebody emailed the attachment. The original folder has report FINAL final 2.docx, new report.docx, report old.docx, and report revised.docx; none tells a colleague which period is covered.
Copy the files to a practice folder. Open each copy and read its report date and contents before assigning a name. Do not guess from the old filename alone. Your intended ascending Name order is:
2026-11-03_ops-report_v01.docx
2026-11-03_ops-report_v02.docx
2026-11-10_ops-report_v01.docx
2026-11-10_ops-report_v02.docx
The date groups the reporting periods, while the version orders revisions inside each period. v02 means a later revision; it does not mean approved. If approval matters, keep the approved copy in a clearly described delivery folder or maintain an explicit approval record.
Scenario 2: notes for a workshop
A fictional workshop takes place on 12 November. Keep the event date stable even when you edit the notes before the event:
2026-11-12_workshop-notes_v01.txt
2026-11-12_workshop-notes_v02.txt
The two actual TXT files state the same event date. Revision 01 says “bring paper”; revision 02 says “bring paper and pens.” The revision changes, while the event date stays stable. If the workshop is rescheduled, agree whether the folder should use the revised date; avoid half-renaming a shared set while colleagues are working in it.
Apply the rule without losing the originals
- Copy the six downloaded reports and notes into a new practice folder. Show their extensions so that you can preserve them.
- Read the date and revision inside every file, then compare your intended new name with the downloaded CSV. Check that every new name is unique.
- Rename only the copies. On macOS Tahoe 26, Finder’s multi-file Rename menu offers Replace Text, Add Text, and Format. For a tiny set with different dates, individual renaming is often clearer than a batch operation.
- Set the folder to an ascending Name sort. Do not use the Modified date column to judge this naming pattern.
- Open each renamed file. Confirm that its content and extension still agree, then compare the folder against your mapping table.
A rename does not convert a file. Changing .docx to .pdf can break opening behavior without creating a valid PDF. Use the originating application’s Export or Save As command for a real conversion.
Keep names portable
For a set shared with Windows users, avoid < > : " / \ | ? *, trailing spaces, and trailing dots. Do not use reserved names such as CON, NUL, or COM1, even with an extension. Avoid distinguishing important files only by capitalization; case behavior differs across file systems.
Keep folder paths reasonably short, particularly when other software will open them. Do not rename system folders, application support files, or live project assets that an application locates by name. Renaming a linked spreadsheet or shared cloud file can affect references or other users.
Check the result
Your test passes when a person can identify the correct period and revision from the name, the visible Name sort matches the intended sequence, every original has a recorded counterpart, and all copies still open. If two names collide, stop and inspect the documents. Do not overwrite one to make the rename succeed.
Keep the mapping table with the practice set until the result is checked. For real shared work, agree the rule first and make a recoverable copy before a larger rename.
References & scope
These official references support the software instructions. Practice documents are original, fictional teaching examples; labels can vary by release.
- Naming Files, Paths, and Namespaces
Windows reserved characters and names; extension and case limitations. - Rename files, folders, and disks on Mac
Finder batch Rename choices and names that should not be changed.