Every plugin deserves a try-it link

One URL gives anyone a fresh WordPress site with your plugin active. Behind it: disposable sandboxes for testing every build before it ships.

instant demo launcher
WordPress.org plugin Click to search or edit
Launch demo

Search WordPress.org by name or slug. Your guest gets a fresh sandbox with the plugin active — no SandyWP account required. Themes work too.

Trusted by

PublishPressPaywallProjectNewsletter GlueInfinite UploadsMetaSlider

Reproduce the exact stack your user runs

Choose latest WordPress, pin a supported release, or test the current preview across PHP 8.1–8.3. That “works on my machine” bug has fewer places to hide.

Explore PHP switching

WordPress

Latest · 7.0.27.1 beta27.0.27.06.96.86.76.6

PHP

8.38.28.1

Extras

MultisiteSSHWP-CLI

The release grind, without the server babysitting

deploy

Ship from the terminal

One command uploads, installs, and activates your plugin ZIP on an existing sandbox.

$ sandywp deploy test-site my-plugin.zip

debug

WP_DEBUG, without the FTP dance

Toggle WordPress debug flags per site, read debug.log in the dashboard, or use SSH and WP-CLI when you need a shell.

Dashboard → Debug mode → Enable

reset

Clean slate, same URL

Reset a standard sandbox to a fresh WordPress install while keeping its public URL and admin login.

Dashboard → Reset to clean slate

Prefer the terminal for the whole environment? See every SandyWP CLI command.

Questions plugin developers ask

How fast is “seconds,” really?

Default-stack sandboxes use a warm pool and are typically ready in seconds. Pinned or preview WordPress versions, multisite, and plugin installs take a little longer while SandyWP provisions the requested stack.

Can testers use a launcher without an account?

Yes. Send them /plugins/<slug> and they can launch a fresh guest sandbox with that WordPress.org plugin active. SandyWP may ask for an abuse-protection check before creating the site.

What happens when I break the site?

That is what the sandbox is for. Reset a standard site to a clean install, or delete it and create another. Your production site stays out of the test loop.

Does SandyWP replace my local environment?

It complements it. Keep building locally, then deploy a plugin ZIP or push a local WordPress install to a real, shareable URL on the stack you choose.

Ship the fix, not the back-and-forth.

Free to start your first reproduction site is seconds away.