WordPress Playground Explained: What It Is and How to Use It

Key Takeaways

• WordPress Playground is a serverless, browser-based sandbox that lets you run a full WordPress site for testing and learning without any hosting.
• The tool is a disposable testing environment for experimenting with themes, plugins, and custom code, but it is not a replacement for a live website.
• While Playground is great for quick tests, a live staging environment is essential for testing performance and preparing for production.

If you’ve ever tried setting up WordPress just to test something, you know the drill: find hosting, spin up a database, configure PHP, and then finally install WordPress. It’s a lot of steps for something that might only take five minutes to try out.

That’s exactly why WordPress Playground exists. It runs WordPress entirely in your browser, no server or installation needed. With a single click, you can launch a fresh WordPress site, experiment with plugins, or tweak a theme without touching your local setup.

In this post, we’ll talk about what WordPress Playground actually is, how it works and why it is a helpful tool for developers, site owners, and anyone learning WordPress.

I’ll also walk you through how to customize the WordPress instance with themes and plugins, saving your changes, and even embedding Playground into your own site.

What Is WordPress Playground?

WordPress Playground isn’t just another demo tool — it’s a full WordPress environment that runs directly in your browser. The idea was first introduced during the State of the Word 2022, and it quickly caught attention because it works without any servers, PHP setup, or MySQL databases behind the scenes.

Instead of connecting to traditional hosting, Playground uses technologies like WebAssembly and SQLite to mimic a real WordPress environment right in your tab. That means you get the familiar WordPress dashboard, the ability to install plugins and themes, and even test custom code — but none of it depends on your computer or a hosting account.

Think of it as a throwaway WordPress lab. It looks and feels like the real thing, but once you close your browser, the entire instance disappears unless you save it.

How WordPress Playground Works

WordPress usually runs on a full setup: a web server like Apache or Nginx, PHP installed on the machine, and a MySQL database in the background. That’s how most hosting environments are put together.

Playground skips all of that. Instead, it runs the pieces of WordPress directly in your browser, so you don’t need a server or a local database service running.

WebAssembly (runs PHP in your browser)

The main part that makes this possible is WebAssembly (Wasm). It lets PHP execute inside the browser itself. Without it, WordPress wouldn’t even start, since PHP normally depends on a server to run.

SQLite (lightweight database inside Playground)

For the database, Playground relies on SQLite instead of MySQL. SQLite is a single-file, lightweight database. It isn’t designed for huge production sites, but for testing or demos it’s more than enough. WordPress still interacts with it in the same way it does with MySQL.

Service Workers (managing requests offline)

Then there are Service Workers and Worker Threads. They keep background tasks moving and manage requests in the browser. You won’t really notice them working, but they’re the reason the dashboard feels responsive and plugins run without dragging everything down.

Why and When to Use WordPress Playground

Playground isn’t here to replace hosting. It’s more of a quick tool for the moments when you need a WordPress site right away and don’t feel like spinning up a full environment.

Testing WordPress Without Hosting

There are times you just want to check something in WordPress — maybe a setting, maybe a plugin — but don’t want to bother with servers, databases, or local installs. Playground opens in seconds and gives you a clean site to play with. No setup required.

Learning and Experimenting Safely

If you’re new to WordPress, or showing someone else how it works, Playground is basically a sandbox. You can change themes, add content, even break things on purpose. Nothing important is at risk, and once you close the tab, it’s gone.

Prototyping Themes and Plugins

Developers might use it as a scratchpad. You can drop in some CSS, test a new block, or quickly check a PHP snippet without firing up your local stack. It’s not the same as running a full dev environment, but for quick ideas, it’s usually enough.

Running Demos or Training Environments

Playground also works well for training sessions or product demos. Instead of walking people through a long setup, you just send them a link. Everyone gets their own WordPress site in the browser, ready to go.

How to Start a WordPress Playground Instance

To launch a Playground site, open wordpress.org/playground/ in your browser and click on Explore Playground. After a short load, you’ll see a fresh WordPress site running locally in your browser — no hosting or installation needed.

By default, Playground runs the latest stable version of WordPress with standard settings. If you want to adjust the environment, click the gear icon in the top-right corner.

From there, you can:

• Pick a WordPress version — useful if you want to test an older release or the upcoming “Nightly” build (the development version updated daily with the latest code changes).
• Choose a PHP version — to match the version your live site uses.
• Change the language of the admin dashboard.
• Enable options like network access (to install plugins/themes from the web) or multisite.

Once your site is ready, you can start using it like any normal WordPress site. For example, to create a basic page:

• Go to + New → Pages.

• Choose a pattern if you like.

• Add a title and some content.
• Hit Publish and view it instantly.

That’s all it takes to get Playground up and running.

