Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is the WordPress Playground? A Plain Explanation

Short answer

WordPress Playground is a free tool that runs a full WordPress site inside your browser, with no host, install, or account. It uses PHP compiled to WebAssembly and SQLite instead of MySQL, so you can try themes, plugins, and settings in a private sandbox. It is a place to learn and test, not a place to host a live site.

Key takeaways

  • WordPress Playground runs a full WordPress site in your browser with no host, install, or account.
  • It uses PHP compiled to WebAssembly and SQLite instead of MySQL, as of November 2026.
  • Playground keeps up to five recent autosaves in your browser, and temporary sites vanish on refresh.
  • You can open a set WordPress or PHP version with a link, such as ?wp=6.5 or ?php=8.3.
  • A Playground site has no public address, so visitors cannot reach it like a live site.
  • Export a ZIP before you close a site you want to keep, because browser storage can be cleared.

What is WordPress Playground?

WordPress Playground is a free tool that runs a full WordPress site inside your browser, with no host, install, or account.

The official Playground docs describe it as an online tool to experiment and learn about WordPress. You open a page, WordPress starts, and you get the admin screens and the editor you would see on a normal site.

The official Playground website moved to wordpress.org/playground, while the docs live at developer.wordpress.org. The live demo runs at playground.wordpress.net.

Playground is free software under the GNU General Public License version 2 or any later version, according to the Playground docs. For the cost picture on a real site, see Is WordPress Free?.

A Playground site is a sandbox. A sandbox is a separate, safe space where you can try things without changing a live site. You can change a setting, break a layout, or install a plugin, then close the tab and start again.

How does WordPress Playground work in your browser?

Playground runs PHP in your browser with WebAssembly and stores content in SQLite instead of MySQL.

A normal WordPress site needs three parts: a web server, PHP, and a database. Playground moves all three into your browser tab. The Playground docs say it runs entirely client-side in WebAssembly, with no authentication and no backend required.

WebAssembly is a compact binary format that lets code written in other languages run in a browser. In Playground, the PHP interpreter is compiled to WebAssembly, so PHP code runs inside the tab. That is why you do not install PHP on your computer first.

For the database, Playground uses SQLite instead of a MySQL server. SQLite is a small database that lives in a file, not on a separate server. The quick start guide shows that database in wp-content/database/.

Your work stays on your device while you use it. The quick start guide says Playground runs locally in your browser and does not upload your site unless you choose an action such as Export to GitHub.

What parts replace a normal server?

  • PHP compiled to WebAssembly runs WordPress code in the tab.
  • SQLite stores posts, pages, settings, and users in a file.
  • Browser storage holds the site files and database between visits.
  • A Dock at the bottom of the page holds the tools for saving, files, and export.

What can you do inside a Playground site?

You can create pages, upload plugins, install themes, import content, and do most things you would do on a regular WordPress site.

That list comes from the quick start guide. It is the clearest short test of what Playground is: if the job fits inside wp-admin, it often fits inside Playground.

You can open /wp-admin/ for the dashboard and /wp-admin/plugins.php for the Plugins screen. The Dock address field jumps straight to a screen. For step-by-step use, see How to Use WordPress Playground to Test Plugins.

Playground suits learning and short checks. You can try a block pattern, change a theme setting, or see how a menu behaves. It also suits demos: a link can open WordPress with a plugin already installed, or the same clean site for every student.

A link or a Blueprint can open Playground with a set WordPress version, PHP version, plugin, theme, or starting setup.

The quick start guide calls this the Query API. You add a short value to the Playground web address, and Playground starts with that choice already made.

Examples from the guide are ?plugin=coblocks, ?theme=pendant, ?wp=6.5, and ?php=8.3. You can combine values, such as ?php=8.2&wp=6.2, and you can repeat a value to add more than one plugin or theme.

