by
Bohdan Smaha
0 (0 reviews)
WPBR Bulk Replace
Replace hundreds of PDFs and documents at once: match new files to posts, review every pairing, back up, replace, and roll back if needed.
WPBR Bulk Replace ranks #69,909 among WordPress.org plugins with 0+ active installations, is #5,824 of 6,651 in the Media category, and was last updated Oct 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.3.0
Current Version v1.3.0
Updated 3 days ago
Last Update on 29 Oct, 2026
Refreshed 2 days ago
Last Refreshed on
#5,824 of 6,651 in Media
Actively maintained
Rank
#69,909
—
No change
Active Installs
0+
—
No change
KW Avg Position
N/A
—
No change
Downloads
104
+4 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
42,341
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 10 more installs to reach 10+
Rank Changes
Current
#69,909
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.3.0
- Last Updated
- Oct 29, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.1.4
- PHP Version
- 7.4 or higher
- Author
- Bohdan Smaha
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Jetpack – AI Agents & MCP, Security, Backup & Analytics
3M+ installs
#17
Advanced Custom Fields (ACF®)
2M+ installs
#28
Image Optimizer – Compress Images and Convert to WebP or AVIF
1M+ installs
#58
EWWW Image Optimizer
1M+ installs
#60
Regenerate Thumbnails
1M+ installs
#64
Smush – Image Optimization, Compression, Lazy Load, WebP & CDN
1M+ installs
#65
Imagify Image Optimization: Optimize Images | Compress & Convert to WebP/AVIF
900K+ installs
#68
Smart Slider 3
800K+ installs
#78
Frequently Asked Questions
Common questions about WPBR Bulk Replace
No. Nothing is written until you tick rows and click through the Back up and Replace step, and every file replaced is copied to a backup folder first.
Yes. Processed rows can be rolled back from the batch screen for as long as their backup exists. Deleting backups is always a deliberate action, never automatic.
By default, nothing is removed. Your batches, history, settings and backups stay in place and are picked up again if you reinstall. There is a setting to opt in to full removal. Turning it on and then deleting the plugin permanently destroys staged files and backups — which means processed rows can no longer be rolled back — along with the plugin's tables and settings. It never touches your Media Library, the replacement files now live on your site, or the meta values on your posts. Externally pinned staging or backup directories are not deleted automatically during uninstall and must be removed manually if desired.
They are two editions of the same plugin by the same author. WP Bulk Replace is distributed from wpbulkreplace.com and updates from there; WPBR Bulk Replace is the WordPress.org edition and updates from WordPress.org. Features and data are the same. Because they share their data, only one can be active at a time. If one is active, the other declines to activate and says why. Neither edition deactivates, removes or changes the other.
Deactivate WP Bulk Replace. Activate WPBR Bulk Replace. Your batches, history, backups and settings are picked up as they are. Optionally, delete WP Bulk Replace from the Plugins screen while WPBR Bulk Replace is active. WPBR Bulk Replace then keeps the shared data, even if "Delete all data when the plugin is deleted" is switched on. Switching back works the same way: deactivate WPBR Bulk Replace, activate WP Bulk Replace, then delete WPBR Bulk Replace if you like. Deleting WPBR Bulk Replace never deletes the shared data while WP Bulk Replace is installed. One case is not protected. If "Delete all data when the plugin is deleted" is switched on, and you delete WP Bulk Replace while WPBR Bulk Replace is installed but not active, WP Bulk Replace's uninstaller deletes the shared batches, history, backups and settings, exactly as that setting says. WPBR Bulk Replace cannot step in, because an inactive plugin runs no code. To avoid it, delete WP Bulk Replace while WPBR Bulk Replace is active, or switch that setting off first (it is off by default). The Plugins screen warns about this while WPBR Bulk Replace is active and the setting is on.
Yes, and it is the better place for them. Backups are copies of live documents, so a folder inside uploads relies on a deny rule that some servers ignore. Point the plugin somewhere else in wp-config.php: define('WPBR_BACKUPS_DIR', '/path/outside/webroot/wpbr-backups'); define('WPBR_STAGING_DIR', '/path/outside/webroot/wpbr-staging'); Either constant overrides the matching field on the Settings screen, which then shows the folder read-only. The path must be absolute; the folder is created if it does not exist. The folder fields on the Settings screen deliberately cannot do this — they only accept paths inside wp-content, because a path typed into the admin should not be able to direct writes anywhere on the server. I replaced a file, but my site still shows the old one. Usually the replacement worked and a browser, a caching plugin or a CDN is showing a copy it saved earlier. Replacing keeps the file's address on purpose, so nothing that links to it breaks — and a cache cannot tell the file changed. Under Bulk Replace → Settings, "Add a version to links to replaced files" is on by default. It adds a small marker such as ?updated_on=20261014-093015 to the document links (PDF, Word, Excel and similar files) WordPress builds from your Media Library on your public pages, for files this plugin replaced, so browsers fetch the new file. Nothing stored is changed. It does not reach links typed into your content (including the File block), images, audio or video, or pages that a cache has saved a copy of until you clear that cache. If a download or preview feature on your site stops working for a file you replaced, turn the setting off.
No. Updates come from WordPress.org like any other plugin from the directory. The only request the plugin makes itself is to your own site, to check that its backups folder is not publicly readable. Links to the Help Center open in your browser only when you click them.
Yes, that is what it is for. Put the new files in a batch, match them to posts, review the pairings, then replace in bulk. The workflow is upload, match, review, then back up and replace. Practical limits, so you can plan: PDF, DOC and DOCX files are accepted by default, and the contents are checked, not only the extension. Browser uploads go one file at a time with a progress bar; for a very large set, copy the files into the staging folder over FTP and scan instead. Replacing runs in small chunks (5 files per request by default, adjustable in Settings), so the browser tab has to stay open while it runs; if it closes, finished rows stay finished and you can run the rest. The plugin does not cap the number of files, but your server's disk, memory and time limits still apply. Matching only proposes: filenames that are too different from the post's title need a manual correction on the Review screen.
The plugin in the directory works on one site at a time: each site has its own batches, backups and settings. To replace files across the sites of a network in one reviewed job, with a backup on each site, you need WP Bulk Replace Pro and its optional Multisite add-on, which is sold separately. Each covered site needs Pro. Details: https://wpbulkreplace.com/add-ons/multisite/
Plain custom fields that hold a file URL work in this edition. Replacing files held in Advanced Custom Fields file and image fields, including fields inside a repeater or flexible content layout (one repeating level), needs WP Bulk Replace Pro. It repoints a file that is already there; it does not create ACF fields, rows or layouts. More: https://wpbulkreplace.com/pro/
