Batch Rename Images

1. 1
   Add your files: Drop in photos, RAW files, HEIC images or videos — anything you want renamed.
2. 2
   Pick a starting point: Choose a preset such as Date + sequence, or write your own pattern.
3. 3
   Build the name: Tap tags like {name}, {n}, {date} and {camera} to insert them into the pattern.
4. 4
   Check the preview: Every old name and its new name are listed side by side before anything happens.
5. 5
   Download or rename in place: Take one archive, or let Chrome rename the files in your own folder, with undo.

A folder of IMG_4821.JPG tells you nothing. Renaming by capture date, camera or a sequence turns a pile of files into something you can search, sort and hand to somebody else — and doing it to two hundred files by hand is an afternoon.

• Chronological order: Names built from the capture date sort correctly in every file manager and every upload form.
• Consistency: One pattern applied to the whole set, instead of two hundred slightly different decisions.
• Nothing is re-encoded: Only the name changes. Pixels, EXIF, colour profiles and embedded thumbnails come out byte for byte identical.
• Safe to check first: Every new name is listed beside its old one before a single file is written.
• Clashes handled: Two files that would end up with the same name are numbered apart automatically.

A pattern is ordinary text with tags in braces. Everything outside a tag is written literally, so photo-{n} produces photo-1, photo-2 and so on. Type them or tap them in.

Your files are sorted, the pattern is evaluated for each one, find and replace runs on the result, the letter case is applied, the extension is settled, the name is made safe for a filesystem, and anything that would still clash is numbered apart. That order matters, and it is the same order every time.

• Capture date, not file date: The date comes from EXIF DateTimeOriginal where the file has one, and the tool says so when it has to fall back.
• Find and replace: Plain text or a full regular expression, with capture groups like $1.
• Case conversion: lower, UPPER, Title, kebab-case and snake_case.
• Sorting: By name, capture date, size or type — and name sorting is number-aware, so IMG_2 comes before IMG_10.
• Numbering that tracks the batch: Leading zeros are widened automatically when the count needs more digits.
• Rename in place: In Chrome and Edge the files in a folder you choose are renamed directly, with a single undo.

Any of them. Nothing is decoded to rename a file, so format support is not a question of what a browser can open — it is only the small preview thumbnail that needs a decoder, and a file without one is still renamed.

• Photos: JPG, PNG, WebP, GIF, BMP, AVIF and TIFF, with a preview for each.
• RAW: CR2, CR3, NEF, ARW, DNG, ORF, RW2 and RAF. Capture date, camera and model are read straight from the file.
• HEIC and HEIF: iPhone photos, including their capture date, whether or not the browser can display them.
• Video: MP4 and MOV, using the creation time the camera recorded in the file.
• Everything else: Renamed by name, size and file date. A file with no preview shows its type instead of a picture.

Whenever the names you have are not the names you need: a memory card straight off a camera, a client delivery that has to follow a naming standard, a set of frames that must sort in order, or an old folder nobody can search.

• Photo libraries: Put a whole shoot into date order with names that stay sorted anywhere.
• Client deliveries: Apply an agreed naming standard to a hundred files in one press.
• Frames and sequences: Zero-padded numbering so 2 does not sort after 10.
• Uploads: Strip the characters that upload forms and servers reject.
• Archive cleanup: Turn IMG_0001 into something a search can find.

A few things worth knowing before you rename a folder you care about.

• The renamed files are byte-for-byte identical to the originals — only the name is different.
• Capture dates are read from the file's own header, which is why RAW and HEIC work.
• Names are made safe automatically: path separators, control characters and reserved Windows names cannot get through.
• Two files that would end up with the same name are numbered apart, so nothing is silently lost.
• Everything happens on your device. No file and no file name is sent anywhere.

A rename is easy to get right and awkward to undo, so it is worth two minutes of care.

• Read the preview before you commit — it lists every old name against its new one.
• Use leading zeros whenever the batch passes nine files, or the order falls apart.
• Sort by capture date before numbering if you want the numbers to follow the shoot.
• Keep the extension unless you have a specific reason not to; changing it does not convert the file.
• Try the pattern on a few files before running it over a whole card.

When not to use it

• Do not rename files that something else refers to by name — a website, a project file, a database.
• Avoid changing names that an automated pipeline expects to match a fixed shape.
• Check with whoever receives the files if a naming standard has been agreed.
• Renaming does not convert anything: a file called photo.png that was a JPEG is still a JPEG.

Reads each file's header rather than decoding it, so a hundred photos are ready in well under a second.

• Image merger
• Image splitter
• Collage maker
• Image filters