Etch WP

Choosing a builder is deciding what leaving it will be like

Nobody thinks about that on the day they install one. You choose on what you can see: how fast you assemble a page, how good it looks, how many modules it brings. And every reasonable builder wins that comparison somehow.

The bill arrives three years later, when you want to switch. That is when you find out your content is not content: it is shortcodes and proprietary blocks stored in the database, and deactivating the plugin turns your pages into a soup of codes in square brackets. Migrating stops being a change of tool and becomes rebuilding the site.

That is the problem Etch sets out to solve. Its bet is building visually but returning the result to the native WordPress block editor, so that what you assemble stays WordPress and not a layer on top of it.

What it is

• A visual development environment for WordPress, positioned as an alternative to classic builders.
• Sync with the block editor: what you do in Etch comes back to the native editor.
• A focus on maintainability, with stated attention to scalability and the accessibility of the result.
• A WordPress plugin, not an external tool or a separate service.
• Active development, with versions shipping continuously.

Who it makes sense for and who it does not

It makes sense if you build sites for other people and you care about what you leave behind. A client handed a site tied to a builder is tied to that builder continuing to exist and continuing to be affordable, and that is a decision you made on their behalf.

It also makes sense if you have been burned. Anyone who has migrated a large site off a builder knows exactly what is being talked about here and needs no explanation.

It does not make sense if what you want is to assemble a page in an afternoon from ready-made templates. That ground belongs to the established builders, with thousands of designs waiting and an enormous community. Etch does not compete there.

What to know before committing a project

It is a young tool, and that cuts both ways. The good side is that it was designed from scratch with what ten years of builders have taught. The uncomfortable side is that it does not have behind it the ecosystem of add-ons, templates and tutorials the veterans do.

Its own public documentation is more vision than specification: it does not detail compatibility, technical requirements or concrete limits. That is not a fault in the product, but it is a fact to weigh.

The practical advice is the usual one with new tools: try it on your own project or a small one before the commission your quarter depends on.

Requirements and what it does not do

It needs WordPress. It is a plugin, not a standalone product.

It is not a theme: it does not hand you the design, it hands you the way to build it. And it is not a migrator: it does not convert into its format whatever you already built with another builder.

It also does not bring a template library comparable to the established builders'. If your way of working is starting from a finished design and adapting it, you will miss that here.

Alternatives in the catalogue

The big three are in the catalogue and each answers a different way of working. Elementor Pro has the most templates and add-ons. Bricks is the favourite of people coming from development who want control of the markup. And Divi is still the most complete if you stay inside its world.

If your problem was not the builder but the design, a well made block theme can save you installing one: Kadence and Blocksy work with the native editor.

Frequently asked questions

Is it just another builder?
It presents itself as an alternative: it builds visually but returns the result to the native block editor.

What happens if I deactivate it one day?
That is its whole point: what you built stays WordPress content rather than proprietary shortcodes.

Does it migrate what I built with Elementor or Divi?
No. It does not convert existing projects from other builders.

Does it bring ready-made templates?
Not at the level of the veteran builders. If you work from finished designs, you will notice.

Is it finished?
It is in active development, with versions shipping often. Better to try it on a small project first.

Does it replace my theme?
No. It is the way you build, not the design you start from.