Can I undo a bulk rename on my server?
Yes. FTP by Zaweba's operations log keeps every Disk batch, and Undo this batch reverses renames, moves, trashing and permission changes.
Yes, you can. FTP by Zaweba keeps an operations log of everything Disk has done on a server, grouped batch by batch, and a bulk rename is one of those batches. Open the log, find the rename and choose Undo this batch, and the files go back to their original names.
Most FTP clients send a rename to the server and forget about it. If you renamed three hundred files with the wrong rule, putting them back means working out every original name yourself. That is why a proper undo matters more on a server than it does on your own PC, where the Recycle Bin and backups are close at hand.
What the log covers
The operations log lists the changes Disk makes to a server: renames, moves, trashing and permission changes, along with the other things it has done. Renames, moves, trashing and permission changes can be undone as a batch. A bulk rename of a whole folder counts as one batch, so one undo reverses it all.
That makes it a safety net for exactly the jobs that feel risky: cleaning up names across an uploads folder, changing .htm to .html across a site, tightening permissions on a folder tree, or tidying old files into a trash.
Undoing a rename
Open the operations log from Disk. Batches are listed in order, with what each did. Pick the rename you want to reverse and press Undo this batch. The files are renamed back on the server.
If you also used link awareness to update references in your local site after the rename, remember that those local edits were a separate step. They can be undone too, but separately, since they changed files on your PC rather than the server. Undo both, or the pages will now point at the names you just reversed.
Better than needing it
Undo is a net, not a plan. Bulk rename shows a preview of every old and new name before anything changes, and nothing happens until you press Rename. Reading that preview carefully catches most mistakes before they reach the server. Rules can be switched off one at a time to see what each contributes, which is a good way to find the one doing something odd.
Protected items are left out of renames automatically, so files such as .htaccess, wp-config.php and .env, the web root and cPanel folders keep their names whatever rules you add.
Trying rules on one folder first, then on the rest, keeps any mistake small.
Other safety nets in FTP by Zaweba
The operations log sits alongside other protections in the app. Files deleted on the server can go to a server-side trash, and the Trash window has Restore ticked to put them back exactly where they were. Before a Put overwrites a server file, or a Get or a save overwrites a local one, the previous version is kept in local history on your PC, with Compare with current and Restore. Delete Permanently, which skips the trash, warns you first and asks you to type the number of files when folders are included.
Taken together, these mean most mistakes on a site can be walked back. That changes how you work: you can tidy a messy server with confidence instead of leaving it alone for fear of breaking something.
When undo cannot help
Undo reverses what Disk did. It doesn't know about changes made since by other people, by other tools or by the site itself. If someone uploads a file with one of the original names after your rename, putting the old names back could collide with it. Undo soon rather than days later, while the server is still as you left it.
