Studio by WordPress.com 1.17.0 shipped on 27 July 2026, one day before this piece went up. That is the release to look at if you are deciding between WordPress Studio vs Local for your team’s local development in mid-2026, because the two tools have stopped converging and started diverging. Studio is betting on WordPress.com and Pressable plus an agentic command line. Local is betting on Blueprints, one-click deploys and a wider set of platforms. The changelog tells you which bet fits your shop.
Where Studio 1.17 sits in the release cycle
WordPress.com’s Studio has moved quickly through 2026. The CLI arrived in 1.7.0. Debugging tools landed in March. Linux support, specifically Ubuntu, arrived on 11 June. Then agentic Studio Code commands, including /publish to push a local site to WordPress.com and /liberate to recreate a site from platforms like Wix, went into the mix. Version 1.17.0 on 27 July is the consolidation release: the pieces that shipped earlier in the year now sit in one installer, and Linux users are no longer reading release notes from the sidelines.
The shape of the tool matters more than any single feature. Studio is a WordPress.com product, and it syncs with WordPress.com paid plans and Pressable only. That is not a limitation someone forgot to lift; it is the product. If your sites do not live on Automattic’s infrastructure, Studio’s sync path is a dead end. The usual advice is to test sync against a real staging environment before you standardise the whole team on it, because the moment you need to push a site somewhere else, you are exporting a ZIP and moving it by hand.
Local in 2026: Blueprints, MagicSync and platform reach
Local by WP Engine is the incumbent and knows it. The feature set that carries it in 2026 is Blueprints, which let you template and clone starter sites instead of rebuilding the same plugin stack for every project, and MagicSync, which handles one-click deployments to WP Engine and Flywheel. Windows, Mac and Linux are supported, which matters when your team is not uniform.
WP Engine also published a local development guide on 15 July 2026, written by Michael Bertram, that reads like a positioning document as much as a tutorial. You can read it at wpengine.com/blog/local-development. The release history for Local lives at localwp.com/releases, and it is worth reading before you commit either way, because the pace of patch releases tells you how much of the product is still moving.
If your hosting is on WP Engine or Flywheel, MagicSync is the closest thing either tool has to an opinionated workflow. You do not configure a deployment pipeline; you click, and the site lands on staging. For agencies running the same stack across a dozen client sites, that is the whole argument. If you want to run Local on a different host, you are back to manual exports, and the Blueprints still save you the rebuild time.
Email testing is the quiet differentiator
Local ships Mailpit. Studio has no built-in email testing. That sentence matters more than it looks. Contact forms, password resets, WooCommerce order emails and membership notifications all need somewhere to land in development, and if the tool cannot catch them, you are either installing a mail catcher yourself or sending test mail into the internet and hoping nobody notices. For any project with transactional email, Local saves a setup step that Studio has not shipped. If Studio is otherwise a better fit, budget an afternoon for wiring up an external catcher and document it for the team.
Studio vs Local: the comparison
| Dimension | Studio 1.17.0 | Local |
|---|---|---|
| Sync targets | WordPress.com paid plans and Pressable only | WP Engine and Flywheel via MagicSync |
| Starter site templating | Not in the disclosed feature set | Blueprints |
| Email testing | None built in | Mailpit |
| Platforms | Linux (Ubuntu) added 11 June 2026 | Windows, Mac and Linux |
| Agentic commands | /publish, /liberate, CLI since 1.7.0 |
Not in the disclosed feature set |
Read the table by column, not by row. Studio is the tool for teams already inside Automattic’s stack who want the agentic commands and the WordPress.com sync. Local is the tool for teams on WP Engine or Flywheel, or for anyone who needs Blueprints and Mailpit badly enough to give up the command palette. There is a third case, and it is common: a shop running both because different clients sit on different hosts. That is not elegant, but it is honest, and it beats forcing a migration to make the tooling tidy.
For a longer walk through Studio’s CLI and Linux build, Ben Ryan’s guide at benryan.com.au is a useful second source. We conclude that the tools have settled into two lanes rather than one race. Pick the lane your infrastructure already sits in. If you are paying for a host with one-click local-to-staging deploys and want that pipeline in the tool, WP Engine’s plans are the ones MagicSync is built for, which is the reason Local keeps winning in agencies that already run WP Engine.
What shipping faster actually requires
Neither tool removes the parts of local development that cause real pain. Docker resource tuning, database drift, PHP version mismatches between local and production, and the discipline of testing a plugin update before it goes out are on you, not on the installer. Studio’s agentic commands shorten the push step. Local’s Blueprints shorten the spin-up step. Everything between those two points is still your process.
The release cycle to watch is Studio’s. It went from CLI to debugging tools to Linux to agentic commands in roughly seven months, and 1.17.0 is the release that proves the team can land all of it in a stable installer. Local’s cadence is the one to watch if you depend on it daily, because hosting companies reposition their developer tools whenever a business line moves. Read the changelogs, not the landing pages. That has been the rule since long before either of these tools shipped.
FAQ
Does Studio sync with any host besides WordPress.com and Pressable?
No. Studio’s sync path covers WordPress.com paid plans and Pressable only. If your sites live anywhere else, plan on manual exports or a different tool for the push step.
Can Local handle email testing out of the box?
Yes. Local ships Mailpit, so transactional mail from contact forms, password resets and commerce plugins is captured locally. Studio has no built-in email testing, so you would wire up an external catcher.
Which tool should a Linux-based agency run?
Both support Linux as of mid-2026; Studio added Ubuntu support on 11 June and Local has shipped Linux builds alongside Windows and Mac. The deciding factor is not the operating system but the sync target and whether you need Blueprints and Mailpit.
