File Naming Conventions: Best Practices, Examples & Templates

Choose the fields you actually use to find a file: a subject, client, document type, date, or original identifier. Put the most useful grouping field first. Avoid adding fields whose values you cannot reliably obtain.

A date-first name sorts chronologically in a filename list. A client-first name groups clients. Neither replaces a folder structure or a search tool; choose the order that suits the way you browse.

A downloaded invoice’s creation date may be its download date. Do not label that field Invoice Date. If your naming prompt asks for a document date, specify which one and what to return when it is absent.

An ISO-style YYYY-MM-DD date sorts in calendar order. A date alone does not distinguish several revisions made on the same day.

Spaces are readable on a desktop. Hyphens can be convenient for files that will become URL paths. Use one convention within a collection so names are easier to scan.

Keep an explicit version identifier if versions matter. RenameClick cannot infer your approved version from a filename or guarantee that the latest modification is the correct final document.

Preserve a camera number or export ID when another system uses it. An automatically assigned counter is a new sequence, not the original identity of the file.

See preserving original identifiers for the full reference.

Use one template per file family and keep the field order fixed inside that family. Replace the placeholders with the fields you actually search for. The names below are illustrative; your files and rules will produce different words.

Keep the date in ISO order when chronological sorting matters, and put the field you search by first when it does not. A version marker belongs at the end, where it does not break the sort. Underscores separate fields; hyphens join the words inside one field.

$date{YYYY-MM-DD}_$slugcase{$1}
$exif{date}_$slugcase{$1}
$date{YYYY-MM-DD}_$oldName

The first pattern prefixes the generated description with the file creation date, the second with the EXIF capture date, and the third keeps the original name behind a date. Field-based names such as supplier, document type and number come from the document text, so write that structure in Custom Instructions; format patterns cannot read inside a document.

• final_v2_FINAL.docx: the version is ambiguous. Use one version marker at the end, or let the date carry the version.
• 03-04-2026_invoice.pdf: day and month are ambiguous outside your region. Use YYYY-MM-DD.
• Document1.pdf, IMG_4471.jpg, Scan_0021.pdf: the name says nothing outside its folder. Include the subject and one identifying field.
• Invoice (copy) (1).pdf: copies hide behind counters. Decide whether the duplicate is needed before renaming it.
• Mixed separators and cases across one archive: a convention only helps when every file of the same family follows it.
• Names longer than the file list can show: keep the searchable field near the start so it stays visible when the name is truncated.

On Windows, avoid the reserved characters < > : " / \ | ? * and reserved device names. Check any sync service or web server the files pass through separately; a local filename and a public URL do not share one set of rules.

With the built-in naming instructions selected, use Format to arrange the generated description and metadata. These are templates to enter, not results from a file test:

$date{YYYY-MM-DD}_$1
$oldName_$1
$slugcase{$1}

The first pattern uses the file creation date. The second retains the original name without its extension. Slug Case changes the description to lowercase words with hyphens; $lower{$1} changes case but keeps spaces.

For fields extracted from document content, select Custom Instructions instead and write the whole naming rule there. Format and Output Language are disabled in that mode.

See writing a field-based naming prompt for the full reference.

See the format syntax reference for the full reference.

Inspect the proposed names for missing fields, repeated separators, cut-off descriptions, and conflicting IDs. Use Find & Replace for consistent edits to suggestions, or retry after changing the settings.

Apply the selected files when the names are useful. Keep the convention documented for people who name related files manually.

Save custom formats and instructions as presets. Export Settings transfers supported preferences and presets, including categorization settings; it does not transfer models, API secrets, licenses, or file-operation history.

On another computer, install the required capabilities and reconnect local paths. Import replaces the included settings, so review what you are importing.

See settings export and import for the full reference.