W
Unsaved Playground Not saved to browser storage
Live WordPress running PHP 8.3 and WordPress latest
Booting WordPress Playground

Preparing PHP, SQLite, WordPress core, and the active blueprint.

Step 3 of 5: applying site options

Start or Resume

New sessions, blueprints, and local browser storage.

Start a new Playground

Core, Gutenberg, GitHub, blueprints, and imports.

Vanilla WordPress

Start a clean WordPress Playground with the current settings.

Featured blueprints

Curated starts for common demos.

Your Playgrounds

Saved locally in browser storage.

Blueprint Gallery

Showing all 43 blueprints

Files and Blueprint

Files, blueprint bundles, and export actions.

/wordpress
wp-admin
wp-content
wp-includes
index.php
wp-config.php
wp-cron.php
wp-load.php
blueprint.json
assets/style.css
plugins/welcome.php
A
Open WP AdminNavigate the live iframe to /wp-admin.
H
Open HomepageReturn the live iframe to the site front page.
PR
Export to GitHub PRExport a theme, plugin, or wp-content directory to a GitHub repository as a pull request.
ZIP
Download .zipDownload the current playground snapshot.

Data and Logs

SQLite-backed WordPress data and PHP runtime output.

Database management is an early access feature. WordPress Playground emulates MySQL using SQLite. The tools are a work in progress and are improving every week.
wp_posts
wp_options
wp_users
wp_terms
wp_comments
IDpost_titlepost_status
1Hello world!publish
2Sample Pagepublish
7Hello from WordPress Playground!publish
9Navigation Menudraft
[21-May-2026 10:18:21 UTC] PHP Warning: file_get_contents(/wordpress/wp-admin/css/view-transitions.min.css): Failed to open stream.
[21-May-2026 10:18:20 UTC] Blueprint step completed: setSiteOptions.
[21-May-2026 10:18:20 UTC] PHP Notice: Function wp_maybe_inline_styles was called incorrectly. Unable to read the path key.
[21-May-2026 10:17:58 UTC] PHP Fatal error sample hidden after refresh; open Logs to inspect runtime output.

Settings

Runtime, language, network, and multisite.

This is an Unsaved Playground. Your changes will be lost on page refresh.
Apply & Reset is destructive. It wipes the current WordPress database, uploads, plugin changes, and theme edits unless you save first.