Checking folder access.
Bulk Rename opens a folder in place, which needs the File System Access API. It is available in Chromium browsers such as Chrome, Edge, Brave and Opera on desktop.
Related tools
- Batch ProcessorRun a text transform over many files and write the results back, safely.
- Duplicate FinderFind identical files in a folder tree by content, then reclaim the space.
- Archive ViewerBrowse and extract zip and tar archives without unpacking them to disk.
- Folder DiffCompare two folders on your own machine and see exactly which files were added, removed, or changed by content hash.
- Compression LabRun text or files through gzip and deflate, compare sizes, and inspect compressed data.
- Hex ViewerInspect binary files byte by byte with reusable struct templates.
What it does
Renames a whole folder of files in one pass, in the browser, against the real files on your disk. Five modes cover the usual jobs: find and replace (with optional regular expressions and $1 group references), a template with {name}, {ext}, {n}, {counter}, {parent} and {date} tokens, a case change (lower, upper, title, kebab, snake or camel), a numbered sequence with a prefix and zero padding, and a clean up pass that strips accents, tidies spaces and drops characters that cause trouble later. A glob or regex filter narrows the job to the files you actually mean, such as *.jpg. Every plan is checked for names that collide before a single file is touched.
How to use it
Choose a folder, and the tool reads it in place and shows a table of every file with the name it would get. Tweak the pattern and the table updates as you type, so you can see the result before committing to it. When it looks right, press Apply renames, review the exact list of changes, download the undo file, and confirm. Files are only renamed inside their own folder: nothing moves between folders and subfolders are never renamed.
Why this one
Desktop bulk renamers are installs, and the web ones cannot touch real files, so people end up scripting it and hoping. This one previews every change against your actual folder and writes an undo file before it renames a single thing, all locally. Renames come out in an order that lets a whole run shift down by one without a file overwriting the next, and anything that would collide is held back and listed rather than left to fail halfway through.
FAQ
- Can I undo a bulk rename?
- Yes. An undo file listing the reverse of every rename is offered as a download before anything is written, and again afterwards. It is a plain JSON list of the old and new names, so you can replay it here or read it in any editor. Renames are also never destructive: a rename onto an existing name is refused rather than overwriting it.
- Does it rename subfolders too?
- It renames files only, including files inside subfolders, but it never renames a folder itself. That is deliberate: renaming a folder moves everything under it at once, and a mistake there is much harder to walk back than a mistaken filename.
- Are my files uploaded anywhere?
- No. The folder is opened in place through the browser File System Access API and read in this tab, so your files and inputs never leave your device. There is no server side for this tool and no API endpoint, which is also why it needs a Chromium browser such as Chrome, Edge, Brave or Opera on desktop.
Keyboard shortcuts: press ? anywhere on this page to see them.