Spectra Legacy

Quick take

For a Spectra Legacy WordPress site, the first question is whether existing pages already depend on its blocks. Spectra Legacy is not the plugin I would choose for a brand-new Gutenberg build in 2026. Its job is different now: keep existing sites built with the former Spectra plugin stable, compatible, and supported while new feature development moves to the separate Spectra Blocks plugin.

My Spectra Legacy review is therefore less about whether it has a good block library and more about migration risk. If an existing site depends on these blocks, there is no reason to force a rewrite simply because the product was renamed. If you are starting fresh, use a current block system that is still receiving new features.

Best fit: Spectra Legacy makes the most sense for existing WordPress sites already built with the former Spectra block library that need continued compatibility and maintenance. A different tool will usually make more sense for new Gutenberg builds that want an actively expanding block roadmap.

Why Spectra became Spectra Legacy

Brainstorm Force split the old Spectra product into two tracks in July 2026. The existing plugin was renamed Spectra Legacy so sites already using its blocks could continue without migration or content changes. A new separate Spectra Blocks plugin became the destination for ongoing feature development.

The rename did not convert existing blocks or remove their content. Pages, settings, and block markup remain in place. This is the key point for site owners who see “Legacy” and assume an immediate rebuild is required.

What existing sites still get

The existing block library remains functional

Spectra Legacy keeps the blocks that existing sites were built with, including layout, content, post, social, form, SEO, and site-tool blocks. The current product description specifically says those sites can continue working without a required migration.

Security and compatibility maintenance

The plugin still receives security fixes, WordPress/PHP compatibility updates, and critical bug fixes. Version 2.20.3 addressed a security issue, and 2.20.2 added WordPress 7.1 compatibility.

No new feature roadmap

This is the main limitation and it is intentional. New features ship in Spectra Blocks, not Spectra Legacy. If an existing site needs a new block capability, you should evaluate the new plugin rather than wait for the legacy product to expand.

Both plugins can run during transition

Brainstorm Force says Spectra Legacy and Spectra Blocks can run together while a site transitions. Existing pages can keep their legacy blocks while new pages use Spectra Blocks. The plugins load assets for the blocks used on a page, so this transition model is supported rather than a hack.

No forced migration deadline

There is no required migration date. An existing site can keep Spectra Legacy indefinitely as long as the maintained plugin remains compatible with the WordPress environment and continues meeting the site’s needs.

ZipAI remains for the former Spectra AI block

The former Spectra AI block was renamed ZipAI and continues to work in Spectra Legacy. I would still avoid treating AI functionality as a reason to start a new build on the legacy plugin, because new development is happening elsewhere.

Spectra Legacy vs Spectra Blocks

Spectra Legacy vs Spectra Blocks is primarily a product-direction decision. Spectra Legacy exists for compatibility with existing sites. Spectra Blocks exists for future development. That difference should drive the choice more than a feature checklist.

If a Spectra Legacy WordPress site is already built with the old block library, keeping it active is the low-risk option. If you are building new pages and want the current roadmap, use Spectra Blocks. During a gradual transition, both can coexist until the old blocks are no longer needed.

Where the trade-offs show up

The obvious trade-off is product direction. Spectra Legacy is maintained, but maintenance and innovation are different things. Existing sites get stability; new projects give up the benefit of the active Spectra Blocks roadmap if they deliberately start on the legacy plugin.

The word “Legacy” can also create unnecessary pressure to migrate. I would not rebuild a stable production site solely to remove the label. Migration makes sense when there is a real maintenance, feature, performance, or editorial reason to move.

During a mixed-plugin transition, teams also need clear editorial rules about which blocks belong to old pages and which system should be used for new content. Running both is supported, but inconsistent authoring habits can create a messy long-term block stack.

Spectra Legacy pricing

Pricing checked September 9, 2026. Spectra Legacy is free on WordPress.org. As a maintenance-focused Gutenberg blocks plugin, its value is preserving existing content rather than adding new features. It continues to receive maintenance, compatibility, and security updates without requiring a migration to Spectra Blocks.

For Spectra Legacy pricing, there is no paid core decision to make on this profile. The meaningful cost is operational: maintaining existing content versus investing time in a gradual transition when there is a real reason to adopt a current block system.

PluginSuggest verdict

My Spectra Legacy review conclusion is simple: keep it when an existing site needs it, but do not choose it as the foundation for a new build. Brainstorm Force has made that product boundary unusually clear.

Existing users should update to the latest maintained release and avoid unnecessary migrations. For a new Gutenberg blocks plugin, new projects should evaluate Spectra Blocks, Kadence Blocks, or another actively developed block system instead.

Spectra Legacy FAQs