Title: WordPress Playground web instance
Published: July 15, 2026
Last modified: July 16, 2026

---

# WordPress Playground web instance

## In this article

 * [Customize Playground](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#customize-playground)
    - [Site Settings](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#site-settings)
 * [Export a Playground](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#playground-options-menu)
    - [Blueprint pane](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#blueprint-pane)
    - [New Playground](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#new-playground)

[ Back to top](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#wp--skip-link--target)

[https://playground.wordpress.net/](https://playground.wordpress.net/) lets developers
run WordPress in a browser without a server. This environment makes testing plugins,
themes, and features quick and easy.

Some key features:

 * **Browser-based**: No local server setup required.
 * **Instant Setup**: Run WordPress with a single click.
 * **Testing Environment**: Ideal for testing plugins and themes.

The [Query Params API](https://developer.wordpress.org/playground/developers/apis/query-api/)
allows you to directly load specific configurations into a Playground instance. 
This includes setting a particular WordPress version, theme, or plugin. You can 
also define more complex setups using blueprints (see [examples here](https://developer.wordpress.org/playground/quick-start-guide#try-a-block-a-theme-or-a-plugin)).

The Playground website includes a Dock that opens tools for launching, configuring,
inspecting, and exporting your Playground.

![Playground Dock](https://i0.wp.com/wordpress.github.io/wordpress-playground/img/
dock/dock-overview.webp?ssl=1)

## 󠀁[Customize Playground](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#customize-playground)󠁿

The Dock includes these destinations:

 * **New**: Start from the Blueprint Gallery, a Blueprint URL, a GitHub repository,
   a pull request, or an imported `.zip` file.
 * **Playgrounds**: Switch between recent and saved Playgrounds.
 * **Blueprint**: View, edit, export, and run the current Blueprint.
 * **Site Settings**: Configure WordPress version, PHP version, language, networking,
   and multisite.
 * **Database**: Inspect the SQLite database and open database tools.
 * **Files**: Browse and edit files in the WordPress filesystem.
 * **Logs**: Read PHP, WordPress, and Playground runtime messages.
 * **Export**: Download a `.zip`, copy the original setup link, or export the current
   state to GitHub.

### 󠀁[Site Settings](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#site-settings)󠁿

![Site Settings in the Dock](https://i0.wp.com/wordpress.github.io/wordpress-playground/
img/dock/dock-site-settings.webp?ssl=1)

The **Site Settings** pane includes these [Query API options](https://developer.wordpress.org/playground/developers/apis/query-api#available-options):

 * `wp`: Defines the WordPress version.
 * `php`: Specifies the PHP version for the instance.
 * `language`: Sets the WordPress instance language.
 * `multisite`: Enables WordPress multisite support.
 * `networking`: Enables network access to the WordPress Plugin Directory and WordPress
   APIs.

## 󠀁[Export a Playground](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#playground-options-menu)󠁿

Open **Export** from the Dock to download or share the current Playground state:

 * **Download as .zip**: Saves files, database, and current edits to a `.zip` file
   that you can re-import later.
 * **Copy original setup link**: Copies a URL that rebuilds the Playground from 
   its original Blueprint. It does not include later edits.
 * **Export to GitHub**: Pushes the current state, including edits, to a GitHub 
   repository.

![Export options in the Dock](https://i0.wp.com/wordpress.github.io/wordpress-playground/
img/dock/dock-export-playground.webp?ssl=1)

### 󠀁[Blueprint pane](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#blueprint-pane)󠁿

![Blueprint pane in the Dock](https://i0.wp.com/wordpress.github.io/wordpress-playground/
img/dock/dock-current-blueprint.webp?ssl=1)

The **Blueprint** pane lets you edit, export, and run the Blueprint for the current
Playground.

### 󠀁[New Playground](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#new-playground)󠁿

![New Playground options in the Dock](https://i0.wp.com/wordpress.github.io/wordpress-
playground/img/dock/dock-new-playground.webp?ssl=1)

The **New** pane shows all the ways to launch WordPress Playground: choose a Blueprint
from the gallery, import `.zip` files, load from GitHub repositories, and preview
PRs from WordPress core and Gutenberg.

The Blueprint Gallery lists more than 40 blueprints.

The site at [https://playground.wordpress.net](https://playground.wordpress.net)
is there to support the community, but there are no guarantees it will continue 
to work if the traffic grows significantly.

If you need certain availability, you should [host your own WordPress Playground](https://developer.wordpress.org/playground/developers/architecture/host-your-own-playground).

First published

July 15, 2026

Last updated

July 16, 2026

Edit article

[ Improve it on GitHub: WordPress Playground web instance ](https://raw.githubusercontent.com/WordPress/wordpress-playground/trunk/packages/docs/site/docs/main/web-instance.md)

Changelog

[ See list of changes: WordPress Playground web instance ](https://developer.wordpress.org/playground/handbook/web-instance/?output_format=md#)

[  Previous: Start using WordPress Playground in 5 minutes](https://developer.wordpress.org/playground/handbook/quick-start-guide/)

[  Next: Troubleshooting WordPress Playground](https://developer.wordpress.org/playground/handbook/troubleshooting/)