MassiveRenamer
A program to rename many files at once on Windows and macOS, inspired by Lupas Rename (Windows only, frozen in 2004): combinable rules, a preview that flags problems before touching anything, and an undo that works even after closing the program.
The problem
It happens to everyone sooner or later: a hundred photos all named IMG_4821.jpg, a series’
season with its names in a mess, a folder of documents where the capitals are random. Renaming
them by hand is a nightmare; renaming them with a program is another matter, if the program is
good. There’s Lupas Rename, a free classic for Windows, which exists only there and hasn’t been
updated since 2004. For the Mac there’s nothing equivalent, so I made one for both:
MassiveRenamer.
What it does
Rules combine, show up at once in the preview and are applied all together. Each group has its own checkbox in the title: unticked, it does nothing and its fields are greyed out, but the values stay. After a successful rename all the boxes switch off, so the next batch can’t inherit a rule by accident.
- replace the whole name, or search and replace (regular expressions included), now with several pairs at once;
- cut characters from the left or right, or remove and insert at a given position;
- put in a date: modified, created, or the one inside a photo (its EXIF data, read by a small parser of my own);
- change upper and lower case, in several ways;
- add text before or after the name;
- number with a start value, increment, digits, position and separator;
- change, capitalise or remove the extension.
A path bar above the list shows the folder the files come from and can be typed in, with
folder completion, to jump to another one. In the preview, the parts of the new name that change
are highlighted, and the order can be set by hand (arrows move the selected files). The
list can be re-filtered or emptied without starting
over, with a filter (*.jpg;*.png), subfolders and hidden files
as you choose; order matters, because numbering follows it, and numbers inside names sort as
numbers (img2 before img10).
Before renaming, the preview tells you everything
The real job of a program like this isn’t renaming: it’s not ruining anything. So the preview flags, before doing anything: duplicate names, files that already exist, characters the system doesn’t allow, Windows’ reserved names, empty names. An existing file is never overwritten.
Two steps for the hard cases
Renaming a to b and b to a seems harmless, but done one file at a time the first step
overwrites the second. Likewise, going from foto.jpg to FOTO.JPG on Windows and Mac is a
tricky case, because the system treats the two names as the same file. The solution is to
make the moves in two steps, through temporary names: first everything goes to a neutral
name, then each goes to its final name. That way swaps and case-only changes work.
An undo that survives
The last renames are written to disk, so they can be undone even after closing the program,
and now several levels back (the last twenty). The last rules used are also in the File menu. For
those who prefer another way, there’s an export of a script (.bat on Windows, .sh on
Mac) that redoes the rename, along with the one that undoes it. Rules can be saved to and loaded
from a file.
How it’s built
A Python project with a Qt (PySide6) interface, in Italian and English, chosen from the Language menu. The part that matters, the engine (rules, preview, rename, undo, scripts), is independent of the interface and covered by tests. Executables are built with PyInstaller; a Mac can’t build the Windows one, so CI does it, producing them for Windows, Apple Silicon Mac and Intel Mac on every change. As with GBFileCopier, the main branch is protected: you work on a separate branch, open a pull request and merge only with the checks green on all three platforms; there are also automatic dependency updates and secret scanning.
It updates itself, but only if you let it
Since 29 October the program can update itself. At first start a bar asks whether to check for news every day: until I answer yes, it contacts no one. If a newer version exists it offers “Install and restart”. The mechanism is the same one I wrote for GBFileCopier, with the same precautions: the file is downloaded only from the project’s releases page and must match the hash listed in the checksums file. On Windows the new program takes the place of the one in use (the old one becomes a file to delete at the next start); on Mac the downloaded app’s version is checked and a script replaces it after quitting, putting the old one back if something goes wrong. From source, or in a folder that can’t be written to, the button just opens the release page. A version tag on GitHub, which must match the one written in the code, triggers the build and publishes the release.
Right-click, and one window at a time
The missing piece was reaching the program from where files already are. On Windows it adds entries to the context menu of files, folders and a folder’s background; on the Mac, a Quick Action in Finder. Selecting many files and launching the program repeatedly must not open many windows, so there is now a single instance: the second launch hands its paths to the first and exits. Here continuous integration caught a real bug: if the sender didn’t wait for the first to acknowledge, Windows lost the paths.
Status
0.1.0 was published on 29 October 2026, and the same evening 0.1.1. A lesson from the first: its Mac app had a broken signature, because the version was written into the bundle after signing, so downloaded copies were reported as “damaged”; the release notes point to 0.1.1, the first signed and notarized Mac build. On 30 October I did what had been missing: the real automatic update from 0.1.0 to 0.1.1, by hand, on the Mac and on Windows (rename, undo, update), and it worked. That also means the Windows interface has been tried by a person. 0.2.0, published the same day, brought the new rules, the right-click menu and the single instance; I haven’t yet seen the Explorer entries and the Finder’s Quick Actions with my own eyes. The project moved to the GPL-3.0 license.
Then came a round of housekeeping. The interface now has its own tests, run without a screen on every change, with screenshots saved by the build. The executables got lighter by dropping the parts of Qt the program never uses: the Mac app went from 104 to 69 MB, the Windows one from about 50 to 28. And since a missing library only shows when the program starts, the build now launches the packaged program in a self-test on each platform; a library removed by mistake stops the change. All of this, plus the path bar, manual order and multi-level undo, came out as 0.3.0 on 31 October, with a Mac app of 23 to 26 MB and a Windows executable of 28. Checksums verified, the Mac app notarized.
The self-test itself taught a lesson. On the Intel Mac build machine the run hung for 52 minutes: the system service that supplies icons simply doesn’t answer there, and when the window is activated Qt waits for an icon forever. Nothing in the program was wrong. The build now probes that service first and, if it’s dead, skips the part that needs it, leaving a warning; the self-test also prints the time of each phase and has a 60-second watchdog that shows where it got stuck..
0.4.0, on 31 October, brought real installers. On Windows there is now a per-user installer (Start menu entry, an optional right-click menu entry, and an uninstaller that removes it too), and the single-file version stays as the portable one; an installed copy updates by downloading the installer and running it silently once the program has closed. On Mac there is a .dmg with the app and the Applications shortcut, signed and notarized. Its release run failed once: the Intel build machine lost its network while waiting for Apple’s notarization, so notarization now polls for the result every 20 seconds, retries on errors and gives up only after an hour. 0.5.0, on 7 November, added the checkboxes and a more readable preview, after I saw weak contrast on the Windows dark theme and a leftover trim: colours per light and dark theme, and the changed parts in dark text on solid yellow. The new notarization worked first time on both Macs, and I checked that the automatic update works and the new preview reads better. I haven’t confirmed the update path through the Windows installer, since I’m not sure which copy was updated. The Windows executable is still unsigned.
Anyone who wants to support the project will find an entry in the Help menu, a link in the About window and a README section, with a PayPal donation: paypal.me/GiulioBanterla.
Stack
Python · PySide6 (Qt) · PyInstaller · pytest · GitHub Actions · GPL-3.0