Quick answer
Replace files one at a time when you have a few and you already know exactly what each one replaces. Use a batch when the incoming set itself needs working out, checking, verifying, or doing again next month.
There is no magic number where “a few” becomes “bulk”. Five confusing files can justify a proper review; twenty perfectly named ones might take ten minutes by hand.
The better question is: how much deciding is there per file, and what does one wrong replacement cost?
The number of files is only the first clue
One correction is easy: you know the document, you know the new file, and one person can check it afterwards.
Two hundred is obviously different.
Most real jobs are in between. A department sends 18 revised PDFs. If every filename matches a document exactly, that is repetitive but simple. If those 18 contain department abbreviations, date tokens, two renamed programs and three documents that have never existed before, it needs judgement.
Four questions that decide it
1. Do you know where every file goes?
If yes, doing them individually is fine.
If you have to search the Media Library, open pages, consult a spreadsheet or work it out from the filenames, then the deciding is the job — and it is worth having all of it in one place where you can see it.
2. Are the filenames reliable?
Compare:
parking-application.pdf → parking-application.pdf
with:
Parking Form FINAL 9-2026.pdf → resident-parking-request.pdf
The first needs no thought. The second might well be right, and it needs somebody who knows the site to say so.
3. What happens if one is wrong?
Getting a decorative image wrong is visible the moment anyone looks at the page.
Getting a permit form, a benefits guide, a safety sheet or an application wrong produces a download that works perfectly and is the wrong document. Nobody notices until somebody submits it.
Higher consequence justifies more checking, even for a modest number of files.
4. Will you do this again?
A one-off cleanup can absorb a lot of manual effort.
Monthly reports, annual handbooks, catalogs, forms and course documents come back. Those benefit from something that remembers the decisions you made last time.
The free plugin contains the whole replacement workflow. Pro remembers your corrections, so the same naming habits do not need explaining every cycle.
A rough decision tree
- One file? Do it individually, unless the document is unusually risky or you are not certain where it goes.
- A few, all obvious? Individual replacement is still efficient.
- A few, and you are not sure about them? Upload them together and look at the matches.
- Dozens or hundreds? Use a batch, unless you already have this safely automated somewhere.
- It comes round every month? Keep what you worked out rather than solving the same naming problem twelve times a year.
Three corrected PDFs
A communications manager has a press kit, a media fact sheet and a speaker bio.
Each one has an obvious home and is used in one obvious place.
Doing those individually is faster than setting up a batch. Do that.
Twelve school handbooks
A district receives 12 revised handbooks named by school abbreviation:
BHS-HB-26.pdfCMS-HB-26.pdfNORTH-HB-FINAL.pdf
and the site uses full school names.
Twelve is not many. But putting one school’s handbook on another school’s page matters, and the work here is identity matching rather than uploading — so a batch with a review step is the right call even at twelve.
Sixty monthly reports
A team replaces the same 60 PDFs every month.
The value is not only speed. It is repeatability: upload the complete set, spot the missing or extra ones, look at the exceptions, replace the approved rows, and verify the month as a unit.
And because it recurs, remembering last month’s corrections is worth more each time.
A hundred optimized images
An image team exports 100 reprocessed images with the same filenames.
That looks like the ideal bulk job, and images bring extra questions: the generated sizes, whether thumbnails need regenerating, caches and CDNs, and whether the dimensions or format changed.
Do not assume the same filename makes an image behave like a PDF. There are five or six files behind every image, so check how your theme serves them before replacing a batch on a live site.
What a batch should actually add
Batching should add control, not just a bigger upload button.
What you want: a list of what arrived, suggested matches, the unmatched and uncertain ones visible rather than buried, a review step before anything is written, backups and a way back, a check afterwards, and a clear record of what happened.
A “bulk” tool that only writes 200 files faster, without helping you check 200 decisions, is a way of making mistakes at speed.
When a script is better
A team with a predictable deployment pipeline — file identity guaranteed, changes reviewed in version control, rollback proven — should use the script.
This is for when the people doing the mapping are editors and administrators working inside the site, rather than engineers working inside a deployment system.
When doing it by hand is better
When the job is genuinely small and obvious.
Do not add a process because one exists. The point is to make difficult multi-file work safer, not to turn a two-file correction into a project.
FAQ
How many files counts as bulk?
There is no number. How complicated the mapping is, how often it repeats, and what a mistake costs all matter more than the count.
Can I use it for a small batch?
You can. Whether you should is a different question — if every document is obvious and there are only a few, doing them individually is simpler.
Does Pro unlock bulk replacement?
No. The free plugin has the whole replacement workflow, with no file limits. Pro remembers what you fixed, so recurring work gets quicker.
Summary
Choose by how much deciding is involved, not by an arbitrary file count.
Individual replacement is ideal when you already know where everything goes. A batch earns its overhead when the set needs mapping, checking, exception handling, repeating, or verifying as a whole.
Related: Bulk replace files in WordPress · Replace hundreds of files safely · WP Bulk Replace vs Enable Media Replace · File replacement vs a script