
How to Rename Files Automatically by Date, Project, and Category
To rename files automatically, first define the information each filename should contain. Then choose a tool that can obtain that information reliably: a batch renamer for predictable text changes, or a content-aware tool for details inside documents.
A practical pattern is:
YYYY-MM-DD_project_category_identifier.ext
For example, 2026-10-21_ATLAS_invoice_INV-1042.pdf is useful because each part has a defined meaning. The goal is consistent, verifiable names, not adding every available detail.
1. Decide which date belongs in the name
A file can have several relevant dates:
| Date | What it describes | Suitable use |
|---|---|---|
| Document date | A date printed inside the document | Invoices, letters, dated reports |
| Capture date | When a photo or scan was captured | Media workflows where capture time matters |
| Download or receipt date | When you received a copy | Intake tracking |
| Filesystem timestamp | A property of the stored file | Workflows that explicitly use that property |
Do not treat these as interchangeable. Copying, exporting, and downloading can affect filesystem timestamps. A contract may contain a signature date, effective date, and renewal date; specify which one you want.
Use YYYY-MM-DD for dates that should sort chronologically as text. If the source does not contain the required date, flag the file for review instead of inventing one.
2. Define the project field
Use a stable project ID when several clients or projects have similar names. Keep an agreed mapping between IDs and readable project names.
A project-specific intake folder can supply context that a generic document lacks. Still, verify the contents before applying that context to every file: a folder can contain a misplaced attachment.
Choose one spelling, such as ATLAS, and use it consistently. Avoid switching among client abbreviations, informal nicknames, and internal codes in the same workflow.
3. Use a short category list
Start with the categories people already search for, such as invoice, receipt, contract, report, and meeting-notes.
Keep classification separate from workflow status. Identifying a document as an invoice does not establish that it is approved or paid. Those decisions belong in the relevant business system.
Document the difference between easily confused categories. A supplier's invoice and your payment receipt may refer to the same purchase but serve different purposes.
4. Choose the right renaming method
Use a rule-based batch tool when the required information already exists in the filename and you need a repeatable transformation, such as replacing a prefix or adding a sequence.
Use content-aware naming when the source names are generic and useful details appear inside supported documents or images. Renamer.ai can propose names using file content and a naming template.
Neither method removes the need to define the rules. Do not assume an application will learn your team's conventions automatically from ordinary use.
5. Configure and preview a small batch
In Renamer.ai, choose or create a naming template that expresses the fields you want. Use the current guides for the available controls and supported formats.
The example pattern in this article describes the desired output; it is not placeholder syntax to paste into every tool.
Test a representative batch containing:
- A clear document with all required information.
- A document with several dates.
- A file with a missing project ID.
- Two documents that could produce the same name.
- A scan that is difficult to read.
Review the proposed names against the actual files. Preserve extensions and identifiers such as invoice numbers. Use an explicit exception process for missing or uncertain values.
6. Configure folder destinations separately
A filename template controls the name. A folder organization template controls where a file goes. Test both so that a correct name does not conceal an incorrect destination.
For an ongoing workflow, a Magic Folder can monitor a chosen intake folder. Start with a dedicated folder and confirm the behavior using copies. Keep processed output separate from incoming files and check that the setup does not repeatedly process its own output.
Avoid testing on files that other applications manage by path, such as active project assets or photo-catalog originals.
7. Keep recovery and review simple
Before a large batch, retain a backup and a record of original names. Review and revert features can help correct renaming changes, but they do not replace independent backups.
Do not overwrite a file simply because two proposed names match. Determine whether the files are duplicates, revisions, or different records, then preserve a meaningful distinguishing field.
After processing, open a sample, confirm destinations, and check that shared links or application references still work where relevant.
How to know the workflow is working
Track the proportion of names accepted, common corrections, and time spent handling exceptions. Improve the template when the same mistake repeats.
Start with one document category and expand once another person can find the right file using the resulting names. Our file naming conventions guide provides additional examples for teams.
About the author

Uros Gazvoda
Uroš is a technology enthusiast, digital creator, and open-source supporter who’s been building on the internet since it was still dial-up. With a strong belief in net neutrality and digital freedom, he combines his love for clean design, smart technology, and human-centered marketing to build tools and platforms that matter.
Founder of Renamer.ai