WordPress Playground Explained: Full WordPress in Your Browser (Zero Install)

Setting up WordPress through the traditional method involves finding hosting, creating a database, and uploading files before you’re able to log in. However, WordPress Playground eliminates all these steps! Simply open a browser tab, wait a few moments, and a fully operational WordPress site is ready for you—complete with a server, database, and signup form.

The magic behind this process lies in PHP, the programming language powering WordPress, which is compiled into WebAssembly (a format that your browser can execute directly). Instead of the usual MySQL, SQLite is employed for database management. This entire setup operates on your device and is an official project from WordPress.org, available for anyone to use without charge.

This guide will explore what Playground is in detail, provide five practical scenarios in which everyday site owners can benefit from it, and will also candidly address some limitations you should be aware of before depending on it for significant tasks.

Let’s dive in!

What is WordPress Playground?

Visit playground.wordpress.net, and you’ll be greeted by a functioning WordPress site in mere seconds. Everything operates locally within your browser window: the PHP engine, the database, and the site files. No part of this system needs a server you pay for, and any experiment you perform here won’t affect an actual website.

At its core, the Playground project compiles PHP versions ranging from 7.0 to 8.4 into WebAssembly, uses SQLite, and keeps your site’s files stored in your browser’s memory. This isn’t just a simulation or a superficial walkthrough; it’s a genuine WordPress experience where themes, plugins, and settings work just as they would in a standard installation.

Playground is not merely a side project. It is an official initiative from WordPress.org, spearheaded by core developer Adam Zieliński and supported by a dedicated team sponsored by Automattic. Additionally, it welcomes contributions from the community on GitHub. The team periodically shares updates on the Make WordPress Playground blog. Keep in mind that this project is considered experimental and may experience unexpected changes, a point to note for the limitations discussed later.

PRO TIP: Consider every Playground session as temporary. If you create something worth saving, you can export the entire site as a ZIP file before exiting the tab.

Beyond a quick demo in your browser, the toolkit offers functionality for multi-site administration, file editing, database inspection, and importing existing sites. While much of this is more relevant for developers rather than casual users, it’s good to know there’s significant capability available.

1. Safely test a plugin or theme before applying it to your site

This is a feature that many site owners will appreciate. Playground allows you to add URL parameters that pre-install plugins and themes, enabling you to try new software in a safe environment rather than risking your live site.

For example, by entering https://playground.wordpress.net/?plugin=coblocks, you’ll launch a fresh WordPress instance with the CoBlocks plugin already installed and activated. You can change the slug to test different plugins, use multiple plugin parameters to see how they interact, or similarly use ?theme= to preview a specific theme. The Query API documentation provides the full range of options available.

Why is this important? Because asking, “will this plugin disrupt my layout?” is much easier to answer in a disposable tab than on your actual site that your visitors see. Always test before you install.

2. Explore wp-admin without consequences

One of the project’s core objectives is to facilitate “Learning WordPress Through Exploration,” and it certainly achieves that. For those new to WordPress, Playground grants access to the entire admin dashboard, menus, settings, and the block editor within an environment where mistakes carry no cost.

Feel free to explore the Settings, publish a test post, install a random theme, or even delete things on purpose just to observe the results. When you’re finished, simply close the tab, and all traces will disappear. It’s akin to a practice driving car for WordPress: same controls, no real-world consequences.

3. Quickly create a demo for clients or readers

Have you ever clicked the “Live Preview” button on a plugin page in the WordPress.org directory? That’s Playground in action. These buttons trigger a blueprint (a small JSON configuration that instructs Playground how to set up the site) to allow you to test the plugin before downloading.

You can use the same strategy yourself. Freelancers can provide clients with a link to a pre-configured demo rather than a PowerPoint presentation. Support forums, tutorials, and documentation can direct users to a ready-to-go example site instead of just descriptive text. A demo that launches in seconds is far more effective than a screenshot.

