Bulk File Renamer

Two tokens plus anything literal: {n} becomes the sequence number, {orig} becomes the original base name, and everything else is copied as typed. There's no date token or regex support, so write dates directly into the pattern, like 2026-07-03-shoot-{n}.

Use a pattern such as 2026-07-03-wedding-{n} with Start at 1 and Padding 3, which produces 2026-07-03-wedding-001.jpg through however many frames you loaded. The ISO date prefix keeps every future folder listing in chronological order.

Never. Your files are read in the browser, copied under their new names into a ZIP, and the download is a fresh archive. The originals on disk keep their old names, so a bad pattern costs you a redo, not data.

Your pattern probably had no {n} token, so all outputs shared one name and later entries replaced earlier ones in the archive. Any multi-file pattern needs {n} somewhere, or {orig} if you're prefixing existing names, to keep each entry unique.

Yes, the reading, renaming, and ZIP packaging all happen locally in your browser tab. That makes it fine for contracts, client deliverables, and anything else you wouldn't hand to a random web service.

It zero-pads the sequence number to a fixed width: padding 3 gives 001, 002, 003. Padded numbers sort correctly in every file manager, where unpadded ones produce the classic 1, 10, 11, 2 ordering mess. Match padding to your batch size, 3 covers up to 999 files.

In list order, counting up from the Start at value. Files number in the order they were added, so add them in the sequence you want, or Clear and re-add if the order came in wrong. The preview's first five rows confirm the mapping before you run it.

That's exactly its job. A pattern such as final-{orig} keeps every base name and adds your prefix, so report.pdf becomes final-report.pdf. Combine both tokens, {n}-{orig}, when you want originals preserved but forced into a numbered order.

No, the bulk file renamer online runs in the browser tab, so there's nothing to download, update, or keep licensed. A bulk file rename here reads your files locally, writes the new names into a ZIP, and never uploads a thing, which suits client work and contracts.

Yes. You can rename multiple files at once whether they're photos, PDFs, audio, or a mix, up to 100 MB each, because the tool only swaps names and re-zips. That's the point of a batch rename files run, one pattern applied to an entire mixed folder regardless of extension.

Consistency and speed. A batch file rename tool applies one pattern to hundreds of files in seconds, with zero-padded numbers that sort correctly, something manual renaming gets wrong fast. Reach for this file rename tool when a folder needs uniform names, not when you're fixing a single typo.

Yes. When you file rename online here, only the base name changes; the tool reattaches each original extension automatically, so report.docx stays a .docx. That's one less thing to get wrong than with a manual file renamer, where a fat-fingered extension can break the file.

A web app, so there's no bulk rename utility download to install or keep updated. If you've used a desktop bulk rename utility before, the idea is the same, patterns and sequence numbers, but this one runs in any browser and can't touch files outside what you drop in.

Any run where two or more files need the same pattern is fair game for bulk rename, though the payoff grows with the count. For five files the live preview shows every before-and-after pair; past that it shows the first five, which is enough to trust the pattern before you commit.

Not directly. This file name renamer builds new names from a pattern with {n} and {orig} tokens, rather than finding and replacing text inside the old names. To strip or swap a specific word across a batch, rename with a fresh pattern here, or use a desktop tool for regex-style replacement.