Batch rename photos
How to Batch Rename Photos on Windows with Dates and Counters
Windows File Explorer can apply a common name and counter, but production photo sets often need capture dates, padded indexes, camera fields, folder names, dimensions, find/replace, and a preview that catches collisions before any file is written.
Use UtiliVera Image's filename template with tokens such as {name}, {index4}, {taken}, {year}, {month}, {day}, {width}, {height}, {folder}, {camera}, and {model}. Review every generated name in Output Plan, then export renamed copies without changing the originals.
Download UtiliVera ImageWindows 10/11 · portable · no signup · no watermarkDesign a name that sorts and remains understandable
For a simple ordered set, use a readable project name plus a zero-padded counter, for example campaign-{index4}. Padded indexes keep 0002 before 0010 in ordinary alphabetical sorting.
For camera archives, combine date parts with the original stem or camera model. A pattern such as {year}-{month}-{day}-{index4}-{name} preserves chronology while retaining a clue to the original file.
Use metadata tokens carefully
Capture-time tokens depend on trustworthy photo metadata. Scans, screenshots, downloaded images, and edited files may lack an original capture date or contain a date written by another tool. Preview fallback behavior before renaming a mixed collection.
Available tokens cover the original name, padded and unpadded indexes, current and capture dates, time, width, height, source size, output format and extension, source folder, camera make, model, ISO, and lens. Literal find/replace and filename case conversion handle recurring cleanup that does not need a token.
Prevent duplicates before processing
Two cameras can generate the same original filename, and several subfolders can contain IMG_0001.JPG. Preserve folders or include a unique date, folder, or counter token when all results will enter one destination.
Open Output Plan and search for duplicate destination paths. Select an explicit collision policy—rename, skip, or atomic overwrite—rather than allowing an operating-system prompt to interrupt a large batch.
Rename while converting only when it helps
Renaming can be combined with conversion, resizing, metadata cleanup, or compression in the same tested recipe. That is efficient for delivery copies, but an archival rename-only project should avoid unnecessary pixel re-encoding.
Keep the originals, export to a separate folder, and retain the batch report as a mapping from every source path to its new name. Test the template on a small representative queue before applying it to thousands of photos.
Verified release
Test the workflow, not a marketing promise.
Version 0.8.0 scored 97.1/100 in an independent final audit with no P0 or P1 findings. Its frozen evidence manifest binds 23 test artifacts to the published executable.
Read the audit summary →Frequently asked questions
Can UtiliVera rename files by capture date?+
Yes. Capture-time and separate year, month, day, and time tokens are available when the source metadata contains those values.
Can I add leading zeros to the sequence number?+
Yes. Use {index4} for a four-digit sequence such as 0001, 0002, and 0003.
Are the original files renamed in place?+
The normal UtiliVera workflow writes planned outputs to a separate destination and keeps originals untouched.
Sources checked
Format, workflow, and comparison details were checked against the primary or official pages below on August 9, 2026.