I have been following Unblock since its announcement and find myself repeatedly on the cusp of repurchasing (I bought it and then received a refund). I find working within core WP a hindrance, with a lot of clicking around rather than just building content or writing code. Today, I took another look at Unblock and once again struggled to work within core WP — Etch is far more direct. I took a look at the documentation and was intrigued by some of the expression and syntax options but couldn’t commit to the purchase (the fallback option is so needed). To that end, I decided to ask ChatGPT to review both sets of documentation and provide an unbiased review. Here is that review.
I evaluated only the two documentation sites as they appear today, July 29, 2026. I did not use previous work, reputation, pricing, community discussion, or hands-on experience.
Bottom line
Neither product is an unconditional winner.
- Unblock appears more focused, less architecturally restrictive, and more thoroughly documented at the individual-feature level. It is the stronger choice if you want to work directly in Gutenberg, retain theme flexibility, and prioritize dynamic content, queries, forms, and AI assistance.
- Etch presents the more ambitious professional development environment. It is the stronger choice if reusable components, full-site templates, direct HTML/CSS/JS authoring, client editing, and programmatic control are central to your workflow.
If forced to choose based only on what is demonstrably documented today:
- I would choose Unblock for a conventional content or marketing site.
- I would choose Etch for an agency-scale design system or component-driven site, provided I accepted its greater architectural commitment and unfinished areas.
For a conservative, production-critical project, the documentation alone would not lead me to adopt either without a proof of concept.
Direct comparison
| Area | Unblock | Etch |
|---|---|---|
| Core architecture | Extends Gutenberg directly | Separate visual environment synchronized to custom Gutenberg blocks |
| Theme dependency | Works with any block theme; blank theme recommended | Companion Etch theme required |
| HTML/CSS control | Strong | Stronger development-environment experience |
| Dynamic data and loops | Detailed and seemingly cohesive | Powerful, but parts of the data workflow are changing |
| Components | No comparable dedicated system documented | Major strength: props, slots, variations, reusable instances |
| Full-site templates | Relies more on the native WordPress environment | Dedicated Etch template workflow authored into FSE |
| Forms | Built-in managed forms | Appears to depend on third-party passthrough blocks |
| AI | Broader provider support; specialized agents | Experimental and currently OpenAI-only |
| Developer extension | Extensive PHP hooks | Much deeper typed JavaScript builder API, but experimental |
| Documented maturity | Explicit beta | Broader product, but numerous WIP/planned areas |
| Documentation style | Precise, restrained, operational | Extensive and transparent, but frequently promotional |
Architecture and lock-in
Unblock operates inside the native block editor and works alongside core blocks. Its companion theme is recommended but optional; the documentation explicitly says it works with any block theme. That is the lower-commitment architecture. Unblock theme documentation
Etch uses its own development interface and automatically authors the result into custom Gutenberg blocks. The documented bidirectional synchronization and client-facing Gutenberg experience are compelling. However, the Etch theme is mandatory, and its documentation warns that switching themes can cause lost layouts, broken functionality, incompatibility, or data corruption. That is the largest architectural risk disclosed by either product. Etch Auto Block Authoring, Etch theme requirements
Etch’s WordPress storage strategy reduces content lock-in, but the required theme and custom-block rendering model mean it should not be described as dependency-free.
Markup and styling
Both products claim semantic HTML, real CSS, two-way synchronization between visual controls and code, and selective loading of the styles used.
Unblock’s documentation is more concrete about output: per-page CSS, omission of unused styles, and a 50 KB threshold for inline versus external CSS. Unblock design tools
Etch offers a more IDE-like experience: rearrangeable panels and direct editing of HTML, CSS, and JavaScript. Its attached-selector model also promises portability and tree-shaking. Etch interface, Etch CSS panel
Neither documentation site provides independent benchmarks, Lighthouse results, representative output audits, or reproducible performance tests. Therefore, claims such as “crystal clean,” “optimized,” or “no bloat” should be treated as product claims — not established comparative evidence.
Unblock’s “one block, one element” slogan also has documented exceptions: Section produces a section plus a div, while Image produces figure plus img. That does not make the output poor, but the slogan is not completely literal. Unblock blocks
Dynamic sites
Both products document posts, terms, users, custom data, nested loops, main query inheritance, conditions, and dynamic attribute values.
Unblock’s system presently reads as more internally complete. It documents:
- Visual query, condition, and data builders
- Twig-like expressions
- Named query results and pagination
- Explicit loop metadata
- Empty-state handling
- Extensible providers, filters, and functions
Unblock loops, Unblock dynamic data
Etch offers similarly broad loop sources and good worked examples, but its documented empty state is currently a workaround. More importantly, “Data Sources to Replace Loop Manager” is an immediate development priority, indicating that this part of the architecture is actively changing. Etch loops, Etch current priorities
Components and templates
This is Etch’s clearest advantage.
Etch documents custom components with props, slots, variations, static and dynamic instances, plus a full template management system built into WordPress FSE. For agencies maintaining systematic sites, that could outweigh several other shortcomings. Etch components, Etch templates
Unblock’s documentation does not present an equivalent first-class component architecture. Native WordPress patterns may cover some reuse cases, but the inspected documentation does not substantiate parity with Etch here.
However, Etch’s native component library should not be mistaken for a finished large component suite: nearly every listed native component is marked WIP or Planned. Etch native components
Forms and AI
Unblock has the stronger documented form system: managed HTML forms, file uploads, spam protection, rate limiting, email delivery, explicit limits, error codes, and PHP integration hooks. Unblock forms
Etch says unsupported third-party blocks—including form blocks—can pass through to the front end, but Etch displays them as placeholders rather than fully mapped elements. Etch passthrough blocks
For AI, Unblock supports multiple providers through WordPress Connectors and separates building, designing, and writing into specialized agents. Etch Intelligence is explicitly experimental and currently supports only OpenAI. Unblock AI, Etch Intelligence
Extensibility
Etch wins on depth. Its typed window.etch API exposes blocks, styles, stylesheets, components, loops, navigation, custom fields, UI, history, skills, and AI presence. That is a serious platform-level capability. Its drawback is that the API remains at 0.x, is explicitly experimental, and is not recommended as a pinned production dependency. Etch Public API
Unblock offers a substantial yet more conventional PHP hook surface that covers data providers, expression extensions, queries, asset handling, security, forms, and AI configuration. It looks easier to consume safely, but it cannot manipulate the full editor environment as deeply as Etch’s API can. Unblock developer documentation
Maturity and documentation credibility
Unblock candidly calls itself beta, claims to be production-ready, and targets a stable release in September 2026. Its changelog shows frequent beta releases. Unblock introduction, Unblock changelog
Etch does not present itself as beta, but its documentation calls the product young and identifies:
- Hostinger save/upload failures
- Content Hub, custom post types, and custom fields as a proof of concept or “playground”
- Selector-entry quirks
- An evolving styling interface
- Planned facets and filters
- Potential builder-side server overload from unlimited parallel requests
Etch known issues, Etch performance issues, Etch facets
Etch deserves credit for publishing these limitations. Nevertheless, its documentation often mixes current functionality, future vision, and highly promotional assertions. Unblock’s documentation is generally more precise about limits, errors, sanitization, output behavior, and edge cases. Based solely on documentation quality, Unblock inspires more confidence in its exact capabilities, while Etch demonstrates a broader long-term product vision.
My neutral conclusion: Unblock is the more coherent product proposition today; Etch is the more capable product proposition if its component and visual development architecture match your needs.
For me, the ease of working with Etch and components, along with the long-term vision, outweighs the risks, and I will stick with Etch. I do hope some quality-of-life enhancements already present in Unblock come soon (e.g., easy ?? fallback dynamic data). Maybe it’s just the dark mode.
Leave a Reply