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

Developer · Guide

How to Use WordPress Playground to Test Plugins

Short answer

Open playground.wordpress.net in your browser, go to Plugins, then Add New, and install the plugin you want to check. Activate it, open its settings page, and try its main feature on a test page or post. Nothing you do in Playground touches your live site, so you can judge the plugin before you install it for real.

Key takeaways

  • WordPress Playground runs a full WordPress site in your browser with no host, server, or account.
  • Add ?plugin= followed by the plugin slug to open Playground with that plugin already installed.
  • Playground logs you in as an administrator, so you can install plugins and change settings at once.
  • Playground keeps up to five recent autosaves, and a ZIP export saves files, database, plugins, and themes.
  • Playground is not a permanent server, so email and some third-party services may not work there.
  • Test a plugin on the WordPress and PHP versions your live site uses before you install it there.

What is WordPress Playground?

WordPress Playground is a free tool that runs a full WordPress site inside your browser.

The Playground handbook describes it as a platform that lets you run WordPress instantly on any device without a host. It runs locally in your browser, so it does not upload your site unless you choose an action such as Export to GitHub.

A Playground site is a virtual sandbox. You can install plugins, change settings, create pages, and break things without touching your live site. The handbook says the content you create is limited to the Playground on your device.

Playground is not hosting. It has no permanent public address, so visitors cannot reach it. The About page notes that this limit affects some third-party services, such as email, backups, and automation, in a lasting way.

What do you need before you start?

You need a modern browser, the plugin name or slug, and a short list of what to check.

No account, hosting plan, or local install is needed. The quick-start guide says you can open the official demo on playground.wordpress.net to start WordPress in your browser. You can create pages, upload plugins, install themes, and import content there.

Write down the plugin slug before you open Playground. The slug is the short name in the plugin page address on WordPress.org, such as coblocks or contact-form-7. You will need it for direct links and for Blueprints.

Also note the WordPress and PHP versions your live site uses. You can find them in your live dashboard under Tools, then Site Health, then Info. Match those versions in Playground when you can.

If you plan to compare plugins, list the features that matter most. A short checklist keeps the test focused and makes the result easy to judge. Keep the list to 3 to 5 items, such as the settings page, the front-end output, and one key feature.

How do you open Playground and install a plugin to test?

Open playground.wordpress.net, open Plugins, then Add New, and install the plugin like you would on a live site.

Follow these steps:

  1. Go to playground.wordpress.net and wait for WordPress to load.
  2. Open the Dock and choose New, then Vanilla WordPress from the Blueprint gallery for a plain install.
  3. In the WordPress dashboard, go to Plugins, then Add New.
  4. Search for the plugin by name, click Install Now, then click Activate.
  5. Open the plugin settings page from the dashboard menu or from the Plugins list.

The Playground for Everyone guide gives the same 4-step flow: open the site, go to Plugins, then Add New, search for and install any plugin, then test it. It also notes that Playground logs you in as an administrator, so you can edit any page at once.

Give the site a few seconds to load after each install. Large plugins take longer than small ones. If a plugin asks for a license key or an outside account, note that as a limit of the test, not as proof the plugin is broken.

Add ?plugin= and the plugin slug to the Playground address to open it with that plugin already installed.

The quick-start guide gives this example for the CoBlocks plugin: https://playground.wordpress.net/?plugin=coblocks. You can repeat the parameter to install more than one plugin, such as ?plugin=coblocks&plugin=friends&theme=pendant.

Use a direct link when you want to share an exact test setup. Send the link to a colleague and they open the same plugins in their own browser. Each person still gets a separate Playground, so their changes do not affect yours.

You can also preinstall a theme the same way with ?theme= and the theme slug. The guide gives https://playground.wordpress.net/?theme=pendant as an example. Mix plugin and theme parameters when the test needs both.

Link partWhat it doesExample
?plugin=Installs one plugin from WordPress.org?plugin=coblocks
&plugin=Adds a second plugin?plugin=coblocks&plugin=friends
?theme=Installs one theme from WordPress.org?theme=pendant
?wp=Loads a WordPress version?wp=6.5
?php=Loads a PHP version?php=8.3

