Are my photos uploaded?

No. The entire rename + ZIP pipeline runs in your browser. The image bytes never reach our servers and nothing is saved on disk. The only network traffic is a single Plausible analytics beacon (consent-gated) so we can count batch sizes and pattern usage, with no filenames in the payload.

Which tokens can I use in the rename pattern?

Nine tokens: {date} (YYYY-MM-DD from the photo date, or the file modified date, or the upload time), {time} (HHmmss from the same chain), {seq:NNd} (sequence number padded to NN digits, where NN is 1 to 9), {original} (the original filename without extension), {ext} (lowercase extension), {w} and {h} (image dimensions in pixels), {camera} (camera make + model in kebab-case), and {lens} (lens model in kebab-case). Anything else is rejected as a parse error.

What happens if two files would resolve to the same name?

The tool detects collisions case-insensitively by default (matching Windows and macOS default-filesystem behaviour) and refuses to build the ZIP until you adjust the pattern or flip the case-sensitive switch. The colliding rows are highlighted in the preview table and announced through an aria-live region for screen readers.

What does the manifest.csv contain?

Two columns and one row per file in input order: an "old,new" header followed by lines like "IMG_1.JPG,2026-04-28-001.jpg". The manifest is committed to the ZIP root so you have a permanent audit trail of what was renamed to what, even if the ZIP is later split or repacked.

Why did some files get renamed to image-001.jpg instead of my pattern?

The sanitiser strips path separators, control characters, and Windows-forbidden glyphs, then trims leading dots and trailing whitespace. If the resulting basename is empty or pure underscores (which can happen when {original} resolves to "..." or when every character was filtered out), the engine falls back to image-NNN to avoid producing an unwriteable filename. The fallback rows are flagged in the preview.

How big a batch can I run?

Up to 200 files per ZIP, each up to 100 MB. The ZIP writer is deterministic (same inputs always produce the same output) and the main thread stays responsive because EXIF parsing is incremental.

Kostenlos, keine Anmeldung, nichts gespeichert

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.

Drop your files Convert HEIC to JPG instead

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.

Ziehen zum Vergleichen, vorher / nachher

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.

Auf einen Blick

Quick facts

Die Zahlen und Kompromisse, die du brauchst, bevor du dich festlegst.

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.

Ablauf

So funktioniert es

Drei Schritte, in der Regel in unter fünf Sekunden erledigt.

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
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
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
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.

Beispiele

Sieh es in Aktion

Ziehe jeden Schieber, um Vorher und Nachher Pixel für Pixel zu vergleichen.

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.

Date-stamped phone bursts converted to a readable 2026-04-12 shoot sequence with a 3-digit suffix.

Datenschutz

Dein Bild ist weg, wenn du fertig bist

Läuft in deinem 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.

In Sekunden verarbeitet
Nichts gespeichert
Kein Konto verknüpft

Jetzt ausprobieren

Bild hochladen

Ein Klick. Keine Anmeldung. Wir erledigen den Rest.

Bilder im Stapel umbenennen

Lege deine Dateien ab

Lege dein Bild hier ab oder klicke zum Hochladen

PNG, JPG, WebP, AVIF, GIF, HEIC oder HEIF bis 100 MB pro Datei. Bis zu 200 Dateien gleichzeitig.

Umbenennungs-Muster

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

Groß-/Kleinschreibung in Namen unterscheiden (erweitert)

Deine Dateien verlassen diesen Browser nie

Umbenennungen werden lokal berechnet. Nichts wird hochgeladen.

Glossar

Bulk-rename glossary

Verständliche Definitionen für die Fachbegriffe oben.

FAQ

Häufig gestellte Fragen

Antworten auf die Fragen, die die meisten Leute stellen, bevor sie ein neues Werkzeug ausprobieren.

Mehr Werkzeuge

Zitieren oder teilen?

Kopiere eine knappe Markdown-Zusammenfassung (Titel, Beschreibung, FAQ, kanonische URL und Zitierung), bereit zum Einfügen in ein KI-Werkzeug oder ein Dokument.

Markdown-Spiegel ansehen

Bulk rename images with EXIF dates, in your browser

Übersicht

Quick facts

So funktioniert es

Drop your files

Type a rename pattern

Review the preview table

Download the ZIP

Sieh es in Aktion

Dein Bild ist weg, wenn du fertig bist

Bild hochladen

Bilder im Stapel umbenennen

Bulk-rename glossary

Häufig gestellte Fragen

Verwandte Werkzeuge

Convert HEIC to JPG

View EXIF metadata

Extract colour palette

Zitieren oder teilen?