PDF & Documents
Bulk rename files from a CSV list
Upload your files as a ZIP together with a CSV of new names. You get the renamed files back and an index that maps every new name to the old one.
or drop it here
- ZIP / CSV
- Up to 2,000 files
1 prepared source file · 196 bytes
- Files: 2
- Collisions resolved: 0
renamed-files.zip · rename-index.csv · findings.csv · manifest.json
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
Rename a batch of files and keep a map back
Upload a ZIP and set the naming pattern
You upload your files as a ZIP together with a CSV of new names, up to 2,000 files per job. You enter a filename pattern before the run. The preview lists every old and new name side by side, so you can fix the pattern before a single file is written. Your upload is never changed. The renamed copies go into a new ZIP, and the limit is shown before you upload.
Renamed files and an index to undo it
You download renamed-files.zip, rename-index.csv and findings.csv. The index maps every new name to the old one, so you can reverse the rename later. Checksums, short fingerprints of each file, show that the contents did not change on the way. A manifest.json file records what you uploaded and a summary of the job. Compare a few entries in the index with the files in the ZIP before you replace your originals.
Name collisions and names that fail
The collision setting decides what happens when two files end up with the same name. Stop halts the job, and Append counter adds a number to the end. Every resolved collision is written into the index. Some names fail outright: paths that point outside the archive, names reserved on Windows, names that are too long, and names that would clash on another system because of upper and lower case. These stop the job because they tend to break quietly at the destination.
Questions before you run it
How do I describe the new filenames?
With a filename pattern entered before the run. The preview lists every old and new name, so the pattern can be corrected before a single file is written.
Are my original files changed?
No. Renamed copies are written into a new ZIP and the upload is left as it was. A rename index and checksums ship with the package so the mapping can be walked back.
What happens when two files end up with the same name?
The collision control decides: Stop halts the job, Append counter adds a numeric suffix. Either way, every resolved collision is written into the index.
Which names are rejected outright?
Paths that escape the archive root, names reserved on Windows, and entries whose length or cross-platform casing would clash. These are hard failures, because that class of problem breaks silently at the destination.
How many files can one job cover?
Up to 2,000 files. ZIP and CSV are both accepted as sources, and the ceiling is shown before upload rather than discovered part way through.