Get Started
Wp Staging Pro featured image

WP Staging Pro v6.18.0 - WordPress Staging Sites Made Easy

Developer: WP StagingCategory: WordPress PluginsTrusted with 710 downloadsPro11 favoritesLatest v6.18.0Updated 1w ago

Features: Cloning - Create a clone of your website with a simple click Push Changes - Copy Plugins, Theme & Media files from Staging to Live site Authentication - Staging Site is available for auth...

Related items

Related Givewp Plugins

Give Recurring Donations Addon icon

Give Recurring Donations Addon - WordPress Plugin

by Liquid Web

Adds support for recurring (subscription) donations to the Give donation plugin.

Give Fee Recovery Addon icon

Give Fee Recovery Addon - WordPress Plugin

by Give

Ask Your Donors to Cover Gateway Processing Fees.

Give Form Field Manager icon

Give Form Field Manager Addon

by Give

Form Field Manager (FFM) allows you to add and manage additional fields for your Give donation forms using an intuitive drag-and-drop interface.

Features:

  • Cloning – Create a clone of your website with a simple click
  • Push Changes – Copy Plugins, Theme & Media files from Staging to Live site
  • Authentication – Staging Site is available for authenticated users only
  • High Performance – Cloning process does not slow down your website loading speed
  • Secure – WP Staging is coded well for protection of your data

Please note: This first version does not copy any database entries. It pushes your file changes from the staging to the live site which is a real time saver after testing plugin and theme updates.

Recent releases

Release history

