Staging goes stale. Live previews don't.
Staging hands you a copy that starts drifting right away. ThemeSync runs your theme on the real site, for people with the link only.
A staging clone, two weeks in
- Products from the day you cloned
- Content the client added since: missing
- Pushing back risks overwriting it
A ThemeSync preview, two weeks in
- Today's catalogue, live
- Everything the client added is there
- No copy to reconcile
Your theme sits on their site as an inactive theme, served only to visitors with the preview link. Everyone else sees the live site, untouched.
For client theme review, specifically.
| Local dev | Staging plugin | Host staging | ThemeSync | |
|---|---|---|---|---|
| Today's real products and orders | – | Snapshot | Snapshot | Yes |
| Every client plugin running | Partial | Yes | Yes | Yes |
| Client reviews without a login | – | Often gatedFree WP Staging keeps clones behind a login 1 | Varies | Yes |
| Nothing to reconcile afterwards | – | NoWoo orders need protecting on push-back 3 | NoPush can overwrite newer content 2 | Yes |
| Works on any hosting plan | Yes | Yes | NoOften gated to higher tiers 2 | Yes |
| Cross-browser and device screenshots | – | – | – | Yes |
| Clients comment on the page | – | – | – | Yes |
| Sign-off before launch | – | – | – | Yes |
| Testing plugin and PHP updates | Yes | Yes | Yes | NoTheme only, not a full clone |
Just stop reviewing themes on it.
Staging is the right tool for plugin updates and PHP bumps. It was never built for showing a client a design.
What each one nails, and where review hurts.
Local dev
LocalWP · Docker · Valet- Nails it
- Fast iteration, full debugging and zero risk to the client's site.
- Gets painful when
- Their catalogue has thousands of products and yours has twelve. And nobody can open a localhost link.
Keep it. We're not an editor. The handoff point is review.
Staging plugins
WP Staging · Duplicator- Nails it
- Safe testing for plugin updates, PHP upgrades and migrations, on any host 4.
- Gets painful when
- The clone ages. Pushing back needs care to protect live orders 3, and there's no review tooling.
Complementary. Staging for infrastructure, ThemeSync for the theme.
Host staging
Kinsta · WP Engine · cPanel- Nails it
- One click, close to production and nothing extra to install 5.
- Gets painful when
- Commonly reported limits bite: higher tiers only, one copy, and push-back overwriting newer content 2.
Client already has good host staging? Use it for environments.
Cloud sandboxes
InstaWP and similar- Nails it
- A throwaway WordPress site in seconds. Great for testing an idea.
- Gets painful when
- It's a fresh install, not their store. Getting the real catalogue in is a project of its own.
Great scratchpads. Not a client review environment.
Better you know now.
- You're testing plugin or PHP updates. That needs a full clone. Use staging.
- You can't install a plugin on their site. The preview depends on it.
- You're building on a child theme. Previews run as standalone themes for now.
- The work is mostly backend or plugins. We're built around themes and client review.
- You need to self-host. We're hosted only, for now.
- NexterWP: WordPress staging approaches and WP Staging's free version. nexterwp.com
- WP STAGING: common limits of host staging. wp-staging.com
- WP STAGING docs: protecting WooCommerce orders when pushing live. wp-staging.com
- WP STAGING on WordPress.org: plugin overview. wordpress.org
- Kinsta: guide to WooCommerce staging. kinsta.com
Third-party features and pricing change and vary by plan. Points above are summarised in our own words from the linked sources at time of writing. Spot something out of date? Tell us.
Real store. Real data. No copy to reconcile.
One free store. Nothing to uninstall.