Check the slug before you share the link. A wrong slug loads a plain Playground or fails to install the plugin. Copy the slug from the plugin page on WordPress.org, not from a search result title.

How do you test a plugin on a different WordPress or PHP version?

Open Site Settings in the Dock to choose the WordPress and PHP versions, or add ?wp= and ?php= to the Playground address.

The quick-start guide lists these examples: ?wp=6.5, ?php=8.3, ?php=8.2&wp=6.2, and ?php=next. Use php=next to preview the next PHP version built from the php-src development branch.

Only major versions work in these parameters. The guide states that you can specify major versions like wp=6.2 or php=8.1 and expect the most recent release in that line. It also states that wp=6.1.2 and php=7.4.9 will not work.

WordPress.org recommends PHP 8.3 or greater as of November 2026, with MariaDB 10.11 or MySQL 8.0 or greater. Test on the PHP version your host uses, not only on the newest one. A plugin that works on PHP 8.3 may still fail on the older version your live site runs.

If your live site runs an older WordPress version, test on that version first. Then repeat the key checks on the version you plan to update to. That order shows whether the plugin or the update caused a problem.

How do you test two plugins side by side?

Open each plugin in a separate browser tab with its own Playground, then run the same checklist in both tabs.

The Playground for Everyone guide suggests opening multiple browser tabs with different Playground setups to compare plugin A versus plugin B. It also suggests comparing how content looks in different themes the same way.

Use the same test content in both tabs. Create one test page with a heading, a paragraph, and an image, then use the plugin feature on that page in each tab. Same content makes the difference between the plugins clear.

Keep one change at a time. If you change two settings at once and something breaks, you will not know which change caused it. Change one setting, check the result, then move to the next item on your list.

Before you pick a winner, check the plugin pages on WordPress.org for signs of trouble. Our guide to finding abandoned WordPress plugins shows how to check the last update date and the tested-up-to version. A plugin that works in Playground but has no recent update still needs care.

How do you check that the plugin worked?

Check three places: the Plugins list, the plugin settings page, and the front end of a test page.

First, open Plugins, then Installed Plugins, and confirm the plugin shows as Active. If it shows an error or a missing file notice, stop and read the message before you change anything else.

Second, open the plugin settings page and save one setting. Then reload the page and confirm the setting stayed saved. A setting that resets after a reload points to a problem with the plugin or with the Playground session.

Third, view a test page on the front end while logged in and in a private browser window if you can. Check that the plugin output appears where you expect it, such as a form, a block, or a widget area.

Also check for PHP errors and broken layouts. Open the page, scroll through it, and look for blank areas, missing images, or text in the wrong place. If you see a fatal error, note the exact message and the step that caused it.

A plugin that passes these checks in Playground is ready for a staging test. Playground alone does not prove it will work with your theme and other plugins on your live site. Use a staging copy for that final check, as explained in our guide to choosing WordPress hosting.

How do you save or share your test setup?

Save the Playground in browser storage, export it as a ZIP, or share a Blueprint or direct link that rebuilds the same setup.

Playground autosaves new sites when browser storage is available. The quick-start guide says you can find up to five recent autosaves in Your Playgrounds from the Dock. Open the Autosaved or Unsaved status in the Dock to store it for good.

To keep a Playground beyond the autosave cycle, click the Autosaved status in the Dock, choose Store permanently, then choose Save in browser storage. A saved browser Playground appears in Your Playgrounds. Browser storage still belongs to your browser, so export a ZIP when you need a file you can move or archive.

To export, open Export from the Dock and use Download as .zip. The exported file holds the current files, database, plugins, themes, uploads, and edits. The SQLite database is included in wp-content/database/.

To restore a ZIP, open New Playground from the Dock, choose Import zip, and select the ZIP file. This restores the files and database from the ZIP into a new Playground.

A WXR file is different: it imports WordPress content into an existing site, while a ZIP restores files and the database into a new one.

