Run production WordPress locally — from a WP STAGING backup, with one command
WP STAGING CLI creates Dockerized WordPress environments and can restore or extract .wpstg backups without needing a working WordPress installation.
Ideal for agencies, plugin authors, and disaster recovery workflows.
Included with Developer and Agency licenses of WP STAGING Pro.
$ wpstaging add https://client.local
$ wpstaging restore https://client.local --from=https://client.com/.../backup.wpstg
$ wpstaging extract backup.wpstg --include=wp-content/pluginsWhat WP STAGING CLI is built for
Fast local environments, reliable restore workflows, and backup tooling you can script.
Dockerized WordPress environments
Create clean WordPress installs with the PHP/WP versions you need — without writing Compose files. Learn more →
Local copy from .wpstg backup
Turn a production backup into a working local site for debugging, QA, and client work.
Extract only what you need
Pull out plugins, themes, uploads, or a database dump — without a full restore.
Inspect backups before you act
View header, metadata, and index details to confirm what’s inside a backup file.
Container control + shell access
Start/stop sites, check status, open a shell in PHP/DB containers — from the same CLI.
Repeatable across machines
Same commands on macOS/Windows/Linux. Ideal for teams and standardized workflows.
Common jobs made simple
From local builds to recovery workflows — the CLI keeps it fast and consistent.
Client debugging
Restore a production backup locally and reproduce issues safely.
QA and regression tests
Test changes against specific PHP/WP versions without setup overhead.
Disaster recovery
Extract or restore .wpstg backups even if the site is down.
Automation & scripting
Use the CLI in scripts for repeatable client workflows and provisioning.
Quick command samples
A few examples that show the range: environments + backups + debugging.
Create a fresh site
$ wpstaging add https://mysite.local --php=8.3 --wp=6.6Create a Dockerized WordPress site with specific PHP/WP versions.
Restore from a .wpstg backup path or URL
$ wpstaging restore https://mysite.local --from=/path/to/backup.wpstgTurn a WP STAGING backup into a working local site.
Extract only plugins
$ wpstaging extract /path/to/backup.wpstg --include=wp-content/pluginsPull specific files/folders without a full restore.
Inspect what’s inside a backup
$ wpstaging dump-header /path/to/backup.wpstg
$ wpstaging dump-metadata /path/to/backup.wpstgValidate contents and metadata before extracting or restoring.
Tech notes
Designed for real-world workflows: speed, reliability, and automation.
Under the hood
Uses Docker/Docker Desktop with sane defaults and consistent containers.
Backup tooling
Inspect, extract, and restore .wpstg backups — even when WordPress isn’t running.
Cross-platform
macOS, Windows, and Linux supported with the same command set.
"Restoring a client site locally from a backup used to take ages. Now it’s one command — and I can even extract just the plugin I need."
Sonia R. Web agency owner Freiburg
FAQ
Is WP STAGING CLI included with my license? ⌄
WP STAGING CLI is included with Developer and Agency licenses. The Developer plan is the cheapest option that unlocks the CLI.
Does it work without Docker? ⌄
Docker (or Docker Desktop) is required. The CLI removes the complexity by generating and managing the containers for you.
Can I restore or extract backups if the site is down? ⌄
Yes. You can inspect, extract, and restore .wpstg backups without relying on a running WordPress installation — useful for recovery and debugging.
Where do I find commands and examples? ⌄
The documentation and examples live in the GitHub release repo. You’ll find install steps, command help, and real-world workflows there.
Ready to work faster with real client sites?
Unlock WP STAGING CLI with the Developer plan and restore, extract, and manage local WordPress environments from your terminal.
Already on Developer/Agency? Go straight to docs & download.