Add the images to rename
Choose up to the batch limit. The tool does not need to decode or re-encode the image just to change the filename.
Build a shared filename pattern for the batch, switch to individual mode for exceptions, preview every resulting filename, then download the original image bytes under their new names.
Renaming changes filenames only. The original image extension, bytes, quality, metadata and visible pixels are left unchanged.
Bulk Rename does not decode or re-encode the image. It keeps the original bytes and prepares new download filenames from a pattern such as image-001.jpg. Switch to Edit individually when a few images need custom names.
Visible pixels, compression quality and embedded metadata remain exactly as they were in the uploaded file. Only the downloaded filename changes.
Build filenames from reusable tokens, preview the entire batch, customize exceptions when needed, and download the original image bytes under their new names.
Choose up to the batch limit. The tool does not need to decode or re-encode the image just to change the filename.
Use {name}, {number} and {ext}, then choose a starting number and number padding such as 001, 002 and 003.
The queue shows the resulting names. Switch to individual mode if a particular image needs a custom filename.
The original extension and bytes stay unchanged. Multiple renamed files are packaged into a ZIP for download.
Bulk Rename is a filename operation, so it is useful before or after editing when you want consistent file naming without changing image contents.
Changing a filename or extension text does not convert image data. ConvertAnyFile therefore keeps the original source extension instead of creating misleading filenames.
Answers about filename patterns, numbering, source extensions, unchanged image bytes and ZIP downloads.
No. Renaming does not decode or re-encode the image. The downloaded file keeps the original image bytes.
The tool preserves the original source extension so the filename continues to match the actual image bytes. Typing another supported image extension in a custom name does not convert the file.
The current pattern supports {name} for the original filename stem, {number} for the generated sequence and {ext} for the source extension.
Duplicate generated names are made unique automatically so the prepared batch does not contain conflicting filenames.
Use a related browser-based tool when the next task is metadata cleanup, resizing, compression or cropping.