Quick answer
If you have downloaded a few hundred PDFs, edited them outside WordPress, and now need to put them back without rebuilding every link, the thing to preserve is which file belongs where.
Upload the revised set as one batch, match it against the documents already on the site, check anything whose name changed, watch for files used in more than one place, back up before overwriting, and confirm the same public URLs now serve the corrected versions.
WP Bulk Replace does not edit PDFs. It picks the job up afterwards: getting the revised files back to the right places without breaking anything.
Why this is harder than it sounds
The editing is usually trivial: change a phone number in every form, update a footer or a copyright year, swap a logo, fix a typo, add a required disclosure, change one contact name, correct a date.
It is the putting-back that is hard.
With 200 or 300 PDFs, nobody is worried about the edit. They are worried about which of the 300 goes where.
Keep the document’s identity
If a document is still the same document, the page it lives on is worth keeping.
Current Application Form, Employee Handbook, Program Guide, Product Manual — all of those mean “whatever the current one is”.
Uploading the revised file as new media instead gives you a second Media Library entry, a different URL, a suffixed filename, a duplicate, and every existing link still pointing at the old version.
Replacing avoids all five.
Editing software renames things
The files come back as:
policy_revised.pdfpolicy_FINAL.pdfpolicy_2026-09-18.pdfPolicy corrected.pdf
That is enough to defeat anything matching on exact names, which is why the tidying-up step matters — and why the ones it is still unsure about should stay visible rather than being guessed at.
How to run it
1. Keep the revised set clean. Do not mix it with old exports or unrelated documents.
2. Upload it as one job, with a known number of files, so you can tell at the end whether they all landed.
3. Match against what is on the site using filenames, document titles, fields, and any abbreviations you have explained.
4. Work through the exceptions: renamed files, originals that no longer exist, two plausible homes, files used in more than one place, and anything that should be published as new rather than replacing something.
5. Back up before overwriting. Every one, before the write.
6. Replace only the rows you approved. An unresolved row should never be best-guessed into place.
7. Check the corrections are actually there. Open a sample of the public URLs and look at the document.
Documents used in several places
A revised file may be linked from a dozen pages.
That is a bonus when all of them should show the correction — one replacement fixes twelve pages.
It is a problem when one of them is an archive page that should keep the old version. Then the file has to be separated first, or the correction quietly rewrites history.
Do checksums help?
They tell you the file that arrived is the file you sent. That is useful.
They tell you nothing about whether it went to the right place. A perfectly copied file can still be the wrong document on the wrong page, and the checksum will be delighted about it.
Which is why the matching still needs checking.
Example: 300 PDFs, one footer change
An organization has 300 policy and reference PDFs. A branding change means every one needs a new footer.
After the offline edit:
- 270 filenames still match
- 20 came back with
-finalon the end - 6 were renamed by their departments
- 2 documents are no longer current
- 2 are new and have never been published.
A safe run does not “upload 300 files”. It accepts the 270, puts 26 into review, archives or excludes the 2 obsolete ones, places the 2 new ones, replaces what you approved, and confirms the same URLs now serve the revised files.
What this does not do
WP Bulk Replace does not edit PDF contents, certify accessibility, check legal wording, manage records retention, or verify that a revised file was approved by anyone.
Those all belong to whoever did the editing.
Summary
For offline-edited batches: edit elsewhere → upload the revised set → match it to the existing documents → review the exceptions → back up → replace → verify.
The more files there are, the more it matters that every one of those steps is something you can see.
Related: Bulk replace PDFs · Replace hundreds of files safely · Check where a file is used