UAU Ready
Description
WP Staging Pro clones the entire WordPress site in seconds and generates complete backups, copying the database and files to a subdirectory or subdomain with automatic replacement of links and paths. Built for anyone who needs to test plugins, themes, and updates without risking the live version, the plugin runs the heavy operations in the background and works even on low-performance shared hosting.
Key Features of WP Staging Pro
- Subdirectory or subdomain cloning
Creates an exact copy of the production site, database included. - Background processing
Runs cloning and backup without hitting the server’s time limit on large sites. - Automatic search and replace
Adjusts internal links and paths on the cloned site with no manual intervention. - Push plugins and themes to production
Migrates changes validated in the staging environment back to the main site. - Backup upload to cloud providers
Transfers the generated files to external storage beyond your own server.
Benefits of WP Staging Pro
- Live site protected from breakage
Plugin and update testing happens outside production, without taking your store down. - Data under your control
Nothing depends on an external account or third-party service: everything stays on your own server. - Clone invisible to search engines
A no-index meta tag and its own login screen keep duplicate content out of indexing. - Works on modest servers
Shared hosting and large sites complete the process without stalling.
Who Is WP Staging Pro For?
- Anyone running a live WooCommerce store who needs to validate updates before applying them.
- Theme and plugin developers who want a test environment identical to production.
- Agencies and freelancers managing multiple client sites who need a reliable backup routine.
- Anyone migrating a site to another server or domain without losing settings and content.
How to Download WP Staging Pro
WP Staging Pro is available for download here on Ultrapack. The step-by-step for installing this file is in the How to install tab next to the description. Once activated, the plugin creates its own item in the dashboard’s side menu, where the cloning and backup screens live.
Having a staging environment and a backup routine in the same plugin solves two recurring pain points for anyone running production sites: validating changes before publishing and having a recoverable copy when something goes wrong. Since the whole process happens within your own hosting, with no intermediaries, control over your files and database stays entirely with you.
Frequently asked questions
Is WP Staging Pro – Best WordPress Backup Plugin GPL-licensed?
Yes. WP Staging Pro – Best WordPress Backup Plugin is distributed under the GPL (GNU General Public License). You may legally use, modify and redistribute it on as many sites as you want.
Can I use WP Staging Pro – Best WordPress Backup Plugin on multiple sites?
Yes. You can install WP Staging Pro – Best WordPress Backup Plugin on as many sites as you want. Only automatic updates through Ultrapack Auto Updater have a limit: from 3 to 80 sites, depending on the plan.
How much does WP Staging Pro – Best WordPress Backup Plugin cost at Ultrapack?
WP Staging Pro – Best WordPress Backup Plugin costs US$2.99 as a single purchase, and it is also included in the subscription plans starting at US$12/mo (VIP I).
Does WP Staging Pro – Best WordPress Backup Plugin include updates?
Yes. The current version of WP Staging Pro – Best WordPress Backup Plugin is 6.15.1, published at Ultrapack on Sep 24, 2026. Subscribers update straight from the WordPress dashboard with UAU (Ultrapack Auto Updater).
Is WP Staging Pro – Best WordPress Backup Plugin scanned before publication?
Yes. Every version of WP Staging Pro – Best WordPress Backup Plugin goes through a malware scan (ClamAV and YARA rules, at UltraHub) before it is published.
What are the requirements for the plugin WP Staging Pro – Best WordPress Backup Plugin?
Requires WordPress 3.6 or higher and PHP 7.0 or higher. Tested up to WordPress 7.1.
What changed in this version
Version 6.15.1
- New: Enable multipart backups with compression. (Pro) #3423
- New: Show whether each staging site still opens, with a diagnose dialog and a re-check button when it does not. #5645
- Enh: Add database table and file-part metadata to new backups using backup format 2.1.1. #5571
- Enh: Offer WP Staging Pro on the Free first run once the first backup or staging site is ready, and link Pro pricing from the task selector. #6203
- Enh: Provision only the WordPress sites a CI job actually uses so E2E rounds spend less time setting up. #6330
- Enh: Remove duplicated markup and request code behind the backup, staging and command line screens. #6136
- Enh: Replace scheduled backup plans with inline collapsible section on the backup tab. #2093
- Enh: Rework the staging-creation screen into one understandable process with persistent stages, an activity indicator and on-demand diagnostics. #6205
- Enh: Run an E2E round on Blacksmith when it would be second in the queue for our own runners. #6331
- Enh: Share one copy of the database tasks used by backup restore, push and staging. #6134
- Enh: Show the reworked staging process screen when updating or resetting a staging site. #6218
- Fix: Build the log stream REST URL from the host and scheme of each request, so a running job no longer reports an error on sites served under several domains or over both HTTP and HTTPS. #6233
- Fix: Count immediate scheduled backups and keep success open on Escape. #6434
- Fix: Disable the backup modal when updating a staging site. #6401
- Fix: Encrypt Google Drive OAuth tokens in the database. #6246
- Fix: Give WP STAGING's navigation back on the screen that reports the first staging site or backup, instead of holding the screen until the first run is dismissed. #6381
- Fix: Give a new staging site the database credentials in wp-config.php when the live site's wp-config.php is a symlink, as on Bitnami, or loads its credentials from another file. #6374
- Fix: Honor the unit-test resource-threshold opt-out in legacy jobs. #6198
- Fix: Keep MoveHandlerTest reliable on Windows permission checks. #6199
- Fix: Keep WP STAGING's Backup & Migration page reachable during the first run, instead of showing the success screen there as well. #6381
- Fix: Keep WP STAGING's own submenu on screen throughout the first run, and end the first run when one of its entries is picked. #6381
- Fix: Keep a backup the remote refused to delete in the retention list. (Pro) #6338
- Fix: Keep damaged staging site data intact while a staging site is deleted, so the repair notice still has something to repair. #5892
- Fix: Keep delete-guard case-alias tests independent of request timeouts. #6125
- Fix: Keep deselected tables when deleting a staging site. #6193
- Fix: Keep the notification badge beside the WP STAGING menu label. #6400
- Fix: Keep the separate administrator account after a Next-Gen update or reset of a staging site. (Pro) #6388
- Fix: Keep the staging database credentials in wp-config.php after a Next-Gen reset or update of a staging site that uses an external database. (Pro) #6352
- Fix: Let the staging site creation screen be closed with Escape or a click beside it once its job has finished. #6381
- Fix: Let the unit test suite run again; FinalizeMultipartDatabaseTaskTest stopped it loading on every PHP version. #6265
- Fix: Match CPU Load Priority defaults and restore the inline layout. #6109
- Fix: Prevent Free feedback assets from loading on the front end. #5580
- Fix: Prevent TypeError when reading backup DTO fields before they are set. #5636
- Fix: Prevent invalid WordPress Home or Site URLs from crashing WP Admin. #6221
- Fix: Prevent the empty-object warning when plugin information requests fail. (Pro) #3043
- Fix: Regenerate Elementor CSS so layouts survive pushing staging to live. (Pro) #6090
- Fix: Regenerate the English translation template so it matches the strings in the free backup modal. #6306
- Fix: Regenerate the translation template so static_checks passes again. #6322
- Fix: Remote Sync pull gets stuck waiting after the source site has finished preparing the backup. (Pro) #5218
- Fix: Report a backup plan as overdue only when a run it was due to make did not happen, instead of judging the WordPress cron events, take the last run of a plan created before WP STAGING recorded its runs from the backups it produced, and stop the free version reporting backup plans created with WP Staging Pro as overdue. #6347
Release notes published by the developer.
How to install
Automatic updates: this item is updated by the Ultrapack Auto Updater. With it installed, the new version shows up in your dashboard like any other WordPress update (how to set it up).
- Download the file
wp-staging-pro.zip. - In the WordPress dashboard, go to Plugins > Add New > Upload Plugin.
- Select the file
wp-staging-pro.zipand click Install Now. - Click Activate.
Requirements: Requires WordPress 3.6 or higher and PHP 7.0 or higher. Tested up to WordPress 7.1.
Stuck on a step? Open a ticket telling us which one you stopped at.
