=== WP STAGING - Backups & Restore, Migration & Clone Plugin - Cloud Backups, Scheduled Backups ===

Contributors: WP-Staging, WPStagingBackup, ReneHermi, lucatume, lucasbustamante, alaasalama, fayyazfayzi
Donate link: https://wp-staging.com/backup-wordpress
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Tags: backup, wordpress backup, restore, move, transfer
Requires at least: 3.6
Tested up to: 7.1
Stable tag: 4.15.1
Requires PHP: 7.0

WordPress backup plugin: backups, restore & migration in minutes. Clone or duplicate your site, test updates on a staging copy. 100% unit-tested.

== Description ==

<h3>WordPress Backup, Restore, Staging, Cloning & Migration — All in One</h3>

WP STAGING is the all-in-one WordPress backup, restore, staging, cloning, and migration plugin, built for professional workflows with 100% unit-tested code, thousands of automated tests, and extensive end-to-end testing across supported PHP versions.

Create a full backup or an exact clone or copy of your website in minutes. Use it to duplicate your site, test plugin and theme updates safely, restore your site when needed, move or migrate WordPress to another server, transfer your site to a new host, or build a staging copy before making changes. WP STAGING also works as a WordPress duplicator, so you do not need a separate duplicator plugin to copy your website.

WP STAGING reliably backs up, clones, and migrates WooCommerce stores too, including orders, products, and customer data.

