Skip to content
Free, no signup, nothing saved

Bulk rename images with EXIF dates, in your browser

Drop up to 200 images, type a token pattern (e.g. {date}-{seq:03d}), and download a ZIP of renamed files plus a manifest.csv mapping old to new. The pattern can read the photo date, original filenames, dimensions, camera, and lens from each image. Photos never leave your browser.

  • Processed 100% in your browser
  • No account required
  • Up to 200 files, 100 MB each
Five messy camera-default filenames before, the same five renamed to a clean date-and-sequence pattern after.Five messy camera-default filenames before, the same five renamed to a clean date-and-sequence pattern after.

Drag to compare, before / after

Overview

Photographers, asset managers, and journalists end up doing the same chore over and over: take a folder of camera-default filenames (IMG_1234.JPG, DSC_0001.RAF, _DSC4567.NEF, P5300012.JPG) and turn them into something a human can sort and a CMS will accept. The destination pattern is usually the same: shoot date plus a sequence number, sometimes camera body, sometimes the original basename as a suffix.

Desktop tools (Adobe Bridge, ExifTool, A Better Finder Rename) do this well, but they require an install and a license. Web tools that exist tend to upload your photos to a third-party server, which is the opposite of what you want for a private shoot or an embargoed press release.

BouseMutton runs the rename + ZIP pipeline entirely in your browser. Drop up to 200 files, type a token pattern (the default is {date}-{seq:03d}, which produces 2026-04-28-001.jpg, 002.jpg, etc.), and the preview table shows you exactly what each file will be renamed to. Click Build ZIP and the browser writes a deterministic ZIP archive containing every renamed file plus a manifest.csv mapping old to new. Image bytes never leave the page.

At a glance

Quick facts

The numbers and trade-offs you need before you commit.

  • Where it runs

    Processed 100% in your browser. Nothing is uploaded.

  • Batch cap

    Up to 200 files per ZIP, each up to 100 MB. PNG, JPG, WebP, AVIF, GIF, HEIC, or HEIF.

  • Pattern tokens

    {date}, {time}, {seq:NNd} (NN is 1 to 9), {original}, {ext}, {w}, {h}, {camera}, {lens}.

  • Collision detection

    Case-insensitive by default (matches Windows / macOS filesystems). Switch to case-sensitive for ext4 / btrfs targets.

  • Audit trail

    manifest.csv with old,new header is committed to every ZIP so the rename is reversible in a spreadsheet.

Workflow

How it works

Three steps, usually done inside five seconds.

  1. 1

    Drop your files

    PNG, JPG, WebP, AVIF, GIF, HEIC, or HEIF. Up to 200 files per batch, up to 100 MB each. No sign-up, no credit card.

  2. 2

    Type a rename pattern

    The default is {date}-{seq:03d}, but you can compose any combination of {date}, {time}, {seq:NNd}, {original}, {ext}, {w}, {h}, {camera}, and {lens}. Literals (dashes, underscores, slashes are stripped) are allowed between tokens.

  3. 3

    Review the preview table

    Each row shows the original filename, the resolved new filename, and a status badge (OK, collision, fallback, truncated). Collisions block the Build ZIP button until you adjust the pattern or enable the case-sensitive switch.

  4. 4

    Download the ZIP

    The browser writes a ZIP archive with every renamed file plus a manifest.csv mapping old to new in input order. Open the manifest in a spreadsheet to keep an audit trail of the rename.

Samples

See it in action

Drag each slider to pixel-peep the before and after.

Mixed macOS, GNOME, and CleanShot screenshot names normalised into a single date-stamped sequence.Mixed macOS, GNOME, and CleanShot screenshot names normalised into a single date-stamped sequence.
Mixed macOS, GNOME, and CleanShot screenshot names normalised into a single date-stamped sequence.
Final, _v6_use_this, and approved drafts rolled into a clean acme-co batch with no v-FINAL noise.Final, _v6_use_this, and approved drafts rolled into a clean acme-co batch with no v-FINAL noise.
Final, _v6_use_this, and approved drafts rolled into a clean acme-co batch with no v-FINAL noise.
Date-stamped phone bursts converted to a readable 2026-04-12 shoot sequence with a 3-digit suffix.Date-stamped phone bursts converted to a readable 2026-04-12 shoot sequence with a 3-digit suffix.
Date-stamped phone bursts converted to a readable 2026-04-12 shoot sequence with a 3-digit suffix.
Privacy

Your image, gone when you're done

Runs in your browser

The rename + ZIP pipeline runs entirely in your browser. EXIF parsing, dimension probing, sanitisation, collision detection, and ZIP writing all happen on the main thread or a render-cycle off-thread tick. The image bytes never reach our servers, never touch disk, and are not used to train any model. The only network traffic is a single Plausible analytics beacon (consent-gated) carrying nothing but the page name, the file count, and the alphabetical set of token names used in the pattern.

  • Processed in seconds
  • Nothing saved
  • No account linked
Try it now

Upload an image

One click. No signup. We'll do the rest.

Bulk rename images

Drop your image here or click to upload
PNG, JPG, WebP, AVIF, GIF, HEIC, or HEIF up to 100 MB each. Up to 200 files at a time.

Tokens: {date}, {time}, {seq:NNd}, {original}, {ext}, {w}, {h}, {camera}, {lens}.

Tokens: {date}, {time}, {seq:NNd}, {original}, {ext}, {w}, {h}, {camera}, {lens}.
Your files never leave this browser
Renames are computed locally. Nothing is uploaded.
Glossary

Bulk-rename glossary

Plain-English definitions for the jargon above.

FAQ

Frequently asked questions

Answers to the things most people ask before trying a new tool.

Citing or sharing?

Copy a concise Markdown summary (title, description, FAQ, canonical URL, and citation) ready to paste into an LLM or a doc.

Please cite as

BouseMutton (2026). Bulk rename images [Web application]. https://bousemutton.com/bulk-rename

Last updated: 2026-04-29