Customizing Playground with Themes, Plugins, and PHP Versions

Once you’ve started Playground, you’re not limited to the default setup. Just like a regular WordPress site, you can change the look with themes, try out plugins, and even switch between different WordPress and PHP versions.

Installing and Switching Themes

Inside the dashboard, go to Appearance → Themes. From here you can:

• Activate one of the themes that’s already available.
• Click Add Theme button to browse the WordPress theme directory to install a new theme.

• Just like any regular WordPress site, you can also upload a theme file if you want to test something specific.

It works exactly the same way as it does on a live site, so if you’re familiar with WordPress, there’s nothing new to learn.

Adding and Testing Plugins

Plugins are managed the same way too. Open Plugins → Add New, and you’ll be able to:

• Search the plugin directory (if network access was enabled when you set up Playground).

• Upload a plugin zip file if you want to try out custom code.

This is useful if you want to check how a plugin behaves before adding it to your main site.

Switching Between WordPress and PHP Versions

One of the more useful features in Playground is the ability to switch both WordPress and PHP versions on the fly. This isn’t something you’d normally do in a live setup without spinning up a new environment, but here it takes just a couple of clicks.

In Playground, you can change versions through the settings panel (gear icon in the top-right corner).

Why does this matter?

Plugin and theme compatibility: Not every plugin or theme works perfectly with the latest version of WordPress or PHP. By toggling between versions, you can quickly see if something breaks before deploying it to a real site.

Different hosting environments: Web hosts don’t all run the same PHP version. Some may be on 8.1, others on 8.3. If you’re building or maintaining code, Playground gives you a way to preview how it behaves across those versions without needing multiple test servers.

Preparing for updates: WordPress core and PHP both release new versions regularly. Testing in Playground helps you understand whether your site (or your client’s) is ready for that upgrade, or if fixes are needed first.

Saving and Restoring WordPress Playground Sites

When you’re experimenting inside Playground, you’ll probably want a way to save your work so you can come back to it later — or even move it elsewhere. Playground gives you 4 main ways to handle this:

1. Saving in Your Browser

If you just want to pick up where you left off, you can save your Playground instance right in the browser. From the menu (the four-square icon in the top-left), choose Temporary Playground → Save → Save in this browser.

Your site will appear under Saved Playgrounds, and any changes you make will now persist, even if you close the tab.

This option is best for short-term projects or quick tests since the saved data lives in your browser.

2. Exporting as a .zip File

For a more portable backup, you can export your Playground site as a .zip. Go to the same menu and select Download as .zip from the hamburger menu in the top right corner. This gives you a single compressed file containing your Playground setup — themes, plugins, content, everything.

Why this matters: a .zip file is much easier to move between environments. You can import it back into Playground, share it with a teammate, or even use it with tools like Studio by WordPress.com for local development.

3. Importing a .zip File Back

If you already have a .zip export, restoring it is straightforward. From the Playground menu, choose Import from .zip, then upload your file. As long as it’s a valid export, Playground will rebuild your site exactly as you saved it.

4. Importing and Exporting with GitHub

In addition to working with .zip files, Playground also connects directly with GitHub. This allows you to export your changes straight into a repository or pull existing code into Playground for testing. As WordPress Github integration is easily possible, it is only logical that Playground also connects with it.

From the Playground menu, you’ll find options to Export to GitHub, which creates a pull request in your repo with the updated files, or Import from GitHub by entering a repository or pull request URL.

For teams or developers already using GitHub for version control, this makes Playground a handy way to test, edit, and sync changes without leaving the browser.

Using Blueprints and the Query API in Playground

Exporting and importing Playground sites works fine if you just need to back up a setup or move it around. But if you’re looking for a quicker, more repeatable way to spin up specific environments, Playground also supports Blueprints and the Query API.

Both options take the idea of saving a Playground further — instead of just freezing your site in a .zip, they let you describe or request what you want and have Playground build it for you automatically.

What Are Blueprints?

In Playground, a blueprint is a small JSON file that acts like a set of instructions. Instead of manually choosing your WordPress version, PHP version, themes, or plugins every time, you can store those choices in a blueprint and reload them whenever you need.

To see this in action, open Playground and click the little square icon in the top-left. From there, head into the Blueprints tab.

You’ll see a gallery of ready-made setups shared by others—ranging from clean installs to preconfigured sites with certain plugins or block themes.

For example, here I’ll just preview the Stylish Press blueprint by adamziel.

Once the blueprint loads, I can make any changes I want in that Playground site—add plugins, change the theme, or update settings. If I want to keep those tweaks, I can save the setup as my own blueprint for later.

If you’ve already customized your own Playground site, you can also turn that into a blueprint.

Switch to the Temporary Playground tab, click the three-dot menu next to your site name, and choose View Blueprint.