For a repeatable setup, use a Blueprint. A Blueprint is a JSON file that lists the steps Playground should run, such as installing a plugin. The Blueprint tutorial shows a first Blueprint that sets a site title, installs a theme, installs the Hello Dolly plugin, and imports content.

What can Playground not test?

Playground cannot test email delivery, payment processing, or other services that need a permanent server and public address.

The About page states that Playground is not a permanent server with an internet address. That limit affects connections to third-party services such as automation, sharing, analysis, email, and backups.

A contact form may save entries in Playground but never send an email. A payment plugin may load its settings page but never reach its payment service. Treat those results as untested, not as passed.

Playground also cannot show how a plugin behaves with your live content, your theme, and your other plugins at once. A clean Playground has no real posts, no real users, and no live traffic. Import a WXR export of sample content if the plugin needs posts or pages to work.

Some plugins need server features that a browser cannot provide, such as cron jobs, shell access, or a specific PHP extension. If a plugin fails to install in Playground, check its WordPress.org page for server needs before you call it broken.

Our guide to what happens when a plugin is closed on WordPress.org also helps when a plugin page shows a closure notice instead of a download button.

What mistakes should you avoid?

Do not treat a Playground pass as proof the plugin is safe for your live site.

Test on a staging copy after Playground. A staging copy has your theme, your other plugins, and your content, so it can catch conflicts that a clean Playground cannot. Keep a backup before you install anything new on a live site, as shown in our guide to backing up WordPress.

Do not close the tab before you save your work. If you opened Playground with ?storage=temp, the site is discarded on refresh. The quick-start guide states that a site opened with ?storage=temp is discarded on refresh, while other new Playgrounds are autosaved when browser storage is available.

Do not test with real user data or real payment details. Playground runs in your browser, but a test with live customer data still creates risk. Use sample posts, sample images, and test payment modes only.

Do not install every plugin you like in one Playground. Install one, test it, then start a fresh Playground for the next one. A fresh start keeps the results clear and avoids plugin conflicts that hide the real cause.

Do not skip the version check. A plugin that works on the newest WordPress and PHP may fail on the versions your live site uses. Match those versions first, then test the newest versions as a second step.

Frequently asked questions

Is WordPress Playground free to use?

Yes. Playground runs in your browser at playground.wordpress.net with no account, hosting plan, or install. You open the site and get a working WordPress install to test plugins, themes, and settings. It is a temporary test space, not hosting, so you cannot use it as a public live site.

Do I need a WordPress.org account to test a plugin in Playground?

No. Playground logs you in as an administrator when it loads, so you can install plugins and change settings without an account. You only need an account if the plugin itself asks you to sign in to a vendor service, and that sign-in is separate from Playground.

Will a plugin I test in Playground affect my live site?

No. Every Playground runs on its own in your browser and nothing syncs to an outside server. Changes stay inside that Playground session. Your live site is only affected when you install or change the plugin on the live site itself.

Can I test a premium plugin that is not on WordPress.org?

Yes, in many cases. You can upload a plugin ZIP file in the dashboard under Plugins, then Add New, then Upload Plugin. The upload works like a normal WordPress install. Some premium plugins still fail if they need a license server, email, or other outside service.

How long does a Playground test site last?

New Playgrounds are autosaved when browser storage is available, and Playground keeps up to five recent autosaves. A site opened with ?storage=temp is discarded on refresh. To keep work longer, save it in browser storage or export it as a ZIP file.

Can I test a plugin with WooCommerce in Playground?

You can install WooCommerce with ?plugin=woocommerce and add a test product, but payment and email steps may not work because Playground has no permanent server. Use it to check settings, product pages, and checkout layout, then confirm payments on a staging site with a test payment mode.

Sources

  1. Start using WordPress Playground in 5 minutes WordPress Developer Resources
  2. About WordPress Playground WordPress Developer Resources
  3. WordPress Playground for Everyone WordPress Developer Resources
  4. WordPress Playground for Plugin Developers WordPress Developer Resources
  5. Build your first Blueprint WordPress Developer Resources
  6. Previews and Blueprints WordPress Developer Resources
  7. Requirements WordPress.org
  8. Test Core Tickets with Playground Make WordPress Test

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