Account

What new tool do you want?

Office & Documents

Batch Rename Files

Rename many files at once — add numbering, dates, prefixes and suffixes, find and replace (with regex), change case or extension — preview every new name, then download as a ZIP or rename in place.

How to use

  1. 1Add the files you want to rename.
  2. 2Build a pattern like 'Holiday-{n}' and set find/replace, case and numbering.
  3. 3Check the preview, then download a ZIP — or, in Chrome and Edge, rename the files in their original folder.

Frequently asked questions

What placeholders can I use?

{name} (original name), {n} (sequence number), {date} (file's modified date) and {ext} (extension).

Can it rename files directly on my computer?

In Chrome and Edge, yes — choose 'Rename in the original folder' and grant access. Other browsers download a ZIP of the renamed copies.

What if two files end up with the same name?

A (2), (3)… suffix is added automatically so nothing is overwritten.

Why renaming happens in two passes: build the pattern, then preview

A rename pattern like 'Holiday-{n}' combines literal text with placeholders that get substituted per file — {name} for the original filename, {n} for a sequence number, {date} for the file's modified date, {ext} for its extension — and the preview step exists specifically because a pattern that looks right in the abstract can produce unexpected results once it's actually applied to 200 real files with inconsistent original names. Checking the full preview list before committing is what catches a pattern mistake before it's been applied to every file instead of after.

Worked example: Batch Rename Files

Renaming a folder of vacation photos with the pattern 'Hawaii-{date}-{n}' applied to files named IMG_4821.jpg, IMG_4822.jpg and IMG_4823.jpg (all shot the same day) produces Hawaii-2026-06-14-1.jpg, Hawaii-2026-06-14-2.jpg, and Hawaii-2026-06-14-3.jpg — the date comes from each file's actual modified timestamp, not a single date typed in once, so photos from a multi-day trip would get their own correct dates automatically rather than all sharing the first file's date.

Why automatic (2), (3) suffixes matter more for find-and-replace than numbering

Sequence numbering by itself can't produce a collision, but a find-and-replace pattern can: replacing 'draft' with '' across a folder could turn draft-v1.docx and final-draft-v1.docx into the same final-v1.docx and v1.docx collision pair, overwriting one unless something intervenes. The automatic (2), (3) suffix exists specifically for this case, silently protecting against the rename quietly destroying a file by reusing its name — worth noticing in the preview rather than assuming every renamed file kept all its original content.

Why Chrome and Edge can rename in place but other browsers can't

Renaming files in their original folder (rather than downloading a fresh ZIP of copies) requires the File System Access API, a browser capability currently implemented in Chromium-based browsers (Chrome, Edge) but not universally across all browsers — which is why the in-place option only appears there, and every other browser falls back to producing a downloadable ZIP of renamed copies that you then need to manually swap in for the originals.

Numbers start at 001, and a broken find pattern leaves the name alone

The pattern opens as {name}, the counter starts at 1, and the padding is 3, so {n} becomes 001, 002, and so on. {date} is the file's modified date as year-month-day. An invalid regular expression does not wipe the name. The base is left as it was. Characters that cannot sit in a file name, such as a colon or an asterisk, become dashes. If the base would be empty after that, the name becomes file. Lowercase and slug also lowercase the extension. The extension box strips a leading dot. Sort can follow the order I added the files, or name, date, or size. The preview lists the old name and the new one before anything is renamed.

Related tools

More: Office & Documents