WordPress Playground: Run WordPress in Your Browser for Testing, Demos and Learning

WordPress Playground is an official WordPress.org project that runs a complete WordPress site inside your web browser. There is no hosting account, no installation and no database server to set up: you open a link, and a working WordPress admin appears within seconds. In WordPress.org's words, Playground "lets you run WordPress instantly on any device without a host."

That makes it a practical tool for business owners as well as developers. You can try a plugin before installing it on your real site, check whether a theme works with a newer PHP version, show a client a demo, or learn WordPress without risking anything.

The trade-off is that Playground is a sandbox, not hosting. By default, what you build lives in your browser and can disappear, it is not reachable by visitors, and some features behave differently from a real server.

This guide explains how Playground works, what it is good for, how Blueprints automate setups, how to save your work, and where its limits are.

How WordPress Playground works

A normal WordPress site needs a web server running PHP and a MySQL or MariaDB database. Playground replaces both with technology that runs in the browser:

• PHP in WebAssembly. PHP is compiled to WebAssembly, so your browser can run it. The documentation describes Playground as running "entirely client-side in WebAssembly," with no backend required.
• SQLite instead of MySQL. There is no WebAssembly version of MySQL for the browser, so Playground uses SQLite. The official SQLite Database Integration plugin translates WordPress's MySQL queries for SQLite.
• Isolated sandbox. Everything runs inside the browser tab and does not affect anything outside it.

The same technology also runs outside the browser: in Node.js through the Playground CLI, in VS Code, and on mobile. The main entry point for most people is the web version at playground.wordpress.net.

What Playground is good for

Testing plugins and themes safely

Before adding a plugin to your live site, open it in Playground and see what it does, what settings it adds and how it looks. If it breaks something, close the tab. This is a fast first filter. For a fuller pre-install checklist, see our WordPress plugin testing and QA guide. For anything that will touch your real data, follow up on a staging site.

Checking WordPress and PHP compatibility

Playground lets you pick a PHP version and a WordPress version. As of October 2026, the Query API accepts PHP 7.4, 8.0, 8.1, 8.2, 8.3, 8.4 and 8.5, and the last three major WordPress versions. That makes it handy for a quick check before a PHP upgrade. See our WordPress PHP versions guide.

Previewing plugins from the directory

Plugin developers can enable a "Live Preview" button on their WordPress.org plugin page. It opens the plugin in Playground, configured by a Blueprint the developer provides. The button only appears when the developer has enabled it.

Demos and client presentations

Agencies and product teams use Playground links to show a configured site, theme or plugin without setting up a server. A Blueprint can preload content and settings so the demo looks right every time.

Learning WordPress

New users and students can explore the admin, the block editor and the Site Editor without hosting costs or fear of breaking a live site. Learning content can link straight into a ready-made Playground.

Development and code review

Developers can preview GitHub pull requests in Playground, run PHPUnit tests with the Playground CLI, and spin up a local WordPress for a plugin folder with one command.

Getting started

1. Go to playground.wordpress.net. A fresh WordPress loads, logged in as an admin.
2. Use the settings panel to change the WordPress version, PHP version, language, networking or multisite mode.
3. Install plugins and themes from the directory as you would on a normal site.
4. Save your Playground if you want to come back to it (see below).

You can also start from a URL. The Query API reads parameters from the address, such as ?plugin= to install a plugin, ?theme= to install a theme, ?php= and ?wp= for versions, ?url= for the starting page, and ?multisite=yes for a network. For example, https://playground.wordpress.net/?theme=pendant opens Playground with that theme installed.

Blueprints: repeatable setups

Blueprints are JSON files that describe how a Playground should be set up. Instead of clicking through the same steps every time, you write them once. According to the Blueprints documentation, a Blueprint can set the PHP and WordPress versions, choose the landing page, and run a series of steps such as logging in, installing and activating plugins and themes, running PHP code and changing files and settings.

You load a Blueprint by passing its address with the blueprint-url parameter, or by pointing a plugin's Live Preview at it. Common uses:

• A product demo with your plugin installed and sample content.
• A bug report that recreates the exact environment where a problem happens.
• A training environment with the same starting point for every student.
• A test matrix: the same setup across several PHP or WordPress versions.

Treat Blueprints like code: keep them in version control and update them when plugins or WordPress change.

Saving your work

Playground's storage options, from the web instance documentation, as of October 2026:

Even "permanent" browser storage belongs to the browser. The documentation warns that storage pressure, private browsing, profile changes or clearing site data can remove it. Export anything you care about.

Limits to know

The official limitations page and the way Playground works point to several constraints:

• Not public hosting. A Playground runs on your device. Visitors cannot reach it, and it is not a way to host a real site.
• Not your real server. SQLite instead of MySQL, a browser instead of a server, and different PHP extensions mean results can differ from production. Plugins that rely on specific server features or direct MySQL queries may behave differently.
• Load times. The documentation cites around 5 to 10 seconds for a fresh WordPress, 30 to 60 seconds with large plugins such as WooCommerce, and slower performance on mobile devices. The WebAssembly files are 15 to 30MB.
• Networking. Networking can be switched on or off. Features that call outside services, such as payment gateways, email delivery or licensing checks, may not work as on a real server.
• Partial WP-CLI support. Not every WP-CLI command is available in the browser.
• Browser differences. Some advanced features vary by browser and version.
• Data loss risk. As covered above, unsaved and browser-stored work can disappear.
• Privacy. Avoid importing a production database with customer data into a browser sandbox. Use sample or anonymized data instead.

Playground is under active development, so some limits change over time. In January 2026, for example, Playground dropped PHP 7.2 and 7.3, in line with WordPress 7.0 raising its minimum to PHP 7.4.

Playground vs staging vs local development

Many teams use all three: Playground to try ideas, local tools to build, and staging to confirm before production. Desktop tools are also adopting Blueprints; WordPress Studio, a free local development app from WordPress.com, supports them.

Is Playground safe to use?

Playground runs in an isolated browser sandbox, so testing a plugin there cannot affect your live site. That makes it a safer first look than installing an unknown plugin on production. Still, a plugin that behaves well in Playground can behave differently on your server, and Playground does not check plugins for vulnerabilities. Continue to follow normal plugin hygiene: check update history, active installs and support activity, and keep everything updated. Our WordPress security guide covers how to vet plugins.

Conclusion

WordPress Playground puts a full WordPress site in your browser in seconds, which makes it one of the easiest ways to test plugins, compare versions, run demos and learn. Blueprints make those setups repeatable. Remember its boundaries: it is temporary unless you save it, it is not your production server, and it is not hosting. For more practical guides, visit our WordPress hub. If you need a plugin demo or a test workflow built around Playground, eSEOspace offers WordPress plugin development services.

Frequently asked questions