File Naming Best Practices

Good file naming is about making filenames more useful.

A useful filename should be:

• Readable by humans
• Stable over time
• Easy to sort
• Easy to search
• Consistent across a library

Start with meaning, not decoration

Useful filenames answer simple questions quickly:

• What is this?
• When is it from?
• Which project or subject does it belong to?
• What stage is it in?

Avoid adding fields only because you can.

Prefer a fixed field order

If the order changes from file to file, the library becomes harder to scan.

Choose one structure and stay with it, such as:

date_subject_title_type

or:

project_status_title_version

Use dates only when they mean something

Do not add a date just because a file has one somewhere in metadata.

Use a date when it is one of these:

• The document date
• The event date
• The capture date
• The publication date

If the date is unreliable or unknown, leave it out instead of guessing.

Normalize repeated concepts

If you use project names, status values, organization names, or subjects, normalize them through a controlled vocabulary.

That prevents drift like:

• final, final-final, final2
• acme, ACME, acme-inc

Keep punctuation simple

Simple separators scale best.

In RenamerX, the current template editor supports:

• underscore
• hyphen

Choose one primary separator per naming system.

Avoid overstuffed filenames

A filename with too many fields becomes harder to read and more fragile when metadata is missing.

A good default is 3 to 5 meaningful fields.

Put the most stable fields first

If your archive is time-based, start with date.

If your archive is project-based, start with project.

If your archive is subject-based, start with subject.

The right first field depends on how you browse your library.

Good examples

Weak examples

The RenamerX mindset

Use AI to extract structure, then use templates to enforce consistency. That is more reliable than asking AI to invent final filenames freely.