Free Bulk Image Renamer — Pattern, Sequence & Date Tokens

What is the Bulk Image Renamer — Pattern, Sequence & Date Tokens?

Bulk Rename is a client-side image-renaming utility. Upload any number of images, define a pattern with simple tokens ({n}, {orig}, {ext}, {date}), preview the result, and download a ZIP containing the originals under their new names. Files are not re-encoded — just repackaged.

Key features

• Token-based naming: {n} {orig} {ext} {date}
• Configurable start number and zero-padding
• Live preview of the first five filenames
• Original bytes preserved — no re-encoding
• Unlimited files per batch
• Output as a single ZIP
• 100% client-side — no upload
• Free, no signup, no watermark

How it works

The browser File API reads your uploaded images as Blobs. For each file, the tool evaluates the pattern with the current sequence index and the file's metadata, then adds the Blob under the new name into a JSZip archive. The archive is generated and downloaded in one operation. Because the bytes are not touched, output quality and metadata are identical to the input.

Why use this tool

Desktop bulk renamers are powerful but platform-specific (Windows-only, Mac-only, or terminal-only). Online renamers usually cap at 20 free files. PikDraw's bulk rename has no cap, runs on every OS, never uploads, and preserves the original image quality byte-for-byte.

Common use cases

• Rename a wedding-day folder to wedding-2026-{n}.jpg
• Standardise product photo names for an e-commerce import
• Prefix dates onto a long-running archive
• Convert sequential camera filenames into descriptive ones
• Prepare files for a CMS that requires a specific naming convention
• Clean up screenshots with timestamps into a tidy series
• Reset numbering across multiple project deliveries

How to use this tool

1. Upload your images — Drop a folder of any image type. File order matches upload order, which is usually filesystem order — re-upload in a different sequence if you need a custom order.
2. Write a naming pattern — Patterns use simple tokens: {n} for the running number, {ext} for the original extension, {orig} for the original filename (without extension), {date} for today's date in YYYY-MM-DD. Combine freely, e.g. wedding-{date}-{n}.{ext}.
3. Set start number and zero-padding — Start at 1 (or 100 to keep sort order across multiple shoots). Padding 3 → 001, 002, … 999. Padding 4 → 0001, 0002 — use enough digits that lexical sort matches numerical sort.
4. Preview the first five names — The preview block shows exactly what each filename will be. Adjust tokens until it reads correctly — there's no undo after download.
5. Download the ZIP — All files are repackaged with the new names into a single ZIP. Originals are not modified. Drop the ZIP into the destination folder and unzip.

Who should use this

Photographers archiving shoots. E-commerce store owners preparing product image imports. Marketers cataloguing brand assets. Designers tidying up screenshots. Anyone migrating images between platforms that have different naming conventions.

How to get started

Drop your folder, type a pattern like 'shoot-{n}.{ext}', set padding to 3, click Rename & Download ZIP.

Best practices

• Always zero-pad so files sort correctly
• Use lowercase and hyphens for web compatibility
• Include a date or project token for archival clarity
• Test the pattern on a small batch first
• Keep originals until you've verified the ZIP
• Avoid special characters that break filesystems (: / \\ ? * " < > |)
• Use {orig} to layer new context onto existing names

Pro tips

• Always zero-pad enough digits — 'photo-9' sorts after 'photo-10' alphabetically.
• Include {date} in archival batches so a folder is self-describing two years later.
• Use lowercase, no spaces — web and Unix friendly.
• Test the pattern on a 5-file batch before renaming hundreds.
• Keep your originals — there's no in-place rename, but you can delete the originals after verifying the ZIP.

Expert insights

Limitations to be aware of

• Cannot rename files in place — outputs a ZIP only
• No regex / find-and-replace mode
• No conditional logic per file
• Image files only
• Single pattern per batch
• Very large batches (10 000+) may slow down ZIP generation

Frequently asked questions

Does this rename files in place on my disk?

No. Browsers can't modify your filesystem from a tab. The tool reads your uploaded files, packages them under the new names into a ZIP, and downloads it. You then unzip into a destination folder and delete the originals if you wish.

What tokens are supported?

{n} = sequence number (with zero-padding). {ext} = original file extension. {orig} = original filename without extension. {date} = today's date as YYYY-MM-DD. You can combine them freely: {date}-shoot-{n}.{ext}.

What is zero-padding and why does it matter?

Operating systems and most upload tools sort filenames lexically (string order), not numerically. Without padding, 'img-2' comes after 'img-10'. Padding 'img-002' makes lexical and numerical order identical. Use 3 digits up to 999 files, 4 up to 9 999.

Can I keep the original names?

Yes — use the token {orig} in the pattern. For example, '{date}-{orig}.{ext}' will prefix today's date onto every existing filename while preserving everything else.

Will image content change?

No. The tool repackages the original bytes — pixels, EXIF, ICC profiles, everything — under new names. No re-encoding. The output ZIP unpacks to identical-quality files.

Is there a limit on file count?

There is no server cap. Browsers handle thousands of small files comfortably; very large folders (10 000+) may slow down the ZIP step. Process in chunks of a few thousand if your batch is enormous.

Are my files uploaded?

No. The tool reads files via the browser File API, repackages them locally with JSZip, and triggers a download. Nothing leaves your device — safe for confidential project files.

How do I rename non-image files?

The picker is restricted to image types. To rename arbitrary files, you'd need a desktop tool such as Bulk Rename Utility (Windows), Renamer (Mac), or `mmv` on Linux.