SmartConvert

New: Batch File Renamer is live — rename files in a folder in bulk, right in your browser. Try it now

Batch File Renamer

Rename files in a folder in bulk with numbers, prefixes, suffixes and text replacement — locally in your browser.

Checking browser support…

Free Online Batch File Renamer

Camera dumps, screenshots and exported assets arrive with chaotic names: IMG_20260918_143522.jpg, Screenshot (12).png, final-v2-REALLY-final.docx. Renaming them one by one is busywork. This batch file renamer fixes the whole folder at once — pick a folder on your device, set one naming rule, check the preview, and apply it to every file in seconds.

Everything happens through your browser's File System Access API. You grant access to one folder, files are sorted by name and renamed in place with sequential numbers, an optional prefix and suffix, the current date or time, or a find-and-replace on the original names. File contents are never read, copied or uploaded; only names change.

How to Use This Tool

  1. Select a folder — click "Select Folder" and grant read/write access. Only direct files are listed; subfolders are ignored.
  2. Pick a naming mode — "Sequential numbers" for 1.png, 2.jpg…, or "Keep original names" to only edit the existing names.
  3. Set the rule — add a prefix (img-), a suffix (-final), the current date (2026-09-18), the current time (14-35-22), or a find-and-replace pair (IMG_photo-).
  4. Check the preview — every current name is shown next to its new name before anything changes. Conflicts block the rename instead of overwriting.
  5. Confirm and rename — the button tells you exactly how many files will change, and progress is reported file by file.

Benefits

  • Sequential numbering — sorted, predictable prefix + number + suffix names with extensions preserved exactly.
  • Date and time stamps — device-local YYYY-MM-DD and HH-mm-ss (no colons, so names stay valid on Windows), shared across the whole batch.
  • Text replacement — global find-and-replace on the filename stem; extensions are never touched.
  • Conflict-safe — duplicate and existing-name collisions stop the run before it starts; chained renames go through temporary names.
  • Private by design — no reads, no copies, no uploads; filenames never leave your device.

Frequently Asked Questions