Kadence, Spectra, GenerateBlocks or core block patterns? Canonical: https://patternpaste.com/blog/block-plugins-vs-core-blocks/ Page builders (https://patternpaste.com/blog/tag/page-builders/)Block themes (https://patternpaste.com/blog/tag/block-themes/)Performance (https://patternpaste.com/blog/tag/performance/) Argument # Block plugin suites or plain core blocks: what each one costs you When a block plugin suite such as Kadence Blocks, Spectra or GenerateBlocks is the right call, what happens to your pages when it is removed, and what plain core-block patterns cost instead. Jake 27 October 2026 5 min read A block plugin suite is the right choice when you need a component core does not have, or per-device design controls on every block, and you accept that the plugin stays installed for the life of the site. Plain core-block patterns are the right choice when the sections you need are ones core can already build, because then nothing on the page depends on a plugin. The difference shows up on the day the plugin is deactivated: core blocks render exactly as before, and a suite's blocks keep their text but lose their design. Kadence Blocks, Spectra and GenerateBlocks are all well-maintained, free on WordPress.org, and widely used. None of what follows is a defect in any of them. It is what a plugin block is. ## What a suite gives you that core does not# Each suite adds blocks under its own namespace (kadence/, uagb/ for Spectra, generateblocks/) and a design panel far larger than core's. The things that panel buys are real: - Settings per breakpoint. Different padding, columns or font size on desktop, tablet and phone, set in the sidebar. Core gives you fluid type presets and a Grid layout that wraps on its own, but no per-device toggle on most settings. - Components core does not ship. Kadence Blocks and Spectra both include a form block, for example, styled to match the rest of the suite. GenerateBlocks deliberately does not: it keeps to a small set of building blocks and leaves components to other plugins. - One vendor for theme and blocks. Kadence Blocks with the Kadence theme, Spectra with Astra, GenerateBlocks with GeneratePress. The pairs are designed together, and the documentation assumes both. - Design without theme.json. A designer who does not want to touch a theme's presets can style each block by hand. If a site needs those things, a suite is cheaper than building them, and it is the honest recommendation. ## What happens to a page when the plugin is removed# A block's settings are saved in its comment in post_content. For a suite's block, the design lives in those attributes, and the plugin turns them into CSS when the page is served. Remove the plugin and that step stops. What the visitor sees then depends on the kind of block: - Blocks with saved markup keep their HTML, because it is in the post. The text, links and images survive. The CSS the plugin generated does not, so columns stack, backgrounds disappear and spacing collapses to the theme's defaults. - Blocks rendered on the server, such as post grids, have nothing saved to fall back on and print nothing. In the editor, each one becomes a notice that your site does not include support for that block, with a choice to keep it as HTML or remove it. A page built entirely from one suite becomes a page of those notices. A core-block pattern has no such step. wp:group, wp:columns and wp:cover are registered by WordPress, and their colours and sizes come from your theme's presets. There is no plugin whose removal changes them. ## Lock-in is a cost you pay later, and only sometimes# Lock-in matters when the site outlives the decision. A client changes agency, a new developer prefers another stack, or the suite changes direction in a major version. Then every page built from it needs rebuilding, section by section, the same job as migrating off a page builder (https://patternpaste.com/blog/migrating-from-page-builders-to-block-patterns/), with the same audit of post_content first. If you build a site, hand it over and the client keeps the same stack for its whole life, the lock-in never comes due. Be honest with yourself about which kind of site it is. ## Performance: measure the page, not the brochure# All three suites describe themselves as loading only what a page uses, and their recent versions generate CSS for the blocks on the page rather than one stylesheet for everything. Core does the same for its own blocks: WordPress loads a block's stylesheet only when the block is on the page, as block theme performance (https://patternpaste.com/blog/block-theme-performance-and-unused-css/) explains. So the gap is smaller than either side's marketing suggests, and it depends on what you build. A page that uses a slider, a form and animated counters loads the scripts for them, from a suite or from anywhere else. Open the page in Chrome DevTools, run the Coverage panel, and compare unused CSS and JavaScript on two versions of the same page. That number is the only one worth arguing about. ## When to choose which# You need | A suite | Core blocks and patterns | Per-device settings on every block | Built in | Fluid presets and Grid only | A form block | In Kadence Blocks and Spectra | A separate form plugin | Pages that survive the plugin's removal | No | Yes | Sections that follow a theme change | Partly, if you used its global colours | Yes, through theme.json presets | Hand-off to a developer who uses another stack | A rebuild | Nothing to rebuild | A mixed approach is reasonable: core-block patterns for the sections core does well (heroes, features, FAQs, pricing, footers) and one plugin block for the one component it lacks. The page then depends on the plugin in one place, which you can name, rather than everywhere. ## What to do on Monday# On a site you are about to start, list the sections it needs and mark each one core can build. If every line is marked, start with core blocks and patterns, and add a plugin only for the component that forces it. On a site already built on a suite, open the Code editor on its busiest page and count the blocks outside the core namespace: that count is your exit cost, and it is better known now than on the day someone asks for it. Pattern Paste is a library of core-block patterns with no colour or font of their own: the free plugin (https://patternpaste.com/free-plugin/) puts 64 of them in the inserter, and the full set by section is in the pattern library (https://patternpaste.com/patterns/). Written by Jake 27 October 2026 ## Keep reading. All 16 articles (https://patternpaste.com/blog/) 30 August 2026 4 min read Performance ### Why block themes load zero unused CSS, and why page builders cannot (https://patternpaste.com/blog/block-theme-performance-and-unused-css/) 28 August 2026 5 min read Page builders ### Block themes and page builders: what each one actually costs (https://patternpaste.com/blog/block-themes-vs-page-builders/) 1 November 2026 5 min read Patterns ### How to make WordPress directory patterns match your theme (https://patternpaste.com/blog/wordpress-pattern-directory-colour-count/) 8 Themes · 542 patterns · 58 interactive ## Your next site, finished sooner. Start a whole site from a theme, or add one section to the site you have. Browse themes (https://patternpaste.com/themes/)Subscribe (https://patternpaste.com/account/)