A Blueprint is a JSON file that sets up a Playground instance. The Playground docs describe Blueprints as JSON files for setting up your WordPress Playground instance. A Blueprint can install plugins, set options, and add content in one repeatable file.

The Dock also has a Blueprint gallery. It starts with Vanilla WordPress, which creates a clean WordPress install, according to the web instance guide. That is the best start when you want a blank site with no extra plugins or content.

Which versions can you pick?

You can pick major versions only. The quick start guide says you can specify major versions like wp=6.2 or php=8.1 and expect the most recent release in that line. You cannot request older minor versions, so neither wp=6.1.2 nor php=7.4.9 will work.

You can also use php=next to preview the next PHP version built from the php-src development branch. The guide links that value to a PHP 8.6 feature preview, as of November 2026. That preview is for early checks, not for a site you plan to keep.

WordPress versions change on a set cycle. Read What Is a WordPress Release Cycle? to see when new versions arrive.

How long does a Playground site last?

A Playground site lasts only as long as its storage mode allows, and a temporary site is lost when you close or refresh the tab.

The web instance guide lists three storage states. The table below shows what each one means in plain terms.

Storage stateWhere it livesWhat happens next
AutosavedIn this browserPlayground keeps up to 5 recent autosaves, and you can recover them from Your Playgrounds
SavedIn browser storage or a local directoryIt stays until you delete it or the browser clears its data
UnsavedNowhere lastingA temporary Playground, including ?storage=temp, is lost when the tab is closed or refreshed

When browser storage is available, new Playgrounds are autosaved. The quick start guide says you can find up to five recent autosaves in Your Playgrounds from the Dock.

If you need a site that is discarded on refresh, open Playground with ?storage=temp. That mode is useful for a quick check you do not want to keep.

Browser storage still belongs to the browser. The web instance guide warns that the browser may remove stored data when storage pressure or privacy settings require it. Export a ZIP when you need a file you can move, archive, or restore later.

How is Playground different from a staging site and a local install?

Playground is a browser sandbox, while a staging site is a private copy of your real site on a server and a local install runs on your own computer.

That difference decides which tool fits the job. Playground starts fast and needs nothing installed. A staging site matches your live host, plugins, and data more closely.

Place to try changesWhere it runsWho can visit itBest for
PlaygroundIn your browser tabOnly you, on that deviceQuick checks, learning, and demos
Staging siteOn a serverOnly people with accessChecks before a live change
Local installOn your computerOnly you, on that computerLonger work without a host

Playground is not a staging site. A staging site copies your real site, with its theme, plugins, and content. Playground starts clean, unless a Blueprint or link adds content to it.

Playground is also not a host. It has no public address, so a visitor cannot open it from another device. If you need a site other people can visit, you need hosting.

You can switch between recent and saved Playgrounds from the Dock. That helps when you keep two or three checks open at once. For a larger set of live sites, read How to Manage Many WordPress Sites From One Dashboard.

What are the limits of WordPress Playground?

Playground cannot act as a live site, and some jobs that need a permanent server or outside services will not work the same way there.

The Playground About page states the core limit in plain terms: Playground is not a permanent server with an internet address, which will limit connections to some third-party services such as automation, sharing, analysis, email, and backups in a persistent way. That comes from the About Playground page.

Some plugins expect a normal server. A plugin that needs a fixed address, a mail server, or a long-running job may fail or behave in a different way.

Storage is another limit. You have up to five recent autosaves, not a full backup history. Clearing browser data can remove a saved Playground, so a ZIP export is the safe copy.

Speed can vary too. A slow device or a heavy theme can feel slower than the same site on a host. Use Playground to check how a feature works, not to judge final speed.

Which jobs fit Playground, and which do not?

  • Try a theme or plugin before you install it on a live site.
  • Learn wp-admin and the block editor without risk.
  • Share a short demo with a link.
  • Check a setting on a set WordPress or PHP version.
  • Host a live site, take payments, or send real email.
  • Keep client work for weeks without an export.
  • Judge exact speed on a production host.

