Question 1

Are my images uploaded to a server?

Accepted Answer

No. All renaming, optimization, EXIF parsing, perceptual hashing, and ZIP packaging happens locally in your browser via the Canvas API, exifr, and Web Workers. Your files never leave your device — this is the single biggest privacy advantage over server-based batch tools.

Question 2

What rename tokens are supported?

Accepted Answer

Tokens available in the pattern field: {index} (1-based position in the queue), {counter} (configurable start/step/pad), {original} (original filename without extension), {date} (file last-modified date YYYY-MM-DD), {exif:date} (EXIF DateTimeOriginal, falls back to {date} when missing), and {width}x{height} (post-resize dimensions). Combine with prefix, suffix, find-replace, and case transforms (lower/kebab/snake).

Question 3

How are filename conflicts handled?

Accepted Answer

After applying your rename rule, the tool scans the resulting names. Any duplicates are auto-resolved by appending an incrementing suffix (e.g. photo.jpg, photo-1.jpg, photo-2.jpg). Conflicts are highlighted in red in the preview table, and a warning badge tells you how many names were auto-suffixed.

Question 4

What image formats are supported?

Accepted Answer

Input: JPEG, PNG, WebP, GIF, BMP, and HEIC (HEIC is decoded via heic2any which lazy-loads only when a HEIC file is detected, keeping the initial bundle small). Output: JPEG, PNG, WebP. AVIF output is not yet supported because the browser Canvas API does not expose AVIF encoding — this is deferred to a later phase that will add a WASM encoder. For now WebP gives the best size/quality ratio in modern browsers.

Question 5

How does this differ from the standalone Image Compressor tool?

Accepted Answer

The existing image-compressor tool focuses on compress/resize/convert for a small set of files. This tool layers a full rename engine on top (tokens, sequence counter, find-replace, case transforms, EXIF/date substitution), adds a drag-reorder live preview table, perceptual-hash duplicate detection, audit CSV/JSON export, watermarking, history with localStorage, and shareable URL presets. If you only need to compress a few images, use image-compressor; if you need to rename + optimize a large batch with a consistent pattern, use this tool.

Question 6

Can it handle hundreds of files?

Accepted Answer

Yes. Processing runs in a Web Worker pool (OffscreenCanvas when available, main-thread fallback otherwise) so the UI stays responsive. A memory cap (~256 MB total) is enforced; if you exceed it the tool pauses and warns you. ZIP output is built incrementally so even large batches download as a single archive without holding every blob in memory at once.

Question 7

What extras are included beyond the core feature set?

Accepted Answer

Ten extras: (1) operation history with localStorage (last 10 runs, one-click re-apply), (2) shareable URL presets (config encoded in the URL hash), (3) audit CSV/JSON export (full old-to-new name + size map), (4) perceptual-hash duplicate detector (skips near-duplicate images even with different filenames), (5) side-by-side thumbnail diff viewer, (6) live throughput dashboard (files/sec, MB processed, ETA, peak memory), (7) per-format quality matrix preview (5 quality levels side-by-side), (8) visual folder-structure editor for output tree, (9) bulk EXIF metadata inspector panel, (10) text watermark embed with position/opacity/color.

Question 8

Does this strip EXIF metadata?

Accepted Answer

Optionally. Canvas re-encoding inherently drops most original metadata; the 'Strip EXIF' toggle (on by default) confirms this behavior. Turn it off only if you specifically need to preserve metadata — note that EXIF-based rename tokens like {exif:date} still work because EXIF is read from the source file before re-encoding, regardless of the strip setting.

Bulk Image Renamer + Optimizer

Bulk Image Renamer + Optimizer

How to use

Bulk Image Renamer + Optimizer