Rename.Tools LogoRename.Tools
FeaturesGuidesApp
RRename.Tools

A powerful browser-based batch renaming tool. Supports regex, rule chains, live preview — all processing done locally with complete privacy.

100% Local Processing, Zero Data Upload

Legal

  • Terms of Service
  • Privacy Policy
  • Disclaimer

Resources

  • All Features
  • Guides
  • GitHub
  • Report an Issue
  • Changelog

Languages

  • English
  • 中文
  • 日本語
  • Español
  • Français
  • 한국어

© 2026 Rename.Tools. All rights reserved.

Made with by developers

Back to guides

Getting started

Batch file renaming basics: import, preview, execute

Batch renaming works best when you treat it like a reviewable change: import a small set, add one rule at a time, and only execute after the preview is clean.

9 min readUpdated 2026-05-22

Start in Sample Test Mode

Sample Test Mode is the safest way to learn the interface because it does not ask for file permissions and cannot change anything on disk. You paste or generate filenames, then test the same rules you would use on real files.

For a first run, use a mixed set of names: a few camera files, one document, and one video filename. Mixed examples make it obvious which rules are too broad and which ones only affect the intended files.

Rename.Tools sample test mode with six imported filenames and an unchanged preview
Use Sample Test Mode to rehearse a workflow before selecting real files from your device.
  1. 1Open the app and click Try Sample Test Mode in the file panel.
  2. 2Paste one filename per line, including the extension, such as IMG_0421.jpg.
  3. 3Click Import Files inside the sample panel.
  4. 4Confirm the file list and preview both show the same unchanged names.
  5. 5Keep Scope set to Name so the first rules do not accidentally rewrite extensions.

Build one rule at a time

A reliable batch rename workflow is a sequence of small, reviewable edits. Add the cleanup rule first, check the preview, then add numbering. If the preview changes something unexpected, the last rule you added is the easiest place to look.

This example removes a camera prefix and adds a padded sequence number. It is intentionally simple: the goal is to learn how the rule chain changes the preview before you use more advanced variables or regex.

Rename.Tools rule chain with Find and Replace plus Sequence rules updating the preview
Add rules one by one and check the preview after each change. Here the sequence rule updates all six sample files.
  1. 1Click Add Rule and choose Find & Replace.
  2. 2Set Find to IMG_ and leave Replace with empty to remove the prefix.
  3. 3Click Add Rule again and choose Sequence.
  4. 4Keep Sequence type as Numeric, Start value as 1, Step as 1, and Zero padding as 3.
  5. 5Review the Preview panel and make sure the numbered results match your intended order.
IMG_0421.jpg2026-05-22_001.jpg

Remove IMG_, insert a date prefix, then add a padded sequence.

IMG_0422.jpg2026-05-22_002.jpg

Read the preview like a checklist

The preview panel is not just a visual nicety; it is the review step. Scan the Original column first, then the New Name column, and look for changes that do not match the rule you thought you wrote.

Use Affected Only when the list is long. It hides unchanged files so you can focus on what will actually be renamed. Use Conflicts Only whenever the conflict count is non-zero, because duplicate target names must be fixed before execution.

  1. 1Check that every changed file still has the correct extension.
  2. 2Check that no new name is empty or only a number.
  3. 3Check that numbering order matches the file order you want.
  4. 4Check Conflicts Only before execution, even if the list looks clean.
report (final).docx005report (final).docx

This may be technically correct but not desirable; it tells you the sequence rule is affecting documents too.

Execute directly or export a script

In Chromium browsers, Rename.Tools can directly rename files selected through the File System Access API. In Firefox or Safari, or when you want a reviewable command-line workflow, export a script instead.

Script export is also useful for teams: one person can build and review the rename plan in the browser, then run the generated Bash or PowerShell script in a controlled folder.

  1. 1For real files, start with a small folder or a copied test folder.
  2. 2Click Export Plan if you want a plain mapping of old names to new names.
  3. 3Click Export Script when direct browser renaming is not available or you prefer terminal execution.
  4. 4Click Execute Rename only after the preview and conflict checks are clean.
  5. 5After execution, use Undo immediately if you notice a mistake.

Common first-run mistakes

Most mistakes come from applying a rule to more files than intended. If only photos should change, filter the file list first or build the rule so it matches only photo-style names.

Another common mistake is changing the full filename when you only wanted to change the name part. Keep Scope on Name for most workflows; switch to Ext or Full only when the guide or your own plan explicitly requires it.

movie.name.s01e03.1080p.mkv006movie.name.s01e03.1080p.mkv

A global sequence rule can affect every selected file. Filter or split batches when file types need different naming rules.

Related guides

Create stable filenames with sequence numberingUse regular expressions for batch file renaming

Ready to try the workflow?

Open Rename.Tools, add a few sample files, and preview every rule before touching the real filenames.

Start renaming