How do you check what version and setup a Playground uses?

Open Site Settings in the Dock to see the WordPress version, PHP version, language, networking, and multisite choices for that Playground.

The web instance guide lists those five settings in Site Settings. PHP version and networking can be applied to an existing stored Playground. WordPress version, language, and multisite change the WordPress install itself, so they need a fresh Playground.

The Dock also has Database and Files views. Database lets you inspect or download the SQLite database. Files lets you browse and edit files.

The Logs view shows PHP errors, warnings, and notices. If a plugin fails to load, check Logs before you change anything else. The address field also tells you where you are: enter /wp-admin/ for the dashboard or /wp-admin/plugins.php for the Plugins screen.

PHP support has changed over time. In January 2026, the Playground team on Make WordPress said Playground had dropped PHP 7.2 and 7.3, with PHP 7.4 as the new minimum and support through PHP 8.5. Check Site Settings before you rely on a version.

What mistakes should you avoid?

Do not treat a Playground site as a backup, a live site, or a place to store work you have not exported.

The most common mistake is closing a tab and expecting the site to still be there. A temporary Playground is lost on refresh, and even an autosaved one is only one of up to five recent autosaves. Store it permanently or export a ZIP if the work matters.

A second mistake is testing only in Playground and then changing a live site. Playground uses SQLite, not MySQL, and runs in a browser, not on your host. A plugin can work in Playground and still fail on a host.

Keep a staging check for live changes, and read How to Back Up WordPress before you change a live site.

A third mistake is sharing a Playground link as if it were a live site. The link opens a fresh copy in the other person's browser. It does not show them your edits, and it does not give them your saved site.

A fourth mistake is picking a version and forgetting it. A link with ?wp=6.5 or ?php=8.3 starts that version, even if a newer version is out. Check Site Settings when a result looks odd, and start a fresh Playground when you need a clean check.

Frequently asked questions

Is WordPress Playground free to use?

Yes. Playground is free software under the GNU General Public License version 2 or any later version, and you open it in a browser with no account. You do not pay for hosting to use it, because there is no host. A live site still needs hosting and a domain if other people are to visit it.

Do I need a WordPress.com account to use Playground?

No. The Playground docs say it runs entirely client-side in WebAssembly with no authentication and no backend required. You open the demo page and WordPress starts. You only need an account if you choose an action outside Playground, such as exporting work to GitHub.

Can other people visit my Playground site?

No. A Playground site runs in your browser on your device, and it has no public address. Other people can open a Playground link, but they get their own fresh copy, not your site. To share your exact work, export a ZIP or move the site to hosting.

Why did my Playground site disappear after I closed the tab?

A temporary Playground is lost when the tab is closed or refreshed. Autosaved sites are kept only as up to five recent autosaves in that browser, and clearing browser data can remove them. Store a Playground permanently in the Dock or export it as a ZIP before you close a site you want to keep.

Can Playground replace my staging site?

No, not for final checks. Playground is a fast browser sandbox with SQLite, while a staging site is a private copy of your real site on a server with your theme, plugins, and content. Use Playground to learn and to try ideas, then use staging to check a change that will go live.

Which WordPress and PHP versions can I try in Playground?

You can pick major versions with links such as ?wp=6.5 or ?php=8.3, and you can use ?php=next to preview the next PHP version. In January 2026 Playground supported PHP 7.4 through PHP 8.5, after dropping PHP 7.2 and 7.3. Check Site Settings in the Dock for the current list, because it can change.

Sources

  1. WordPress Playground Docs WordPress Developer Resources
  2. Start using WordPress Playground in 5 minutes WordPress Developer Resources
  3. WordPress Playground web instance WordPress Developer Resources
  4. About WordPress Playground WordPress Developer Resources
  5. January 2026 | WordPress Playground Make WordPress
  6. WordPress Playground WordPress.org

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test