Moreover, the format itself continues to evolve. New features such as GitHub integration and an advanced blueprint format are under development, promising to make sharing demos increasingly user-friendly.

4. Reproduce a bug for support to observe it

“It works on my machine” is the classic phrase in tech support. Playground resolves this issue. With a blueprint capable of recreating a specific site configuration (like installed plugins, user login states, and executed code), you can provide the support team with the exact environment in which the issue occurs.

Blueprints are straightforward JSON files detailing each step. Available actions include installPlugin, login, and runPHP, plus a WP-CLI command for console tasks (note that not all WP-CLI commands are supported). A basic blueprint appears as follows:

{
  "steps": [
    { "step": "login" }
  ]
}

This single-step recipe launches a Playground site already logged into the WordPress admin. You can add additional steps for more complex setups, making it easier to provide support with precise details, reducing your need for lengthy explanations.

5. Develop locally without Docker or server stacks

Traditionally, local development with WordPress involves using tools such as Docker or XAMPP (read more about how to use XAMPP if you prefer the traditional setup). Playground provides a more streamlined alternative. The official @wp-playground/cli tool can run a local Playground server with a single command, npx @wp-playground/cli server --auto-mount, provided you have Node.js installed. Note that the previous wp-w tool has been officially deprecated as of June 2026, replaced by this CLI.

If you prefer a more visual approach, Studio is Automattic’s free desktop application powered by Playground, offering features such as preview sites and sync options with WordPress.com or Pressable hosting. Additionally, there’s an official Playground extension for Visual Studio Code if that’s your preferred editor.

Key Limitations to Be Aware Of

While Playground is undeniably valuable, it does have its boundaries. Here are the notable limitations:

• Partial networking capabilities. Outbound requests from the browser are routed through a limited CORS proxy, and there is currently no solution for extending this to all cross-origin requests. Features requiring external API calls may not function optimally.
• Reliability for email is questionable. Sending real emails necessitates outbound connections that the current networking setup does not consistently support, and the official documentation does not confirm operational email capabilities. Actions such as password resets and contact forms are features designed for live sites.
• Browser storage may be loss-prone. Websites stored in browser memory can be removed by private browsing modes or due to storage limitations. There are three storage options: Autosaved (keeping up to five recent saves), Saved (permanent browser or local directory), and Temporary (cleared upon closing the tab). However, exporting a ZIP file is the preferred method for backup portability.
• The project is experimental. The development team warns that it “may break or change without notice.” Therefore, avoid building workflows that you cannot easily replicate.
• Resource-intensive plugins require patience. Official loading times: a fresh WordPress site usually loads in about 5 to 10 seconds, sites with light plugins take 10 to 20 seconds, while WooCommerce-level plugins may take 30 to 60 seconds. The underlying engine itself is a 15 to 30MB download.
• Minor iframe issues exist. Links that target the top window can refresh the parent page, and JavaScript pop-ups originating from within Playground may not render correctly.

None of these issues are deal-breakers for the uses outlined above; they simply help delineate the border between a “fantastic sandbox” and a “true website.”

When You Still Require Real Hosting

It’s important to clarify what Playground isn’t. It isn’t a substitute for hosting since your site exists in your browser and doesn’t cater to actual visitors. Additionally, it does not serve as a staging site, as a staging site’s key function is to mimic your live server’s configuration, which your browser cannot replicate. Email, cron jobs, actual web traffic, and payment gateways still necessitate a real hosting environment.

Thus, the best practice involves using Playground for brief, experimental projects and educational purposes, employing a proper WordPress staging site for testing changes against a live configuration, and relying on legitimate hosting for anything intended for public viewing. Each tool has its specific function, and Playground fills a crucial niche.

Have you experimented with WordPress Playground yet? What did you use it for? Please share in the comments section below!

FREE GUIDE

4 Essential Steps to Speed Up Your WordPress Website

Follow these simple steps in our mini-series and significantly cut down your loading times by 50-80%.

Congratulations! You made it to the end of the article!