Limitations

WordPress Playground is under active development and has some limitations you should keep in mind when running it and developing with it.

You can track the status of these issues on the Playground Project board.

In the browser

Temporary by design

As Playground streams rather than serves WordPress, all database changes and uploads will be gone when you refresh the page. To avoid losing your work, either export your work before or enable storage in the browser/device via the "Save" button found in the top right on the side of the address bar.

1. Exporting Playground:

2. Save button:

Browser support

WordPress Playground is designed to work across all major desktop and mobile browsers. This includes:

• Desktop browsers: Chrome, Firefox, Safari, Edge, and other Chromium-based browsers
• Mobile browsers: Safari (iOS), Chrome (Android), and other mobile browser variants

Playground leverages modern web technologies and should function consistently across these browser environments. However, some advanced features may have varying levels of support depending on the specific browser and its version.

Note: Opera Mini support is not currently confirmed.

When developing with Playground

Iframe quirks

Playground renders WordPress in an iframe so clicking links with target="_top" will reload the page you’re working on. Also, JavaScript popups originating in the iframe may not always display.

Run WordPress PHP functions

Playground supports running PHP code in Blueprints using the runPHP step. To run WordPress-specific PHP functions, you’d need to first require wp-load.php:

{
	"step": "runPHP",
	"code": "<?php require_once('wordpress/wp-load.php'); OTHER_CODE ?>"
}

Using WP-CLI

You can execute wp-cli commands via the Blueprints wp-cli step. However, since Playground runs in the browser, it doesn't support the full array of available commands. While there is no definite list of supported commands, experimenting in the online demo will help you assess what's possible.