A few years ago, testing a plugin on a fresh WordPress installation meant spinning up a local environment, creating a database, running the installer and then installing the plugin. Even with good tools, it took a few minutes. Showing a client a quick demo meant setting up a staging site somewhere. Reproducing a bug report meant hoping you could match the reporter’s setup. WordPress Playground removes nearly all of that friction.
WordPress Playground changes all of that. It runs a full WordPress site entirely inside the browser, using a version of PHP compiled to WebAssembly and SQLite as the database. Open a link and, within seconds, you have a working WordPress site with the admin, the editor and plugins, all running on your own device. Nothing is installed and nothing touches a server. For developers, agencies and plugin authors, WordPress Playground has quickly become one of the most useful tools in the ecosystem.
How it works
Normally, WordPress needs a web server, PHP and a MySQL database. Playground replaces each of these with something that runs in the browser:
- PHP is compiled to WebAssembly, so it runs inside the browser’s JavaScript engine.
- The database is SQLite, through the same SQLite integration that lets WordPress run without MySQL.
- The web server is simulated by a service worker that intercepts requests and passes them to the in-browser PHP.
The result behaves very much like a normal WordPress site. You can log in, install plugins and themes, write posts and change settings. By default, everything lives in browser memory and disappears when you close the tab, though Playground can also save sites to browser storage or export them.
Getting started
Visit playground.wordpress.net and a fresh WordPress site loads immediately. From the Playground interface, you can:
- Choose the WordPress version, including betas and nightly builds
- Choose the PHP version
- Enable or disable network access, which plugins need to download from WordPress.org
- Install plugins and themes from WordPress.org or upload zip files
- Export the site as a zip, or import an existing one
- Save the site in the browser to return to it later
You can also configure a Playground with URL parameters. For example, adding plugin and theme parameters installs them automatically:
That single link gives anyone a site with Query Monitor and Twenty Twenty-Five, on PHP 8.3 and the latest WordPress.
Blueprints: repeatable setups
For anything beyond simple parameters, Playground uses Blueprints, JSON files describing how to set up a site. A Blueprint can install plugins and themes, set options, log in, create content, run PHP code and open a specific page.
You can load a Blueprint by URL, embed it in a link or paste it into the Playground’s Blueprint editor. Every person who opens it gets exactly the same site, which is the foundation for most of Playground’s practical uses.
Use 1: Testing plugins and themes quickly
Want to see whether a plugin conflicts with another? Check how a theme behaves with a particular block? Test a plugin on PHP 7.4 and 8.3? Playground lets you do each of these in under a minute, without risking a real site.
It’s particularly handy for:
- Evaluating plugins before installing them on a client site
- Checking compatibility with upcoming WordPress versions, using the beta or nightly options
- Testing PHP version changes before upgrading a server
- Trying settings or configurations you wouldn’t want to experiment with on production
Use 2: Plugin and theme demos
Plugin authors used to maintain demo sites, often with complex reset scripts so visitors couldn’t break them for others. With Playground, each visitor gets their own private copy that exists only in their browser. Nobody can break it for anyone else, and there’s no server to maintain.
WordPress.org supports this directly: plugin authors can add a Blueprint to their plugin’s assets, and a “Live Preview” button appears on the plugin’s directory page, launching a Playground with the plugin installed and configured. For many plugins, that’s become the easiest way for potential users to try before installing.
Agencies use the same idea for client presentations: a Blueprint that sets up a prototype with sample content, sent as a link the client can explore.
Use 3: Reproducible bug reports
“It doesn’t work on my site” is one of the hardest bug reports to act on. With Playground, a reporter can share a link or Blueprint that reproduces the exact setup: WordPress version, PHP version, plugins, settings and content. The developer opens it and sees the bug immediately.
Many WordPress core and plugin issue trackers now encourage Playground links in bug reports. If you maintain a plugin, adding a short note to your support documentation asking for a Blueprint can save hours of back-and-forth.
Use 4: Learning and teaching
Playground is ideal for workshops, training and documentation. Every participant gets an identical site instantly, regardless of their computer or technical skills. Tutorials can include a “Try it” link that opens a Playground set up for that lesson. WordPress’s own learning resources increasingly use this approach.
Use 5: Local development
Playground also has command-line and editor integrations. The Playground CLI can start a WordPress site from a local folder, mounting your plugin or theme so changes appear immediately. A Visual Studio Code extension does the same from inside the editor. For quick plugin development without setting up Docker or a local server stack, these are remarkably convenient.
Limitations to know
Playground is powerful, but it isn’t a full replacement for a real server:
- Performance is lower than native PHP, though fine for testing and demos.
- Network access is limited by browser rules. Plugins that make external requests may fail unless network access is enabled, and some requests are blocked by cross-origin restrictions.
- Database is SQLite, so plugins that use MySQL-specific queries may behave differently or fail.
- Persistence is temporary by default. Export anything you want to keep.
- Some PHP extensions aren’t available, and server-level features like cron jobs, email sending and custom server configuration don’t behave as on a real host.
- Large sites with big databases and media libraries aren’t practical to load.
For testing that depends on real infrastructure, such as performance, caching layers or server configuration, you still need a real staging environment.
A practical agency workflow
One agency workflow that works well uses Blueprints for every new project. At the start of a project, the developer creates a Blueprint that installs the agreed plugins, the starter theme and sample content. Designers and clients open the same link to explore early prototypes without anyone setting up a staging server. When a client reports an issue during review, the developer adds the relevant steps to the Blueprint and shares a link that reproduces it exactly.
For plugin businesses, Blueprints also serve as living documentation. A Blueprint that sets up a common configuration doubles as a tutorial: “Click here to see how the plugin works with WooCommerce subscriptions.” Support teams can send customers a Playground link showing the correct setup next to their own, which often resolves configuration questions faster than written instructions.
Keeping Blueprints maintained
Blueprints reference plugin versions, URLs and content files. Keep them in version control alongside your code, test them when you release new versions and use stable URLs for any files they download. A broken demo link on a plugin page creates a poor first impression, so check public Blueprints regularly. WordPress Playground makes demos effortless, but like any part of your product, they still need occasional care.
Combining Playground with real staging
Playground is best for fast, disposable environments. Use it for first impressions, quick checks and shareable reproductions, and move to a real staging server when you need production-like performance, caching, email or server configuration. Many teams find the two complement each other well.
Where Playground is heading
The project continues to develop quickly, with improvements to persistence, networking, PHP extensions and developer tooling. Features that were experimental a year ago are now routine. Check the Playground documentation occasionally, because new capabilities often remove limitations that previously sent people back to a full local environment.
Try it today
The quickest way to understand Playground is to open it and install a plugin you know well. Within a few minutes, you’ll see where it fits into your own workflow.
Frequently asked questions
Is WordPress Playground secure for client data?
Everything runs locally in the browser, and nothing is sent to a server unless a plugin makes external requests. Still, avoid loading sensitive production databases into tools you don’t control.
Can I use Playground for a production site?
No. It’s designed for testing, demos, learning and development, not for hosting live websites.
Does WooCommerce work in Playground?
Yes, for demonstrations and basic testing. Payment gateways and features requiring external services may be limited.
Can I share a Playground site I’ve built?
Yes. Export it as a zip, or better, recreate it with a Blueprint that others can open from a link.




