Quick answer
When a client sends you a folder of revised PDFs, images or downloads, the slow part is not uploading them.
It is working out which file on their site each one replaces, which names no longer line up, which are new, whether anything you are about to overwrite is used elsewhere, and what actually changed once you are done.
A batch workflow turns that folder into a list of decisions instead of an afternoon of manual replacements.
The email every agency knows
It always sounds simple:
Here are the updated files. Can you replace the versions on the site?
The ZIP has 80 files in it. There is no spreadsheet. The names were made up by whoever exported them from the client’s internal system.
You now have to reconstruct the mapping yourself, by hand, from names you have never seen.
Why doing it manually costs so much
The loop is:
- work out where this file goes
- find the existing one
- replace it
- check it
- do it again.
Step 1 is the expensive one. If 100 files take two minutes each just to identify, that is over three hours before a single file is replaced.
Turn the folder into a batch
A batch takes all of them at once, suggests where each one goes, shows you how sure it is, pulls the uncertain ones into their own list, lets you send any file somewhere else, flags the ones that are new, checks nothing you are replacing is used outside the job, runs only once you have approved it, and tells you what happened to every row.
That splits the thinking from the doing, which is what makes it delegable.
Letting the client check the ambiguous rows
Sometimes you genuinely cannot tell. HRG-2026-v2.pdf means something to the client and nothing to you.
Export the batch, send the handful of rows nobody at your end can resolve, and let the project manager, the client contact or their content editor confirm where they go — without giving anybody a WordPress login.
When it comes back, every row is checked again before it changes anything. The spreadsheet moves decisions around; it does not get to overwrite files on its own authority.
Repeat clients are where Pro earns its money
You see the same client’s naming habits every quarter.
“HRG” is the Human Resources Guide. “FIN” is Finance. FINAL on the end of everything means nothing. That department was renamed two years ago and the filenames never caught up.
Pro remembers all of that, per site, so the next quarter’s batch arrives with those corrections already applied. It also finds files attached through ACF fields and sitting on WooCommerce products, which is most of what makes a client’s site awkward in the first place.
That knowledge lives on the site rather than in one person’s head, so whoever picks up the next batch starts where the last one finished.
Shared files are the agency risk
The client says:
Replace the PDF on this page.
That same PDF is on ten other pages.
Overwrite it without checking and you have changed nine things nobody asked you to change — and you will find out from the client, not from your own process. A batch that stops on shared files puts that in front of you before it happens.
Undo matters more on client work
Clients change their minds. The message you get is always:
Can you put the old one back?
Undoing one file is a two-minute job. Restoring the whole site from last night’s backup because of one PDF is not.
Example: quarterly maintenance
A client sends:
- 60 revised product documents
- 10 forms
- 8 new resources
- 4 files from departments that have been renamed.
A safe run:
- upload all 82
- let the obvious revisions match themselves
- send the 4 renamed-department rows to the client
- mark the 8 new resources as new
- check the shared files before touching them
- replace the rows you approved
- verify
- send the client a short summary of what changed.
Licensing
Every paid plan includes every Pro feature. The only difference between them is how many sites you can use it on — one, five or fifty. Nothing is held back from the smallest plan.
For an agency that is usually the five- or fifty-site plan, since the same client habits turn up on every site you look after. See the pricing page for current prices.
When you do not need this
If the client sends three files and tells you exactly where they go, replace them by hand. It will be quicker.
This becomes worth it when the batch is big, the names are inconsistent, someone else has to check them, the job repeats, or you need to be able to undo one thing.
Making it a repeatable service
Agencies can turn this into a standard procedure:
Intake. Ask for the folder, which site, any mapping notes they have, and who signs it off.
Review. Produce a summary: clear matches, uncertain, new, held back.
Client approval. Send back only the exceptions. Nobody wants to approve 80 rows.
Run it. Replace the approved rows, with backups.
Report. Replaced, added, skipped, still unresolved, and how long undo is available.
Written down like that, it is a job you can hand to someone else.
It also makes estimates more honest
Quoting “80 uploads” tells you nothing.
Quoting batch setup, the number of exceptions, client review and verification tells you a great deal — and the exception count predicts the effort far better than the file count does.
Summary
For agencies the useful shape is: client folder → upload → auto-match → resolve the exceptions → get approval → replace → verify → undo if they change their mind.
The value is not only speed. It is that the job becomes reviewable, repeatable and something you can delegate.
Related: Bulk replace files · File-name matching · Plugin workflow vs custom script