Everyday tasks
Add a Prefix or Suffix to Multiple Filenames
Keep the useful part of each filename and add a shared label around it. A project prefix groups related documents; a version suffix marks a review batch without replacing the original name.
Add a project prefix and version suffix
- Before
- proposal.pdf
- After
- client-a_proposal_review.pdf
- Before
- budget.xlsx
- After
- client-a_budget_review.xlsx
Adds client-a_ at the start and _review before the extension. Existing names and extensions stay intact.
Review the rules, then preview sample filenames without changing real files.
Add a project prefix and a review suffix
This recipe adds client-a_ at the beginning and _review at the end of the name, before the extension. Both are literal text: change them to the client and version you actually need. You can use either rule on its own.
Keep Scope set to Name. End means the end of the name being edited; with Full scope, a suffix would go after .pdf instead. Name scope preserves the extension and avoids that mistake.
- 1Choose Try this example above, review the two Add/Insert rules, then choose Try with sample filenames.
- 2For your own rule chain, set Scope to Name. Add Add/Insert, enter client-a_ as the text and choose Start.
- 3Add a second Add/Insert rule, enter _review and choose End. Keep it after the prefix rule.
- 4Check proposal.pdf → client-a_proposal_review.pdf. Edit either text field to customize the shared labels.
proposal.pdfclient-a_proposal_review.pdfbudget.xlsxclient-a_budget_review.xlsxChoose separators and preserve meaningful names
The separator is part of the text you insert. Enter client-a_ rather than client-a if you want an underscore between the prefix and the existing name. A suffix such as _review follows the same rule.
Insert does not renumber or replace the original filename. For a prefix alone, use only the Start rule; for a suffix alone, use only the End rule. If every file needs a new numbered name, use the sequence guide instead.
proposal.pdfclient-a_proposal.pdfOnly the Start rule: client-a_.
proposal.pdfproposal_review.pdfOnly the End rule: _review.
Do not add the same label twice
Insert adds text even if it is already present. Applying the prefix again to client-a_proposal.pdf produces client-a_client-a_proposal.pdf. Keep already-labelled files out of the selected batch, or review them separately.
For mixed batches, a conditional regex can avoid repeating this specific prefix: pattern ^(?!client-a_), replacement client-a_, no flags, Name scope. This is case-sensitive, so Client-A_ is a different prefix. Try both matching and already-labelled names before choosing this alternative.
proposal.pdfclient-a_proposal.pdfConditional regex ^(?!client-a_) → client-a_, no flags.
client-a_proposal.pdfclient-a_proposal.pdfThe same conditional regex leaves this prefix intact.
Move from sample names to real files
Sample names are only a preview and do not grant access to files. Clear the sample list, keep the rules, and select the real files you want to change. Inspect the whole preview again; check long filenames, existing labels and any reported conflicts.
Supported desktop Chrome and Edge browsers can rename local files after you grant access. On browsers without direct file access, preview names in sample mode and export a rename script. Review the script and run it in the folder containing the corresponding files.
Renaming changes names, not document contents or formats. It may affect links from other applications that expect the old names. Keep important originals backed up and execute only after the preview matches your intended result.
Ready to try the workflow?
Open Rename.Tools, add a few sample files, and preview every rule before touching the real filenames.