Bulk Rename Files
Bulk rename files in your browser with 7 rule types, then download renamed copies as a zip. Add up to 2000 files; originals stay unchanged.
🔒 Your files are renamed and packed inside your browser — nothing is uploaded to a server. Changing the extension changes the name only; it does not convert the file format.
How to use
- Add the files you want to rename: Drop files onto the box or click to choose them — any file type is accepted, up to 50 MB per file and 100 MB in total. On a computer you can drop a whole folder and its structure is kept. The box stays on screen afterwards, so you can keep adding files without clearing the list.
- Set up your rename rules: The page starts with one Add sequential numbers rule, so you see a preview straight away. Add more rules with the buttons — Find and replace, Add prefix / suffix, Change case, Delete characters, Change extension, Insert text — and use ↑ and ↓ on each rule card to put them in the order you want. Rules run from top to bottom.
- Check the preview, then pack: The table shows Original name next to New name for every file and recalculates as you type. When it looks right, click Pack and download zip. On a phone, Save to device opens the system share sheet if the browser offers file sharing, and otherwise downloads the zip.
How to bulk rename files online
This tool creates renamed copies in a zip without changing your originals. It accepts up to 2000 files, with limits of 50 MB per file and 100 MB per batch, and processes them in your browser.
The files sitting on your disk keep their names, their location and their contents. To finish the job you unzip the result and replace the old files yourself, or keep both sets side by side. Because nothing on your device is modified, there is also nothing to undo if a rule turns out wrong; you just change the rule and pack again.
Renaming itself never looks inside your files. Each new name is worked out from the old name, the file's position in the list and the rules you set, which is why any file type is accepted and why the preview updates instantly even with hundreds of files. The file contents are only read at the very end, when the zip is built, and they are copied byte for byte. Nothing is uploaded: the renaming and packing code is downloaded with the page and then runs on your computer or phone, so invoice scans, client photos and ID documents stay where they are. The page itself is still fetched from a server, and the zip you download is an ordinary unencrypted file — anyone you send it to can open it.
The before-and-after table is the real output preview. It is recomputed from scratch on every change — a new rule, a reordered file, a different separator — so the New name column is the name that will go into the zip, including the de-duplication suffixes and character cleanup described below. The one exception is adding files while a pack is already running: the box is not disabled during packing, so files added at that moment appear in the preview but not in the zip that was already in progress. If that happens, pack again.
To look inside the result or pull the renamed files back out on a device without a zip app, use Unzip Files.
The seven rules, and why their order matters
Input: report.jpg; start 1; padding 2; prefix position; separator _; text prefix P-. Add sequential numbers, then Add prefix / suffix → P-01_report.jpg Add prefix / suffix, then Add sequential numbers → 01_P-report.jpg
There are seven rule types and you can stack as many as you like, including several of the same type. Pick the one that matches the job from the table below. Each card has Disable, which keeps the rule and its settings in the list but leaves it out of this plan, and Delete, which removes it.
Rules are applied one after another, top to bottom, so the order changes the result — see the two lines above, which are the same two rules swapped. Reorder them with the ↑ and ↓ buttons on each rule card; there is no drag-and-drop. The same logic applies to the file list: sequential numbers follow the list from top to bottom, so moving a file up or down renumbers the batch. There is no automatic sort by name, size or date, so if you need a specific order, arrange the list before you add the numbering rule.
Numbering takes a start value, a step and a number of digits to pad to. Padding to three digits gives 001, 002, 003 — handy because those names sort correctly in any file browser — and the padding is a minimum, not a ceiling: with three digits the thousandth file is simply 1000. The step can be negative, and a negative result is written like -05. The number can go before the name, after the name, or replace the base name entirely, in which case the separator box is disabled because it has nothing to separate.
Find and replace has a Regular expression checkbox. With it ticked, the replacement text follows JavaScript's rules, so $1 is the first capture group and $& is the whole match: searching for (\d+) and replacing with -$1- turns report2024.pdf into report-2024-.pdf. With the box unticked, $1 is just those two characters. If a pattern is invalid, the page lists the browser's own error message under the preview and disables the pack button until you fix it. While a pattern is broken no rule is applied at all, so the names in the preview are your original ones — except where the cleanup and de-duplication steps below still change something, since those run regardless of the rules.
| Task | Rule | Example |
|---|---|---|
| Add numbers | Add sequential numbers | report.jpg → 001_report.jpg (default settings) |
| Remove text | Find and replace | IMG_report.jpg → report.jpg (find IMG_, replace with nothing) |
| Add a code or a date | Add prefix / suffix | invoice.pdf → ACME_invoice.pdf (prefix ACME_) |
| Fix capitals | Change case | My Report.pdf → my report.pdf (all lowercase) |
| Cut a prefix off | Delete characters | 20240131_note.txt → note.txt (9 characters from the start) |
| Rename the extension | Change extension | photo.jpeg → photo.jpg (new extension jpg) |
| Mark a version | Insert text | note.txt → note_v2.txt (_v2 at position 4) |
One rule at a time: each row is what that rule alone does, with the other rules disabled and the default Base name only scope.
Extensions, duplicate names and characters that break file systems
Find and replace → find jpeg, replace with jpg, applied to photo-jpeg.jpeg Base name only (default) photo-jpg.jpeg Extension only photo-jpeg.jpg Whole file name photo-jpg.jpg Add prefix / suffix → suffix ".bak", applied to a.txt Base name only (default) a.bak.txt Whole file name a.txt.bak
Whether a rule touches the extension is decided per rule by its Applies to dropdown — Base name only (the default), Extension only, or Whole file name — and the block above shows what each choice does to the same input. Names are split at the last dot, so archive.tar.gz has the base name archive.tar and the extension gz. The Whole file name scope splits the name again after the change, which is why a .bak suffix becomes the new extension there but stays inside the base name by default. Two rules ignore the dropdown by design: Add sequential numbers only ever changes the base name, and Change extension only ever changes the extension.
Duplicate names are resolved rather than ignored. Inside a zip two entries with the same path would quietly collapse into one, so a clashing name gets a space and (2) inserted before the extension, then (3), and so on until the name is free. The comparison is deliberately loose: names are compared case-insensitively and after Unicode normalization, so A.txt and a.txt count as a clash, and so do the two ways of writing café.txt. That matches how Windows and macOS behave when you unzip. The count of resolved clashes is shown above the preview table, and as a second line of defence the packer refuses the whole job rather than write two identical paths. For the same reason a file named exactly __proto__ is blocked before packing starts: the packing library keeps entries in a plain object, and that one name would make the file vanish without an error.
Every new name then goes through the cross-platform cleanup in the table below. Not every step announces itself: removed characters, reserved-name rewrites, restored names, flattened folder paths and resolved duplicates are counted in warning lines above the preview, while trimmed trailing dots and shortened long names are silent. Note also that 255 characters is not a hard ceiling — a very long extension, or a (2) suffix added after the shortening, can still push the final name past it.
Two cleanup results are worth checking in the preview. Deleting the entire base name does not always restore the original name: a_tmp.jpg becomes .jpg, with no warning, because a name that starts with a dot is read as a base name with no extension. The original name comes back only when the base name really is empty after cleanup — a file called README with its characters deleted, for example — and that restored name is not cleaned a second time, so unusual characters in it stay as they were. In rare cases a restored name shaped like a path pointing outside the archive stops the pack with a message instead of producing a zip.
| Cleanup step | What happens to the name | Warning shown? |
|---|---|---|
| \ / : * ? " < > | or a U+0000–U+001F control character | Those characters are removed (U+007F and above are left alone) | Yes |
| Trailing dots or spaces on the base name or the extension | Trimmed, because Windows rejects them | No |
| Base name is a reserved Windows device name (CON, PRN, AUX, NUL, COM1–COM9, LPT1–LPT9, any case) | An underscore is appended: con.txt → con_.txt | Yes |
| Base name is empty after cleanup | The original file name is restored as-is, without a second cleanup | Yes |
| Name longer than 255 characters | The base name is shortened, the extension is kept whole | No |
| Two files end up with the same path | A space and (2), then (3), is inserted before the extension | Yes |
| A folder path points outside the archive | That file is placed in the zip's root | Yes |
Warnings are grouped by kind above the preview table, each with the number of files it applies to — so the steps marked No simply happen, and you check them in the New name column.
What the zip keeps, and what it leaves behind
File contents are kept exactly: the zip stores your bytes unchanged, so a renamed photo is still the same photo, pixel for pixel, even if you changed its extension. Folder structure is kept too when you drop a folder on a computer — the relative path is written into the zip, so unzipping rebuilds the same tree, although the folder names themselves are never renamed, since the rules only apply to file names. Non-ASCII names survive: entry names are written as UTF-8 with the zip's UTF-8 flag set, so the program you unzip with knows to read accents, Vietnamese tone marks, Chinese characters and emoji as UTF-8 instead of guessing. Zero-byte files are packed as well, and emoji and accented letters count as one character each in Delete characters and Insert text in current Chrome, Edge, Safari and Firefox — browsers without that text-segmentation support fall back to counting code points, where a combining character can be split.
Modification times are not kept. Only the name and the bytes of each file are handed to the packer, so every entry in the zip is stamped with the moment you packed it, not with the date the original file was last changed. Pack the same batch twice and you get two files that differ in those timestamps. Permissions, owners, symbolic links and macOS extended attributes are not kept either; the browser doesn't hand them to the page in the first place. Empty folders disappear, because a web page receives a list of files and a folder with no files in it is simply not in that list.
One more thing the zip does not do is make your files smaller. This page packs at store level — the files are put into a container without being compressed — on the grounds that batches needing renaming are mostly already-compressed photos, videos and Office documents. The overhead is small and predictable: three files totalling 281,800 bytes came out as a 282,128-byte zip in our test, 328 bytes more, or +0.1%. The cost is about 76 bytes per file plus two copies of each entry name, which is why a tiny file shows it most: a 652-byte file becomes a 778-byte zip.
If what you want is a smaller archive rather than renamed files, use Create ZIP instead — it compresses.
Limits, and the jobs this tool cannot do
Each file can be up to 50 MB and the batch up to 100 MB in total, with a ceiling of 2000 files in one go. Files over the single-file limit are skipped one by one as you add them, with a note saying how many were left out, and the rest are added normally; going over the total size shows a warning and disables the pack button, so you find out before reading every file rather than after. The file list and the preview table each draw at most 300 rows — the files beyond that are still numbered, renamed and packed, and the page says how many are hidden. Reading and zipping happen on the page's main thread, so a batch close to the limits can leave the page unresponsive for a while on a slower machine; there is no measured timing to quote, so split very large jobs if the wait bothers you.
Changing the extension changes the name only. Renaming photo.png to photo.jpg leaves a PNG file wearing a JPG name — most viewers identify images by content and will still open it, but some programs refuse. Renaming cannot convert formats, add a password or encrypt the zip, produce tar, 7z or rar, add files to an existing archive, rename folders, or move files into a different folder. The one case where files change folders is a path that points outside the archive: those files are placed in the zip's root and flagged in the warnings.
Renaming also cannot read anything about a file other than its name. There is no renaming by EXIF data, shooting date, file size or modification date, and no per-file-type counters the way Windows Explorer numbers each group separately — the sequence simply follows the list. The {date} placeholder in Insert text stands for today's date in YYYY-MM-DD form, worked out once when the page loads, not for any date stored in the file. If you leave the page open past midnight, it keeps using the day it loaded.
Everything lives in memory only. Nothing is written to local storage or cookies, so refreshing or closing the tab clears your files, your rules and any zip you already made. Changing a file or a rule also clears a zip you have already packed, deliberately, so a stale download doesn't sit next to a changed preview — the exception being the moment a pack is already running, as described above. If you would rather hand the plan to a spreadsheet — or to a colleague who will run the renaming in a script — Export rename list as CSV gives you an Original name, New name list of the current plan; that button works even when no rule is enabled or a pattern is broken. On phones, folder picking generally is not offered by mobile browsers, so you will usually be selecting individual files and getting no folder structure; whether relative paths come through depends on the browser, not on anything this page switches off.
To turn PNG data into JPEG rather than just change the extension, use Image Converter.
Frequently asked questions
- Does this rename the files on my own computer?
- No. Your original files are left exactly as they are — the page only reads them. What you get is a zip of renamed copies, which you unzip and use to replace the originals yourself. If you picked a single file, you can also download that one renamed file directly instead of a zip.
- Are my files uploaded to a server?
- No. The renaming and packing code is downloaded with the page and runs in your browser, and the file contents never leave your device. The page itself comes from a server, like any web page, and the zip it gives you is not encrypted, so treat it like any other file once you share it.
- How do I rename files as 001, 002, 003?
- Use Add sequential numbers; its default settings turn report.jpg into 001_report.jpg. It is the rule the page starts with, set to start 1, step 1 and padding of 3 digits. Numbers follow the file list from top to bottom, so put the files in order with ↑ and ↓ first. Padding is a minimum, not a limit — the thousandth file becomes 1000 rather than being cut short.
- Can I batch change file extensions — does that convert the format?
- You can change every extension at once with the Change extension rule, but it only rewrites the name. A PNG renamed to .jpg is still a PNG file; most viewers go by the content and open it anyway, while some programs will not. For a real conversion, use an image or video converter.
- What happens if two files end up with the same name?
- The second one gets (2) added before the extension, then (3), and so on, and the number of resolved clashes is shown above the preview. Names are compared ignoring case and Unicode spelling differences, so A.txt and a.txt count as a clash — which matches what would happen when you unzip on Windows or macOS.
- Why is the zip not smaller than the files I put in?
- Because this page packs without compressing — renaming batches are usually photos, videos and Office files that are already compressed. The overhead is tiny and predictable: three files of 281,800 bytes total came out as a 282,128-byte zip, +0.1%. Use a zip compressor if size is the goal.
- Can I rename photos by the date they were taken?
- No. The rules only see the file name and the file's position in the list, never its contents or EXIF data, so shooting dates are out of reach. The {date} placeholder in Insert text adds today's date in YYYY-MM-DD form, worked out when the page loaded.
- Can I bulk rename files on a phone?
- Yes, in any modern mobile browser — pick the files from Files, Photos or your downloads. Mobile browsers generally do not offer a folder picker, so expect to select individual files and get no folder structure. When you tap the save button, the zip opens your share sheet if the browser supports file sharing, and otherwise downloads.