This shows the JSON file for your current setup, which you can then save and reuse.

Query API Basics for Advanced Control

Another way to customize Playground is through the Query API. Instead of clicking around to install themes or plugins, you can simply add parameters to the Playground URL and have everything load automatically.

For example, if you want to test the “Classic Editor” plugin, just add this to the Playground link:

?plugin=classic-editor

This will launch a site with the Classic Editor already installed.

The same works for themes—just replace plugin with theme. You can also chain multiple items together with &. For example:

?plugin=classic-editor&plugin=hello-dolly&theme=twentytwentyfour

Open that link, and Playground spins up a site with WordPress running those two plugins and the specified theme—no setup steps needed.

This approach is especially handy when sharing demos. Instead of giving someone a list of things to install, you can send a single link, and they’ll land in a ready-to-go environment.

Embedding WordPress Playground in Your Website

Embedding works much like adding an iframe. WordPress Playground gives you a code snippet you can drop into your page, and it loads a fully functional WordPress instance inside that space.

For example, if you want to let readers try out the Classic Editor plugin, you could embed it like this:

<iframe src=”https://playground.wordpress.net/?plugin=classic-editor” width=”100%” height=”600″></iframe>

That iframe opens a Playground with the Classic Editor already installed, so visitors can experiment directly in your post.

I’ve embedded the iframe to a post on Cloudways blog as you can see in the screenshot below:

You’re not limited to plugins either. If you’ve saved a Blueprint JSON that configures WordPress with specific themes and settings, you can embed that too. Just point the iframe to your Blueprint file, for example:

<iframe src=”https://playground.wordpress.net/?blueprint-url=https://example.com/my-blueprint.json” width=”100%” height=”600″></iframe>

This way, you can share a full demo site—like a WooCommerce test store or a custom theme preview—without touching your live site. And because everything runs in the browser, there’s no risk to your server or database.

Limitations of WordPress Playground to Keep in Mind

Playground is useful for testing and quick demos, but there are a few limits worth knowing:

Performance constraints

Since it runs in the browser through WebAssembly, it’s not as fast as a proper server. Heavier themes or plugins can feel slow compared to real hosting.

No persistent database unless exported

Anything you build is temporary. Once you close the tab, your work is gone unless you’ve exported it as a .zip file or saved it as a blueprint.

Not a replacement for real hosting

Playground works well for learning, experimenting, or sharing setups, but it’s not built for running an actual website. You’ll still need proper hosting for that.

In short, it’s best to think of Playground as a disposable testing space rather than a long-term environment.

Take WordPress Beyond the Playground

WordPress Playground is great for testing, but when you’re ready to go live, choose reliable WordPress hosting for speed, security, and growth.

TRY NOW

Playground vs. Live Staging on Cloudways

Playground is perfect for experimenting in the browser, but it has limits. You can save and reload instances, but you’re still working in a simulated environment. That means you don’t get to see how your site performs on real hosting, and you can’t easily collaborate with teammates on the same setup.

This is where creating a staging site is a better approach. It lets you test performance, experiment with plugins or code changes, and invite team members to review updates before pushing anything live. Unlike Playground, staging gives you both realism and reliability—bridging the gap between quick browser-based tests and production-ready deployment.

Cloudways makes creating a staging site very convenient. In just a few clicks, you can clone your site to a staging environment, run all the tests you need, and then push the changes back to your live site once you’re confident everything works.

How to Create a WordPress Staging Site on Cloudways

Setting up a staging site on Cloudways only takes a few minutes. Here’s how:

Step 1 — Navigate to Your Application

• Log in to your Cloudways Platform.
• Head to Servers, then select the server where your application is deployed.

• Click the www icon and choose the application you want to clone.

Step 2 — Create a Staging Environment

• In the left sidebar, go to Staging Management.
• Click Launch Staging Application.

• A dialog box will appear. You can choose whether to create the staging site on the same server or another server in your account (just make sure the destination meets the app requirements).

• Tick Create as Staging, then hit Proceed Anyway.

That’s it—Cloudways will begin cloning your live application into a staging environment. Once it’s ready, it will appear in your applications list with a staging tag, completely isolated from your live site so you can test safely.

For a complete walkthrough of creating a WordPress staging site on Cloudways, check out our detailed staging guide.

Wrapping Up!

WordPress Playground is a handy way to spin up a WordPress site instantly, whether you’re trying out a plugin, testing an idea, or just learning the ropes. It’s lightweight, fast, and safe since everything runs in the browser.

That said, when you need to test performance, work with a team, or prepare changes for a real site, a proper staging environment is the better choice.

With Cloudways managed WordPress hosting, setting up staging only takes a few clicks and gives you a space that mirrors real hosting conditions—making the jump from experiments to production much smoother.