WordPress Studio Adds Two-Way Sync for Local Sites
A long-requested workflow lands: pull a hosted site down, work locally, and push changes back without a third-party migration plugin. We look at what it solves — and the edge cases it still leaves open.
by Sam Calder·August 14, 2026·1 Comments
WordPress Studio, the local development app aimed at people who do not want a Docker novel, now ships two-way sync with connected hosted sites. You can pull a copy, edit, and push selected changes back.
That sounds simple until you remember databases, uploads, and the chaos of object caches. The first release focuses on posts, templates, and a media subset, with a conflict screen when the remote copy moved while you were in a café.
Agencies that already live in Git will shrug. Builders who live in the Site Editor will not. This is for the latter group, and it removes a whole class of “can you just copy this to staging” tickets.
Caveats remain. Large WooCommerce catalogs, custom tables, and must-use plugins still need a grown-up workflow. But as a default path for brochure and editorial sites, two-way sync is the feature Studio needed to feel like a studio instead of a preview window.
1 thought on “WordPress Studio Adds Two-Way Sync for Local Sites”
Harper Lin · August 15, 2026
Finally. If media library sync holds up on a 40GB site, this replaces half of our staging dance.
