Do I need page-builder plugins, or are blocks enough now?

Blocks are enough for 90% of B2B marketing sites. Specific exceptions below.

The case for blocks-only in 2026

Gutenberg + ACF + theme.json now covers: column layouts, conditional visibility, custom CSS per block, reusable patterns, query loops, content sync between blocks, locale-specific variants, and full design-token integration. Five years ago, page builders won on every one of these.

When you still need a page builder

• Marketing teams that ship 4+ landing pages per month with novel layouts. The page-builder workflow trades long-term technical debt for short-term velocity. Sometimes that’s the right trade.
• Sites with no dev team. If the editor can’t open a block.json file, the page builder is the only sustainable answer.
• Sites where the brand changes every quarter. Page builders let the editor reshape blocks without dev support; custom blocks lock the layout to dev cycles.

The path most teams should take

Custom theme on Gutenberg + ACF, with two or three “flex blocks” that the editor can compose freely. This is the best of both worlds for the 90% case. Classic vs FSE essay ↗ goes deeper on the tradeoffs.