drag & drop, click, or paste from clipboard
Drop to add
drag & drop, click, or paste from clipboard
Download a batch job and the default filenames are whatever your camera or phone generated: IMG_7441.jpg, IMG_7442.jpg, or worse — a flat dump named by timestamp with no meaningful order. Before those files reach a client folder, a CMS upload field, or an asset library, they need real names. Doing that by hand for 80 or 200 files is the kind of task that makes people question their career choices.
Enhydra RPO renames every output file according to a pattern you define before the job runs. Tokens in curly braces expand per file: original name, a padded sequence number, the processing date, output width, output height. Combine them with fixed text and separators to produce exactly the filename convention your workflow demands — client codes, campaign identifiers, dimension strings, whatever the brief requires — without touching a single file after the ZIP arrives.
{name} — the original filename without its extension. Preserves the shoot identifiers already in your filenames while appending new structure around them. A file named DSC_0041.jpg becomes whatever you wrap around DSC_0041.
{index} — a zero-padded sequence number assigned in upload order, starting at 1 (or a custom start value you set). Padding width is calculated automatically from the total batch size: 50 files use two digits, 200 files use three. product_001.jpg through product_200.jpg sort correctly in every file explorer, server, and CMS without any collation tricks.
{date} — the date the batch was processed, in YYYYMMDD format. Useful for archiving — campaign_20260612_001.jpg tells you exactly when the export was made without opening the file.
{width} and {height} — the pixel dimensions of the output file. Handy for multi-resolution delivery: if you resize to 1200px and 400px in separate runs, naming outputs hero_{width}.jpg keeps them straight. Both tokens reflect output dimensions, not input — so they account for any resizing applied in the same job.
These patterns cover the most common delivery scenarios:
Tokens can appear multiple times in one pattern and in any order. Fixed text can include hyphens, underscores, dots, and alphanumeric characters. The extension is always set by the output format you chose — the pattern controls only the base name.
Sometimes a batch is not the whole job — it is a continuation. You photographed 50 products yesterday and named them 001–050. Today you have 30 more and you need them numbered 051–080 so everything imports into the catalog in one unbroken sequence.
Setting a custom start index means the sequence begins at 51 rather than 1. Combined with automatic zero-padding that accommodates the full eventual catalog size, the second batch slots directly behind the first with no renaming and no gaps. The same applies when re-exporting a subset: pick a start index that avoids collisions with files already delivered.
Batch rename runs as part of the same processing job as any other active tool. No extra step, no second download. The names in the ZIP are already correct when it arrives.
It reflects the output dimensions after any resizing applied in the same job. If you resize to 800px wide, {width} inserts 800 — not the original camera resolution. This makes it reliable for naming multi-resolution asset sets.
Not if your pattern includes {index}. Without {index}, files that share an original name would collide — for example, {name} alone when two uploads have the same filename. Including {index} guarantees uniqueness across the whole batch.
Letters, digits, hyphens, underscores, and dots are safe across all operating systems. Avoid spaces, slashes, colons, and special characters — they cause problems on Windows paths and in URLs.
Yes. Rename can run as the sole active tool, leaving pixel data untouched while only the output filenames change. Combine it with any other tools — compress, resize, convert — or run it alone.
It captures the date the job was submitted, not the time each individual file finished. All files in one batch get the same date token, which keeps the naming consistent even for long-running large batches.