Start a clean WordPress Playground with selected runtime settings.
Step 01 / launch source
Start with the route contract visible
A plugin developer can compare each current start path by required input, runtime impact, and whether it touches the current site.
Gutenberg branch trunk previews plugin changes in a fresh runtime.
Choose browser storage or a local directory before leaving the temporary state.
Saving 3028 / 3751 files, then the title becomes Research Browser Playground.
Rename in place or delete with a warning that the stored browser copy is removed.
Settings reset and zip import keep the replace-current-site consequence visible.
Step 02 / save destination
Save the temporary runtime to a concrete place
Browser storage and local directory are separate commitments with different progress and resulting state.
Stores files and database in browser storage and makes the Playground available from the saved list.
research-browser-playgroundWrites the Playground filesystem to a chosen local folder. Browser list shows the directory-backed identity after permission is granted.
Step 03 / saved management
Keep temporary and saved sites visually separate
The manager exposes the current unsaved item, browser-backed saves, local-directory saves, rename, delete, and start-new shortcuts.
Step 04 / Site Manager
Inspect the WordPress runtime without losing the frame
Settings, file browser, Blueprint bundle, database, logs, and additional actions are grouped as developer workbench tabs.
Apply Settings & Reset Playground discards the current temporary site. Saved Playgrounds use Save & Reload with limited configuration options.
/* /wordpress/wp-config.php */
define( 'DB_NAME', 'database_name_here' );
define( 'DB_USER', 'username_here' );
define( 'DB_PASSWORD', 'password_here' );
define( 'DB_HOST', 'localhost' );
define( 'WP_DEBUG', true );
{
"$schema": "https://playground.wordpress.net/blueprint-schema.json",
"login": true,
"landingPage": "/hello-from-playground/",
"preferredVersions": {
"php": "8.3",
"wp": "latest"
},
"features": {}
}
WordPress Playground emulates MySQL using SQLite. Tools are improving and issues can be reported on GitHub.
- Database driver
- MySQL emulation backed by SQLite
- SQLite database path
/wordpress/wp-content/database/.ht.sqlite- Size
- 452 KB
No problems so far.
No problems so far.
No problems so far.
Step 05 / Blueprint catalog
Browse, filter, inspect, then run a Blueprint
The gallery remains a real catalog surface with category density, search, selected detail, and run or inspect behavior.
Step 06 / export and import
Move the project with replacement consequences visible
Transfers keep GitHub export, zip download, import zip, Blueprint URL, and GitHub import separate.
Push the current Playground files to GitHub after connecting an account.
Download the current Playground filesystem and database bundle.
Opening a local file chooser can replace the active files and database. Save first if the current site matters.
Connect a GitHub account to import public plugins, themes, or wp-content directories. Token is not stored after refresh.
Step 07 / runtime settings
Make reset and reload states explicit
The same settings are available from the quick panel and Site Manager, but unsaved and saved sites behave differently.
Unsaved Playground
Changing WordPress version, PHP, language, network access, or multisite requires a destructive reset.
Saved Playground
Stored Playgrounds have limited configuration options. Changes use Save & Reload rather than a fresh destructive reset.
Step 08 / active WordPress frame
Return to the running site
The runbook never hides the browser-like controls: refresh, path navigation, WP Admin, Homepage, saved status, and Site Manager remain reachable.
Hello from WordPress Playground!
This is Playground, a WordPress that runs client-side in your browser. It is perfect for training, demonstrating plugins and themes, and testing purposes.
Note that you are logged-in as admin!To start over, simply reload the page.