The preview is a contract.
The list shows the current name and the name after, for every file, updating on each keystroke. What is on screen is exactly what the disk gets. There is no "apply and see what happens".
macOS · Intel and Apple Silicon
Batch rename files without opening one by one.
NameShift builds the new name from rules you stack, shows you the whole list before touching the disk, and undoes everything with one click if you change your mind.
macOS 13 or later · 15-day trial, no accountRULES3 active
Find and replace
Find:DSC_Replace with:empty — removes the chunk
Insert text
Text:Ana e RuiPosition:At the start
Extension
What to do:Swap one for anotherSwap:jpeg→jpg
Renaming does not convert the file: it stays what it was, it just announces itself differently.
PREVIEW
Original NameNew
- DSC_0001.jpegAna & Rui 2026 0001.jpg
- DSC_0002.jpegAna & Rui 2026 0002.jpg
- DSC_0003.jpegAna & Rui 2026 0003.jpg
- DSC_0004.jpegAna & Rui 2026 0004.jpg
- DSC_0005.jpegAna & Rui 2026 0005.jpg
- DSC_0006.jpegAna & Rui 2026 0006.jpg
- DSC_0007.jpegAna & Rui 2026 0007.jpg
- DSC_0008.jpegAna & Rui 2026 0008.jpg
- DSC_0009.jpegAna & Rui 2026 0009.jpg
9 files · 9 changing · 0 collisions
Rules on the left, the result on the right — the same screen you will be using.
01 · The problem
Bulk renaming is easy. Being sure is not.
Everyone has done it: select the files, hit rename, and find out later that two ended up with the same name, that the numbering skipped, that an extension vanished. The damage shows up a week later, when the client asks for the file.
01
Two files, one name
The rule that looked right lands two files on the same name. One of them is gone — and you find out when the client asks.
02
Numbering that skips
Sorted by date here, by name there, and the sequence comes out with holes. Redoing it means opening the whole folder again.
03
No way back
Renamed, closed, done. With no record of what things were called, "undo" becomes an afternoon of manual work.
02 · How it works
Rules that stack. A list that does not lie.
You build the recipe on the left and read the result on the right, file by file, as you type.
Six rules, in the order you want.
Find and replace, insert text, remove text, number, UPPERCASE/lowercase and extension. Each one is a card: drag to reorder, switch it off to test without losing its setup. Order matters — and it stays in plain sight.
- Find and replacestrip "IMG_" from everything, or swap one chunk for another
- Insert textat the start, at the end, or at the position you choose
- Remove texta literal chunk or a range of characters
- Numberstart value, step, leading zeros and where it lands in the name
- UPPERCASE / lowercaseab · AB · Ab · Ab cd, each button showing its result
- Extensionstandardize .JPG and .JPEG, or swap one spelling for the other
A collision locks the button.
If two files would land on the same name — or the name already exists in the folder — those rows turn red and the rename button stays off until you fix it. The comparison ignores case, because the Mac disk ignores it too.
Undo that actually undoes.
Every operation is recorded with the from-to of each file. One click on "Undo last" puts all the old names back. And the swap happens in two stages, so renaming A to B and B to A simply works.
You own the order.
The list opens sorted by name. Click the header to reverse it, or drag a row where it belongs — numbering follows the order on screen, not the one the system picked.
03 · Honesty
What it does not do.
Renaming does not convert files. Turning .png into .jpg changes the label only — the file stays what it was, and NameShift says so in amber when you ask for it. Nothing is rewritten, recompressed or moved: the content is yours and stays untouched.
04 · In your work
Where this hurts in your work.
Client delivery
The card gives you DSC_0431. The client wants "Ana and Rui Wedding — 001". That is 600 files, and the name has to come out right the first time.
Graduations and events
Each class with its prefix, numbering continuing across folders, and the same recipe reused at the next event without rebuilding anything.
Archive and backup
Standardizing years of material from different cameras: uppercase extensions, old prefixes, names nobody can find in search.
Any file, not just photos
Contracts, audio, video, the finance PDF. NameShift touches the name — what is inside is none of its business.
05 · Pricing
One purchase, two Macs.
No subscription. The version you get today keeps working forever; a year of new versions is included.
LICENCE
US$ 15one-time payment
Covers 2 Macs. Each extra Mac is US$ 8, and you pick how many at checkout.
Buy a licenceUPDATES
1 yearincluded
New versions for a year. After that the app keeps working: it just stops getting new ones.
TRIAL
15 daysno account
Download and use it on your own files. No email, no card, no account.
Price in reais for Brazil. Outside Brazil: US$ 15, also a one-time payment.
06 · FAQ
Questions.
Does it change the contents of my files?
No. NameShift changes the name and, if you ask, the extension. The content is never opened, rewritten or recompressed.
What if I rename them wrong?
"Undo last" puts every previous name back. The record of the operation stays on your Mac — the last ten of them.
Can it rename files inside subfolders?
Yes. Drop the folder: NameShift walks all the way down and lists the files. In v1 it renames files, not the folders.
Which order does the numbering follow?
The one on screen. The list opens by name, you reverse it from the header or drag rows around — the number follows what you see.
Does it work on external drives or network volumes?
Yes, on any volume Finder can see. On a network, renaming depends on the server’s permissions.
Do I need an internet connection?
Only to activate the licence and to check for updates. Renaming is entirely local.
Put things back in order.
Try it for 15 days with your own files. No account, no card.
Download for MacmacOS 13 or later · Intel and Apple Silicon · Version 1.0.2 · 4,4 MB© 2026 NameShiftmacOS 13 or later · 15-day trial, no account