EtchWP vs Etch Studio: what's actually different?

The question sounds simple because the interface looks the same. On August 25, 2026, Kevin Geary said Etch Studio "does not look any different from Etch." That sentence is the anchor for everything else on etchwpstudio.com: one canvas, two backends, two checkouts.

The shared UI

Both products render the same Svelte application. Loops, logic, components, and the style manager behave the same in the canvas. Geary emphasized on stream that whether you build in WordPress or in Studio, the workflow should feel identical — loops and logic work the same, dynamic data works the same.

The pitch is continuity: you should not feel like you switched products when you switch project types. That makes the August 2026 split harder to explain as a new product launch. It reads as a backend swap.

The real difference is the writer

“In EtchWP, you had a loop manager and you configured loops in PHP because … that's how WordPress demands that it be done.”

PHP loop configuration was a WordPress constraint, not a product identity. In Studio, loops and data sources are rebuilt around a relational database the vendor operates. EtchWP still uses Gutenberg blocks and PHP-backed loops because that is how WordPress stores content today.

“This is kind of the development grounds for where we do things the way they should have been done and then we find a way to port that over to WordPress.”

Features that exist in Studio today — the data manager, data sources, schema view, visual JSON builder, global data outside loops — are described on stream as landing in Studio first and porting to WordPress later, the same pattern as the asset manager.

Three-column comparison

EtchWP genuinely delivers what their marketing promised for WordPress: blocks in post_content, two-way sync, client editing in native WordPress. Studio structurally cannot deliver that promise because the data is in their database, not in core WordPress.

What you get and lose either way

EtchWP: Your data stays in WordPress. You need a WordPress host, a license, and the PHP ecosystem. New architecture arrives later, if at all. Maintenance releases continue; the public changelog shows the last substantial feature release on July 8, 2026.

Etch Studio: You get the newer data architecture first, one-click Cloudflare deploy, and a ZIP download of compiled output files. You do not get a Git repository, WordPress-native storage, or coverage under an Etch lifetime deal. Editing requires an ongoing subscription.

Why this is a backend switch, not a new product

On August 25, 2026, Geary described a unified dashboard as a goal, not a shipped feature:

“Think about a unified dashboard where your studio projects and your WordPress projects show up all at once … that would be phenomenal.”

If it ships, LTD backers should not need a monthly fee to access that unified environment, and a self-hosted non-WordPress option should exist. The concession still points to one product with two persistence modes, not two separate products with separate entitlements.

The one-app alternative — same canvas, adapter for WordPress headless, SQLite, or Postgres, hosted or self-hosted — would have preserved lifetime customers instead of asking them to buy the canvas again. That is the path this site documents in its articles; see If you don't need WordPress, what is Etch Studio actually selling? for the don't-need-WordPress branch.