View all 15 versions
v6.18.0LatestVerified Safe
Oct 21, 20264.0 MB
Other
  • Enh: Apply security hardening. Updating is strongly recommended. #7051
  • Enh: Back up large databases much faster. #7011
  • Plus 40 more fixes. #7163
  • WP STAGING | PRO Backup & Cloning | Full Changelog:
  • [https://wp-staging.com/wp-staging-pro-changelog/](https://wp-staging.com/wp-staging-pro-changelog/)
Fixed
  • A backup restore no longer stops when the database is briefly unreachable. #5561
  • Backup plans keep their own schedule when edited, so saving one unchanged no longer makes it run hourly. (Pro) #6473
  • Create staging sites inside wp-content when the site root is not writable. #6846
  • Keep live media files intact when updating or pushing a Next-Gen staging site with symlinked uploads. #7017
  • Large backups uploaded to Dropbox no longer stay at 99%. (Pro) #6986
  • Long backup names and notes in Japanese, Chinese, Cyrillic or emoji no longer break the backup. #7014
  • Stop a push when its safety backup fails, instead of pushing without a restore point. (Pro) #6903
Oct 10, 20263.8 MB
View changelog
Added
  • Add secure transfer sessions for backup downloads. Backups are no longer offered as permanent public URLs. Instead Download Backup and Share Backup Link create a short-lived, tokenized transfer link on click that the webserver serves statically, so PHP never streams the backup and large downloads can not run into PHP timeouts. #5449
  • Protect the permanent backup directory against direct HTTP access on Apache and IIS, and add a backup folder security self-test with a small, expandable notice that says what to ask the hosting provider when the folder is still reachable. #5449
Other
  • Enh: Advertise the Pro auto login feature below the button that opens a new staging site in the free version. #6360
  • Enh: Ask OneDrive for a whole page of entries when listing backups, instead of leaving Microsoft Graph on its default of 200 per request. (Pro) #5913
  • Enh: Limit "Create Blank WP Site" to the Business plan and above. (Pro) #6725
  • Enh: Show the ten newest remote backups first and keep the rest behind a "Show more" button, so a large remote backup folder does not slow the backup list down. (Pro) #5913
Fixed
  • A backup no longer fails when a theme, plugin or media file has a modification date before 1970 or after 2106. #6582
  • A second cancellation that starts while one is still running now waits for it instead of stopping it silently. #6623
  • Background jobs could fail to find their queue table on sites that use SQLite. #6756
  • Clone the subsite that source-blog-id names in the WP-CLI staging-site-create command instead of the current blog. (Pro) #6268
  • Correct the .htaccess rewrite base for multisite network clones. (Pro) #6137
  • Delete the Remote Sync settings when WP Staging Pro is uninstalled. (Pro) #6764
  • Finish deleting a split backup once every part was deleted, instead of ending the request without a reply. (Pro) #6784
  • Finish the remote backup list when one of several storages answers with an error, instead of leaving the loading indicator running and the "No remote Backups found" message out of date. (Pro) #5913
  • Hash the whole backup once instead of twice when a remote upload checks a file already on the remote storage. (Pro) #6498
  • Include Remote Sync logs and timestamps in bundled downloads. (Pro) #6640
  • Keep bundled log downloads inside the 14-day retention window instead of including logs of any age. #6713
  • Keep every job log entry on one line, so a line break in an error message can no longer forge log entries. #6758
  • Keep passwords out of corrupted staging sites reports and remove temporary report files. #6131
  • Keep storage access tokens out of the request error that reaches the job log and the debug log. (Pro) #6631
  • Keep the live site's database prefix while listing a push's tables, so the rest of that request no longer reads or writes the staging site's tables. (Pro) #6772
  • Keep the run day and the missed-run record of a backup plan when only its retention is changed. (Pro) #6479
  • Keep the staging creation screen open after pressing Stop instead of reporting the job as cancelled from another page or opening a status error popup. #6455
  • Let the Delete wpstg-restore.php button remove the restore tool without a Developer or Agency license. (Pro) #6706
  • Make wp wpstg status report running, finished and failed jobs correctly. (Pro) #6787
  • Name the failed backup in upload failure reports. (Pro) #6551
  • Offer the staging site's login page instead of a session-expired error when the license is not active. (Pro) #6708
  • Open the backup explorer on backups with many files instead of failing with an HTTP 500 memory error. #6667
  • Post every failed scheduled backup upload to Slack, a repeated one at most once per hour, and send Slack error reports even with error emails off. (Pro) #6551
  • Preserve clone settings when continuing past the database grant warning. (Pro) #6712
  • Preserve production wpstg_queue and wpstg_settings during Legacy Push. (Pro) #6693
  • Purge the LiteSpeed page cache after a restore, also when the restore replaced or deactivated the LiteSpeed Cache plugin. #6779
  • Read every page of the backup listing on Google Drive, OneDrive and the S3 storages, so the backup list and retention see every stored backup. (Pro) #5913
  • Reading and checking plugin settings could hang or come back empty on sites that use SQLite. #6751
  • Refuse a subsite backup whose blog ID names no subsite of the current network, or names one that is archived, suspended or deleted. #6403
  • Remote Sync push no longer logs a setTmpDatabasePrefix() TypeError on every queue tick. (Pro) #6773
  • Repair a missing queue column when the stored schema version is current. #6693
  • Report a backup file that reached the server's file size limit as such, with what to do about it, instead of as a full disk. #6862
  • Retry a scheduled backup report email that could not be sent. #6551
  • Retry opening the Google Drive upload session after a network error instead of cancelling
Sep 24, 20263.7 MB
View changelog
Added
  • Enable multipart backups with compression. (Pro) #3423
  • Show whether each staging site still opens, with a diagnose dialog and a re-check button when it does not. #5645
Other
  • 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
Fixed
  • 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
  • Count immediate scheduled backups and keep success open on Escape. #6434
  • Disable the backup modal when updating a staging site. #6401
  • Encrypt Google Drive OAuth tokens in the database. #6246
  • 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
  • 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
  • Honor the unit-test resource-threshold opt-out in legacy jobs. #6198
  • Keep MoveHandlerTest reliable on Windows permission checks. #6199
  • Keep WP STAGING's Backup & Migration page reachable during the first run, instead of showing the success screen there as well. #6381
  • 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
  • Keep a backup the remote refused to delete in the retention list. (Pro) #6338
  • Keep damaged staging site data intact while a staging site is deleted, so the repair notice still has something to repair. #5892
  • Keep delete-guard case-alias tests independent of request timeouts. #6125
  • Keep deselected tables when deleting a staging site. #6193
  • Keep the live site's license active after a Next-Gen push. (Pro) #6429
  • Keep the notification badge beside the WP STAGING menu label. #6400
  • Keep the separate administrator account after a Next-Gen update or reset of a staging site. (Pro) #6388
  • 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
  • Let the staging site creation screen be closed with Escape or a click beside it once its job has finished. #6381
  • Let the unit test suite run again; FinalizeMultipartDatabaseTaskTest stopped it loading on every PHP version. #6265
  • Match CPU Load Priority defaults and restore the inline layout. #6109
  • Prevent Free feedback assets from loading on the front end. #5580
  • Prevent TypeError when reading backup DTO fields before they are set. #5636
  • Prevent invalid WordPress Home or Site URLs from crashing WP Admin. #6221
  • Prevent the empty-object warning when plugin information requests fail. (Pro) #3043
  • Regenerate Elementor CSS so layouts survive pushing staging to live. (Pro) #6090
  • Regenerate the English translation template so it matches the strings in the free backup modal. #6306
  • Regenerate the translation template so static_checks passes again. #6322
  • Remote Sync pull gets stuck waiting after the source site has finished preparing the backup. (Pro) #5218
  • 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
  • Report a finished event when a Next-Gen staging job ends, and record a staging job stopped by its requirements check as a requirement failure instead of as a finished job. #6275
  • Report a stable error code with a failed job, so failure causes can be counted across languages. #6276
  • Report the static checks of the fast-tests run in the pull request description too. #6324
  • Restore tables with long names across multiple requests. #5828
  • Restore the staging site list automatically when its stored data is damaged, instead of clearing it and asking y

Frequently asked questions

Is Wp Staging Pro GPL licensed?
Yes, Wp Staging Pro is distributed under the GNU General Public License (GPL). You can legally use, modify, and redistribute it on unlimited websites.
What is the latest version of Wp Staging Pro?
The latest version of Wp Staging Pro on GPLCoffee is v6.18.0 (released Oct 21, 2026, 4.0 MB download size). Every new release is synced automatically, and subscribers can update directly from their WordPress dashboard with the one-click connector plugin.
How much does Wp Staging Pro cost on GPLCoffee?
Wp Staging Pro is available for $5.99 for a 1-year license or $15.99 for a lifetime license. Membership plans also include credit-based access so you can download Wp Staging Pro along with thousands of other plugins, themes, and PHP scripts for a single subscription.
Which WordPress and PHP versions does Wp Staging Pro support?
The current release of Wp Staging Pro requires WordPress 3.6+ or higher, tested up to WordPress 7.1, PHP 7.0 or higher. Per-release compatibility details are listed in the version history.
Is Wp Staging Pro safe to download?
Yes. The latest release of Wp Staging Pro (v6.18.0) was scanned with VirusTotal and came back clean. Scan results are visible on each version page, and releases flagged as malicious are blocked from the catalog.

Auto-updates included

Install it once, update automatically.

The GPLC Connector installs this plugin from your wp-admin and rolls out new versions to your connected sites. Included with every membership plan: 10 to 40 connected sites depending on the plan (Lite 10, Pro 20, Geek and Lifetime 40).