WordPress Studio’s desktop app for Linux is out, Ubuntu first, and it’s free and open source. My reaction to the announcement is a little sideways: the GUI is the least interesting part. Until the Studio CLI landed a few weeks ago, Linux users who asked about support were told Studio wasn’t officially available on Linux and to set up WP-CLI themselves. Now the whole toolchain runs natively, and that changes what I’d standardize on for local WordPress development.
How Studio runs WordPress
Studio runs WordPress on a bundled native PHP runtime with a SQLite database, per the README on GitHub. That’s why a new site takes seconds: no Apache config, no Docker image to pull. The desktop app adds what macOS and Windows users already had: custom local domains with HTTPS, one-click preview links to share with a client (those need a WordPress.com account), and two-way sync with WordPress.com or Pressable, where you choose whether to move the full site, just the database, or individual plugins and themes.
Three ways to do local WordPress development on Linux
Your own Docker or Lando setup gives you the most control. You pin PHP and MySQL to match the host, and the same compose file runs in CI. The cost is upkeep: each new project means more config and a fresh install.
The Studio CLI is the same engine, scriptable. It creates, starts and deletes sites from the terminal and wraps WP-CLI, so studio wp works without installing WP-CLI yourself. If you already have opinions about writing WP-CLI commands, they carry over. For a headless box or a team bootstrap script, this is the layer to use.
The desktop app is the fastest route from nothing to a logged-in admin. It detects your editor and hands you a preview link. If your day is five sites in five tabs, this is the one that saves you the clicking.
The database is where I’d slow down. SQLite handles most theme and plugin work because WordPress reaches it through a translation layer, but plugins that write raw MySQL-flavored SQL are where local and production drift: collation rules, full-text search, INSERT … ON DUPLICATE KEY UPDATE. For a marketing site I wouldn’t care. For a WooCommerce store, where production is MySQL and the order data is the product, I’d build in Studio and sign off on a MySQL staging copy. A Playground block theme workflow makes a similar trade-off and is more upfront about it.
On Ubuntu the desktop app ships as a .deb you install with apt; auto-updates and other distros are still on the roadmap. The CLI is either enabled in the app’s settings or installed standalone:
sudo apt install /full/path/to/studio.deb
studio --help
studio wp plugin list
This is a decision I end up making with clients: which environments move to Studio, which stay in Docker, and how staging fits in. If you want a hand auditing your setup or scripting the CLI for a team, get in touch.
What I’d pick for which site
For sites on WordPress.com or Pressable I’d take Studio without hesitating, because pull and push is the whole point. For plugin and theme work where the database is plumbing, Studio as well, with the desktop app for browsing and the CLI for anything scripted. Stores and projects with unusual MySQL usage keep Docker with pinned versions, then staging. CI stays on containers, because a runner already speaks Docker and has no use for preview links.
If you’re on Ubuntu, try it. Install the .deb, enable the CLI in settings, then run studio --help and, from inside a site folder, studio wp core version. Twenty minutes of that tells you whether it belongs in your workflow.