CoBlocks

Quick take: A capable free Gutenberg extension for straightforward sites that want more block variety without adopting a traditional page builder.

Best fit: Block Editor users who want a free collection of layout, gallery, form, content, and design blocks.

A free Gutenberg block collection for broader page layouts

CoBlocks expands the block editor with layout, gallery, content, form, and design blocks. Its appeal is breadth without moving the site into a traditional page builder, but every third-party block used in content becomes part of the site’s long-term editing dependency.

Features that matter for this plugin

• Layout and row controls: CoBlocks adds layout-oriented blocks that make multi-column and section design more flexible inside Gutenberg.
• Gallery blocks: Several gallery and media presentation options extend what editors can build without a separate gallery plugin.
• Content blocks: Blocks for features, counters, accordions, FAQs, profiles, and other common sections reduce the need for custom shortcodes.
• Form and utility blocks: The collection includes practical blocks for contact and utility use cases alongside visual design elements.
• Pattern-oriented page building: CoBlocks is designed around using Gutenberg as the primary page-building environment rather than embedding an independent front-end builder.

Who this fits best

Block Editor users who want a free collection of layout, gallery, form, content, and design blocks.

Broad free block collection. Lightweight Gutenberg-first approach. Useful page-building features without a separate visual builder. These strengths matter most when they align with an existing operational need.

Trade-offs to consider

A third-party block library becomes part of long-term content compatibility. Feature direction may not move as quickly as more actively commercial block suites. Test these constraints on staging before rolling the plugin across an important production site.

Free vs paid

The WordPress.org version is currently free. The main decision is whether this focused workflow belongs in your stack.

Choosing CoBlocks as a site standard

I would decide early whether CoBlocks is the project’s primary supplemental block library. Reusing the same block set across pages is better than installing different libraries for individual sections, because future editors need to understand and maintain whatever block markup remains in the content.

What to compare before choosing

Otter, Spectra, and Kadence Blocks are the closest Gutenberg-library comparisons. CoBlocks is especially attractive when a broad free collection is enough and the site does not need a heavier premium design system.

Practical decision notes

CoBlocks is a sensible choice for sites that want more Gutenberg components while keeping licensing simple. The decision should still account for content portability. Before building dozens of pages, create a test page with the blocks you expect to use, then temporarily deactivate the plugin on staging to understand the fallback behavior and editing impact. That tells you how tightly the content will depend on CoBlocks. For a long-lived editorial site, knowing the cost of removing a block library is just as important as knowing what it can build today.

If a block is central to key landing pages, include that dependency in the site documentation so future redesigns account for it before plugin removal.

PluginSuggest verdict

A capable free Gutenberg extension for straightforward sites that want more block variety without adopting a traditional page builder.

CoBlocks FAQs