Camera batches
Turn files such as DSC_12345.JPG into project names with dates and sequence numbers without manually editing hundreds of names.
Bulk file renamer · local only
Rename a folder without guessing what will happen.
Drop files, build a rename rule, and see every new filename before anything changes. Download renamed copies as ZIP, or export PowerShell and Bash scripts to rename originals on your own computer.
Step 1
Drop files or choose a folder
RenameDeck reads filenames and metadata in your browser. It does not upload file contents.
Tokens:
{name}{n}{date}{yyyy}{mm}{dd}Step 2
Check the preview
| # | Original | New name | Size | Status |
|---|
Choose files or load the example to start.
Important: browsers cannot safely rename arbitrary original files on every operating system. ZIP export creates renamed copies. PowerShell and Bash exports let you review a script before renaming originals yourself.
Why this exists
Useful when “rename” means more than adding one prefix.
Archives and downloads
Normalize spaces, case, prefixes, suffixes, and numbering while catching duplicate output names before they become a mess.
Cross-platform handoff
Use ZIP when you need renamed copies, CSV when you need an audit trail, or shell scripts when you want local in-place renaming.
How is this different from an upload renamer?
RenameDeck does not send files to an application server. Filename rules, preview generation, and ZIP creation happen in the browser.
Can it handle folders?
On browsers that expose folder selection, relative paths are preserved in the preview and renamed ZIP.
Does it change originals?
No. The browser version creates renamed copies or scripts. Your originals stay untouched unless you deliberately run an exported script.