WP STAGING is developed in Germany and designed for agencies, developers, and businesses that need reliable WordPress backup, recovery, staging, restore, and migration workflows.

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also includes advanced workflows such as [Remote Sync](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another"), which lets you pull a WordPress site securely from one server to another using an API key, and [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a WP STAGING backup into a local Docker-based development site.

All data stays on your server unless you choose a transfer or remote storage workflow. WP STAGING is designed for speed, reliability, and low-resource environments, including shared hosting.

WP STAGING automatically performs search and replace for links and paths during cloning, backup, restore, and migration workflows.

**This staging and backup plugin can clone your website quickly and efficiently, even if it is running on a weak shared hosting server.**

[vimeo https://vimeo.com/999447985]

== Frequently Asked Questions ==

= Why should I use a staging site and backup workflow? =

Plugin updates, theme changes, and custom code should be tested before they reach your live site. A staging workflow lets you clone your production website, test changes safely, and keep a working backup ready in case something goes wrong. Safe updates and update testing on a staging copy protect your live site from broken releases.

Usually, it is best to run the staging site on an environment as close as possible to the production server. That is the best way to catch compatibility issues before they affect your live site.

WP STAGING combines backup, restore, staging, and migration in one workflow, so you can protect your live website, reduce downtime risk, and ship changes with more confidence.

= Is WP STAGING a backup plugin? =

Yes. WP STAGING started as a staging plugin and grew into a complete WordPress backup plugin, with restore, staging, cloning, and migration in one tool.

Even the free version lets you create backups and restore them when needed. [WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") adds more advanced backup workflows, cloud storage destinations, migration tools, and developer-focused features.

= How is WP STAGING different from other backup plugins? =

WP STAGING combines backup, restore, staging, cloning, and migration in one workflow. While many backup plugins focus mainly on archive-based backups or simple migration, WP STAGING also helps you create a working staging copy, test updates safely, and restore your site when needed.

Some backup plugins focus mainly on creating backup archives, while WP STAGING also creates working staging copies for safer testing and rollback workflows. This is especially useful when you want production-like validation before pushing changes live.

Some backup plugins may not fully support custom tables in all scenarios. WP STAGING is designed to work reliably with staging workflows and custom table prefixes used by its own cloned environments.

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also includes advanced workflows such as [Remote Sync](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another") and [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a backup into a local Docker-based development site. That makes WP STAGING especially attractive for developers, agencies, and site owners who want more than a basic backup plugin.

= How do I back up and restore a WordPress site? =

After installing WP STAGING, go to the backup section in the plugin and create a full-site backup. You can then restore that backup if a plugin update, theme change, deployment, or unexpected issue breaks your site.

WP STAGING is designed to make backup and restore simple, even on shared hosting and large WordPress installations.

= What is Remote Sync in WP STAGING Pro? =

Remote Sync is a Pro feature that lets you pull a WordPress site securely from one server to another using an API key. Instead of manually exporting databases and copying files, you connect the two sites and start the sync from inside WP STAGING.

This is especially useful for agencies, developers, and site owners who want a faster and more reliable workflow for moving content between WordPress installs.

Learn more:
[Remote Sync: Pull a WordPress Site from One Server to Another](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another")

= How can I turn a backup into a local Docker development site? =

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") includes access to [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a WP STAGING backup into a local Docker-based WordPress site with one command.

This is ideal for debugging, QA, development, and reproducing client issues locally. It helps you create repeatable local environments without building custom Docker setups for every project.

Learn more:
[WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Upgrade Now")

= How do I move, migrate, or transfer a WordPress site to a new host? =

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") includes migration and transfer workflows that help you move a WordPress website to another host, transfer your WordPress site to a new host, change the domain, or move to another server. You can move your website between hosts without manual database exports.

If you want a guided step-by-step walkthrough, see:
[How to Migrate Your WordPress Site to a New Host](https://wp-staging.com/docs/how-to-migrate-your-wordpress-site-to-a-new-host/ "How to Migrate Your WordPress Site to a New Host")

= How do I duplicate or clone a WordPress site? =

WP STAGING works as a WordPress duplicator: it can duplicate or clone a WordPress site in a few clicks and create an exact copy of your site for testing, development, or as a safety net. Duplication runs in the background, so you can duplicate even large WordPress sites on shared hosting. If you have used a plugin like Duplicator before, WP STAGING covers the same clone and copy workflows and adds backup, restore, and staging.

= Is WP STAGING a good Duplicator alternative? =

Yes. If you are looking for a Duplicator alternative, WP STAGING covers the same use cases: duplicate a WordPress site, create a full-site copy, and move or transfer it to another host. In addition to the duplicator workflow, you get one-click staging sites, scheduled backups, and restore in the same plugin.

= Why do I need a backup plugin at all? =

Consistent website backups are the foundation of a robust disaster recovery strategy. They protect your website against failed updates, user mistakes, malware cleanup, hosting issues, hardware failures, software malfunctions, and data loss.

Backups should include website files, databases, user data, and configuration data. A combination of full backups and incremental backups can improve storage efficiency while keeping restore points current.

If your website generates leads, sales, traffic, or customer trust, regular backups are not optional. A reliable backup, restore, and recovery workflow lets you roll back your WordPress site and can save hours of downtime and expensive recovery work.

= Can I activate permalinks on the staging site? =

Permalinks are disabled on the staging site after the first cloning process.

Read this guide to activate permalinks on your staging site:
[Activate Permalinks on the Staging Site](https://wp-staging.com/docs/activate-permalinks-staging-site/ "Activate Permalinks on the Staging Site")

= I cannot log in to the staging or backup site =

If you use a security plugin such as Wordfence, iThemes Security, All In One WP Security & Firewall, or a plugin that hides the default WordPress login URL, make sure you are running the latest version of WP STAGING.

If you still cannot log in, go to WP STAGING > Settings and disable WP STAGING extra authentication. Your admin dashboard will still remain protected.

= Can I just use my local WordPress development system for testing and backup? =

You can always test your website locally, but if your local hardware and software environment is not an exact clone of your production server, there is no guarantee that every aspect of your local copy will behave the same way.

Differences in PHP version, server stack, memory, CPU performance, and filesystem behavior can all lead to unexpected results on production. That is why staging on infrastructure close to production remains valuable.

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress "WP STAGING - Backup & Cloning") also gives you a more advanced local workflow through [WP STAGING CLI](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress"), which can turn a backup into a local Docker-based development site.

= Is WP STAGING available in multiple languages? =

Yes. WP STAGING is available in multiple languages, and several translations are already complete or nearly complete.

You can view translated plugin pages here:

[English](https://wordpress.org/plugins/wp-staging/ "WP STAGING on WordPress.org")
[French](https://fr.wordpress.org/plugins/wp-staging/ "WP STAGING en Français")
[German](https://de.wordpress.org/plugins/wp-staging/ "WP STAGING auf Deutsch")
[Spanish](https://es.wordpress.org/plugins/wp-staging/ "WP STAGING en Español")
[Croatian](https://hr.wordpress.org/plugins/wp-staging/ "WP STAGING na hrvatskom")
[Dutch](https://nl.wordpress.org/plugins/wp-staging/ "WP STAGING in het Nederlands")
[Finnish](https://fi.wordpress.org/plugins/wp-staging/ "WP STAGING suomeksi")
[Greek](https://el.wordpress.org/plugins/wp-staging/ "WP STAGING στα Ελληνικά")
[Hungarian](https://hu.wordpress.org/plugins/wp-staging/ "WP STAGING magyarul")
[Indonesian](https://id.wordpress.org/plugins/wp-staging/ "WP STAGING dalam Bahasa Indonesia")
[Italian](https://it.wordpress.org/plugins/wp-staging/ "WP STAGING in Italiano")
[Persian](https://fa.wordpress.org/plugins/wp-staging/ "WP STAGING به فارسی")
[Polish](https://pl.wordpress.org/plugins/wp-staging/ "WP STAGING po polsku")
[Portuguese (Brazil)](https://br.wordpress.org/plugins/wp-staging/ "WP STAGING em Português do Brasil")
[Russian](https://ru.wordpress.org/plugins/wp-staging/ "WP STAGING по-русски")
[Turkish](https://tr.wordpress.org/plugins/wp-staging/ "WP STAGING Türkçe")
[Vietnamese](https://vi.wordpress.org/plugins/wp-staging/ "WP STAGING bằng Tiếng Việt")

If you want to help improve translations, please get in touch with us through the support forum.

= Can I give feedback for WP STAGING? =

Yes. If something does not work as expected, please open a support request and describe the issue in as much detail as possible.

We continuously improve WP STAGING based on user feedback, real-world hosting environments, and developer use cases.

Open support:
[WP STAGING Support Forum](https://wordpress.org/support/plugin/wp-staging/ "WP STAGING Support Forum")

== WP STAGING FREE - BACKUP & STAGING FEATURES ==

* Clone the entire production site into a subdirectory like example.com/staging-site.
* High-performance backup and cloning, even for websites with very large databases.
* Create full or partial backups — full-site backup, database-only, or files-only backups.
* Scheduled backups with automatic daily backups.
* Easy to use: create a clone or backup in one click.
* Efficient background processing without slowing down your website.
* No Software as a Service and no external account required.
* All your data stays on your server. Your data belongs to you only.
* No server timeouts on huge websites or weak servers.
* Fast backup, clone, and restore workflows depending on site size and server resources.
* Use the clone as part of your backup and update strategy.
* Only administrators can access the cloned or backup website.
* SEO-friendly staging sites with login protection and no-index handling.
* The admin bar on the staging / backup website is orange colored and shows when you work on the staging site.
* Extensive logging features.
* Supports Apache, Nginx, Microsoft IIS, and LiteSpeed Server.
* Every release passes extensive automated tests to keep the plugin robust, reliable, and fast.
* Fast and professional support team.

== WP STAGING | PRO - BACKUP & STAGING FEATURES ==

The features below are available in [WP STAGING | PRO](https://wp-staging.com/backup-pro-features "WP STAGING | PRO Features").

* Remote Sync - Pull a WordPress site securely from one server to another.
* WP STAGING CLI - Turn a backup into a local Docker-based development site.
* Migrate and transfer WordPress to another host or domain.
* Push staging changes to production (staging to live), including plugins, themes, and media files, with one click.
* Clone a backup or staging site to a separate database.
* Choose a custom directory for a backup or cloned site.
* Select a custom subdomain destination like dev.example.com.
* Define user roles for accessing the clone or backup site. This can be clients or external developers.
* Multisite support for migration, backup, and cloning.
* Schedule recurring backups by time and interval.
* Download and upload backups to another server for migration and transfer.
* Backup retention settings.
* Custom backup names.
* Email notifications if a backup cannot be created.
* WordPress multisite backup and restore.
* Cloud backup, offsite backup, and remote backups to external storage providers.
* Backup to Google Drive.
* Backup to Amazon S3.
* Backup to (S)FTP.
* Backup to Dropbox.
* Custom backup folder destinations for cloud storage providers.
* Priority support.

== DOCUMENTATION ==

<strong>How to Backup and Restore WordPress</strong>
[Backup and Restore WordPress](https://wp-staging.com/docs/how-to-backup-and-restore-your-wordpress-website/ "Backup and Restore WordPress")

<strong>Backup & Transfer WordPress Site to Another Host</strong>
[How to Migrate Your WordPress Site to a New Host](https://wp-staging.com/docs/how-to-migrate-your-wordpress-site-to-a-new-host/ "How to Migrate Your WordPress Site to a New Host")

<strong>Remote Sync</strong>
[Pull a WordPress Site from One Server to Another](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/ "Remote Sync - Pull a WordPress Site from One Server to Another")

<strong>Local Docker Development with WP STAGING CLI</strong>
[WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade "WP STAGING CLI - Local Docker Development for WordPress")

<strong>All Backup Guides</strong>
[All Backup Guides](https://wp-staging.com/docs/category/backup-restore/ "All Backup Guides")

<strong>Working with Staging Sites</strong>
[Working with Staging Sites](https://wp-staging.com/docs/category/working-with-wp-staging/ "Working with Staging Sites")

<strong>FAQ for Backup & Cloning</strong>
[FAQ for Backup & Cloning](https://wp-staging.com/docs/category/frequently-asked-questions/ "Backup & Cloning FAQ")

<strong>Troubleshooting Backup & Cloning</strong>
[Troubleshooting Backup & Cloning](https://wp-staging.com/docs/category/troubleshooting/ "Troubleshooting Backup & Cloning")

== WP STAGING BACKUP & CLONING TECHNICAL REQUIREMENTS & INFORMATION ==

* Works on latest version of WordPress
* Minimum Supported WordPress Version 3.8
* Cloning and Backup work on all webhosts
* No extra libraries required
* Backup & cloning supports huge websites
* Custom backup format is much faster and smaller than any tar or zip compression
* Backup & cloning works in low memory & shared hosting environments

== SUPPORT ==

[WP STAGING Backup & Cloning](https://wp-staging.com/backup-wordpress "WP STAGING Backup & Cloning")

== Installation ==

= Installation via admin plugin search =

1. Go to Plugins > Add new. Select "Author" from the dropdown near search input.
2. Search for "WP STAGING". Searching for "WPStaging" in one word works as well.
3. Find "WP STAGING - WordPress Backup, Restore & Migration" and click the "Install Now" button.
4. Activate the plugin.
5. The plugin should be shown below settings menu.

= Admin Installer via zip =

1. Visit the Add New plugin screen and click the "Upload Plugin" button.
2. Click the "Browse..." button and select the zip file of our plugin.
3. Click "Install Now" button.
4. Once uploading is done, activate WP STAGING - WordPress Backup, Restore & Migration.
5. The plugin should be shown below the settings menu.

== Screenshots ==

1. Create new WordPress staging / backup site (Dark Mode)
2. Create new WordPress staging / backup site (Lite Mode)
3. Select name for staging / backup site (Lite Mode)
4. Create Full Site Backup (Dark Mode)
5. Create Full Site Backup (Lite Mode)
6. Cloning / backup processing (Dark Mode)
7. Backup Complete (Dark Mode)
8. Login to staging site
9. Staging demo site

== Changelog ==

= 4.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 live site's license active after a Next-Gen push. (Pro) #6429
* 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
* Fix: 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
* Fix: Report a stable error code with a failed job, so failure causes can be counted across languages. #6276
* Fix: Report the static checks of the fast-tests run in the pull request description too. #6324
* Fix: Restore tables with long names across multiple requests. #5828
* Fix: Restore the staging site list automatically when its stored data is damaged, instead of clearing it and asking you to reconnect every staging site, and keep a copy of the damaged data so the problem can still be reported afterwards. #5892
* Fix: Restore the update-protection notice translation that told you how many minutes ago the backup was made. #6213
* Fix: Run a Classic push when the saved staging engine is Next-Gen, instead of failing with an invalid staging database table prefix. (Pro) #6440
* Fix: Send the Warnings and General Backup Status emails again when a scheduled backup completes. #6247
* Fix: Show a staging site as unhealthy when its folder holds no WordPress files or its database tables are gone, instead of calling it running because the web server answered with a list of the folder's files. #6405
* Fix: Show an unfinished or broken staging site as unhealthy instead of running. #6349
* Fix: Show in the free backup modal that a backup plan is already scheduled and the time it runs. #6039
* Fix: Stop a Next-Gen update or reset from writing an empty database host, user or password into the wp-config.php of a staging site that uses a custom database connection. The production value is written instead. (Pro) #6387
* Fix: Stop a push reporting success when it could not identify the table holding the live site settings, licence and staging site list. (Pro) #6158
* Fix: Stop a subsite from running a backup plan copied to it from another site. #6364
* Fix: Stop telling you an update failed when WordPress simply did not report how it went. The update usually installed, so WP STAGING now says the result is unknown and offers to reload the page. #6278
* Fix: Stop the PR description from showing a stale E2E job result when two jobs update it at the same time. #6313
* Fix: Stop the Remote Sync pull cancellation test racing the pull it cancels. #6223
* Fix: Stop the automatic health check from marking a working staging site as unhealthy. A site is flagged only after it fails to answer twice in a row, and a staging site created before this check existed is only flagged by the Re-Check health button until it has been seen running once. #6405
* Fix: Stop the first run offering a staging site or a backup the user has already made somewhere else. #6381
* Fix: Translate the new Update Protection panel controls and messages, its setting description and four Remote Sync errors, which were shown in English on non-English sites. #6225
* Fix: Update Protection no longer opens a second progress panel when an update is started from the plugin details window. #6248
* Fix: Use the standard WordPress numbered notification badge in the Free and Pro admin menus. #6348
* UX: Draw the modal success icon cleanly in light mode when the theme switches from dark while the modal is open. #6082
* UX: Toggle table selection actions for push and update. #1518
* Ux: Close the first run's success card with a cross in its corner, and label the way out "Done" instead of "Continue to WP STAGING". #6415
* Ux: Give every tooltip the same border, corner radius and colours, so they no longer differ from page to page. #6105
* Ux: Move each general setting's description into a tooltip on an info icon beside its label. #6105
* Ux: Rename the staging creation success panel button from "Manage staging sites" to "Close". #6420
* Dev: Add the plan for sharding the E2E suites so a Pro round finishes in about 15 minutes. #6294
* Dev: Build the distributable packages once per E2E round and hand them to the suite jobs instead of building them in every job. #6303
* Dev: Cache the pro package built at the plugin's own version separately from the one built at the CI version, so Remote Sync no longer tests against whichever build won the cache race. #6303
* Dev: Correct the Free vs Pro comparison copy against the current plugin. #6244
* Dev: Correct the documented cost of make tests guardrails and of a single test class; both were quoted at about a second and take twelve to twenty seconds and about two. #6292
* Dev: Correct the fast-tests guidance in the pr-labels and create-pr skills. #6437
* Dev: Derive the SFTP SSH key fields from a single named condition and pin the SSH key toggle's stored-key rule with tests. #5927
* Dev: Fix the multisite subsite scheduled-backup badge test after database resets. #6319
* Dev: Give the fast tests unit jobs 30 minutes so a loaded runner no longer cancels a passing branch. #6308
* Dev: Give the review and fix-round skills a hard length budget, so a review opens with its verdict and carries only what the author has to change. #6371
* Dev: Include the release tag in the Pro version built by the Create Distribution Package workflow. #6150
* Dev: Keep a fix as small as the defect it repairs. #6290
* Dev: Keep multisite test sites intact when re-provisioning. #5870
* Dev: Keep mv and rm out of agent commands that do not need them, so a harmless chain no longer stops for a confirmation. #6242
* Dev: Keep nawawi out of the reviewer rotation unless the pull request is a security fix. #6200
* Dev: Keep translations out of pull requests: a PR regenerates the English template and the release merges and translates the eleven catalogues. #6228
* Dev: Label an approved PR for a second approval, then ready-to-merge. #6379
* Dev: Let a worktree photograph and record the Free version, instead of only Pro. #6389
* Dev: Let an agent open a pull request without stopping for a confirmation. #6366
* Dev: Load plugin styles, scripts and images from the loopback URL that make tests_web prints. #6226
* Dev: Make one rule decide what a change owes in pictures, so a fix to a user flow is not shipped without a recording of it. #6389
* Dev: Make the backup E2E tests wait on the success modal instead of a hidden newsfeed item with the same words. #6373
* Dev: Open a pull request description with what changed for a person, and move the technical account below it. #6316
* Dev: Pin the build stamp and the schedule clocks in marketing screenshots, so a second run of a spec no longer rewrites images whose screen did not change. #6240
* Dev: Point the screenshot normalizer's backup-overview clock pins at the scheduled-backups section, which replaced the markup they were written against. #6279
* Dev: Record how long every E2E spec file takes and add the e2e:shard-plan command that balances shards by measured time. #6300
* Dev: Regenerate only screenshots whose screens changed. #6227
* Dev: Regenerate the translation template while a pull request is being opened, so drift on the branch is fixed in seconds instead of a CI round. #6328
* Dev: Remove two pieces of work the E2E test round did without adding any coverage. #6395
* Dev: Report a release that was prepared and never tagged, and allow the missing tag to be created without merging its pull request. #6160
* Dev: Require a recorded reproduction before a bug fix can open a pull request. #6444
* Dev: Run PHPStan beside the fast-test unit jobs instead of ahead of them. #6454
* Dev: Run background jobs again on a make tests_web fixture, whose queue self-request could not reach the loopback URL from inside the container. #6274
* Dev: Run the Pro and Basic E2E suites on the self-hosted wpstg-ci-1 runner box instead of Blacksmith. #6282
* Dev: Run the release test phase version fan-out on Blacksmith and keep its gate on our own runners. #6340
* Dev: Run the single-site and multisite unit test suites as separate jobs so fast tests finish sooner. #6439
* Dev: Say what the back-out proof does not prove, so a test cannot pass it while asserting the wrong behaviour. #6396
* Dev: Scope the local check run in work-on-issue to the files a change actually touches, instead of running the whole fast-test stack every time. #6286
* Dev: Show a UI change in the pull request body — before and after screenshots, and a screencast of a flow. #6296
* Dev: Show the working WP Staging Pro admin on the make tests_web site of a fresh worktree, not only its install page. #6232
* Dev: Sign every review with the model that wrote it and its thinking level. #6206
* Dev: Stop a skills-only push from running the full fast-test suite. #6214
* Dev: Stop the Update Protection tests clicking a half-loaded plugin details window. #6335
* Dev: Stop the remote retention integration tests running a second time under multisite, which costs the label-triggered Pro round 5.7 minutes and covers no code a network install reaches differently. #6426

WP STAGING Backup & Cloning | Full changelog:
[https://wp-staging.com/wp-staging-changelog](https://wp-staging.com/wp-staging-changelog)

== Upgrade Notice ==

Compatible up to WordPress 7.0.
Many improvements for reliability and bug fixes. Please update to the latest version!
