iThemes Builder review (2026): what to do now the theme framework is retired

01What iThemes Builder actually was

iThemes Builder was a theme framework, not a single theme. The idea was that you'd install Builder as your foundation and then assemble individual pages from modular building blocks — a header module here, a content module there — arranging them into a layout without touching code.

That was a genuinely forward-looking idea. Long before the native block editor existed, Builder gave non-developers a structured, drag-style way to lay out a site. You worked in modules and child themes rather than editing raw template files, which made it approachable for people who'd never write PHP.

A framework, layered onto child themes

Builder leaned on the WordPress parent/child theme model. You ran the Builder framework underneath and layered styling and structure on top. It came with a library of layouts and a module system, and iThemes sold child themes and add-ons around it.

We don't quote prices here, and in Builder's case it doesn't matter much: the product is retired. Treat anything you read about its old licensing as historical, and read the next sections as a migration brief rather than a buying guide.

02How iThemes became SolidWP — and why Builder was retired

The story of Builder is really the story of where iThemes chose to put its energy. Over time the company moved decisively away from themes and toward plugins, and Builder was left behind in that shift.

iThemes built its later reputation on a plugin portfolio — backup, security, and site-management tools that became the products people associated with the brand. The theme framework that the company was once known for stopped being the center of gravity.

Eventually iThemes itself was rebranded as SolidWP, with the flagship plugins carried forward under new Solid-branded names. Builder did not make that journey as an actively developed product. It was retired, and it is no longer receiving the ongoing development and support that a framework underpinning a live site really needs.

To be clear and fair: this is a retirement, not a scandal. Companies refocus, and iThemes made a reasonable strategic bet on plugins. But the practical consequence for a Builder site owner is real — your foundation is now legacy software.

03The honest concerns in 2026

If you're still running Builder, here's the measured-but-honest part. The risks of staying on a retired framework aren't dramatic on day one — they accumulate quietly, which is exactly what makes them easy to ignore.

Security and compatibility drift

Retired software stops getting updates. As WordPress core and PHP move forward, an unmaintained framework gradually falls out of step — and any security issue that surfaces simply won't be patched. That's the single biggest reason not to sit on a Builder site indefinitely.

You may not see a problem for a while; plenty of legacy sites keep running. But you're carrying risk with no one on the other end to fix things, and that risk only grows as the gap between your stack and current WordPress widens.

Framework lock-in

Builder's layouts live in its own module-and-framework structure rather than standard WordPress markup. The arrangement of your pages depends on the Builder framework staying active underneath them.

Deactivate Builder or switch themes and a page that looked finished can fall back to raw, unstyled content. Your words and images survive in the database, but the layout that organized them belonged to the framework — and the framework is no longer maintained.

The clock is running

This is the part that makes Builder different from a merely 'older' theme. Because it's retired, time isn't neutral. Every month you stay is another month of compatibility drift and another month closer to a forced, rushed migration after something breaks — the worst time to do careful work.

04Migration urgency: why sooner beats later

With most theme reviews we'd say 'stay if you're happy.' Builder is the exception. When the framework underneath your site is retired and unsupported, planning your exit is the responsible default — not an overreaction.

The reason is simple: a planned migration on staging, done at your own pace, is calm work. A migration forced by a security incident or a fatal compatibility break is a fire drill. The difference between those two experiences is entirely about whether you moved before you had to.

• Move deliberately now if your Builder site matters to your business — do it on staging, on your schedule, before anything breaks.
• Move urgently if you're already seeing PHP warnings, plugin conflicts, or admin glitches — those are early signs the gap is widening.
• At minimum, back up religiously if you genuinely can't migrate yet — full, off-site, restorable backups buy you time, not safety.

None of this is meant to alarm you. Builder sites aren't going to vanish overnight. The point is only that the trend line runs one way, and the cheapest, least stressful moment to migrate is always earlier than the moment you're forced to.

05Modern alternatives to move to

The encouraging news is that what replaced framework-style themes is genuinely better for most people: lightweight themes built around the native block editor, all actively maintained and far lighter than an old framework.

• Astra — hugely popular, fast, and flexible, with a big library of starter templates. A comfortable landing spot if you want polish and a gentle on-ramp.
• Kadence — a strong all-rounder with excellent header/footer building and a generous free tier; great when you want design control without heavy bloat.
• GeneratePress — famously lean and stable, beloved by people who prioritize speed and clean code above flashy options.
• Blocksy — a modern, block-native theme with deep customizer controls and good WooCommerce support, well suited to a fresh rebuild.

All four are built for the block editor, which means your content lives in standard WordPress blocks rather than a proprietary framework format. That's the structural upgrade that matters: you're trading a retired, locked-in foundation for a maintained, portable one.

None is automatically 'the' answer — they're answers to slightly different priorities. But any of them is a safer long-term home than a framework no one is developing anymore.

06Lock-in and longevity: the ThemeBurn lens

Builder is almost a textbook case for the question we care about most: not how good a theme is on day one, but how cleanly you can leave it on day one thousand. Builder's retirement is exactly the scenario that lock-in makes painful.

Because Builder layouts live in the framework's own structure, you can't simply swap themes and walk away clean. Turn the framework off and finished-looking pages collapse into unstyled content. The migration cost that always lurked behind a framework theme has now come due whether you like it or not.

Your content itself isn't lost — the underlying text and images remain in the database. But getting them into a clean, portable shape generally means rebuilding pages in your new theme rather than flipping a switch. On a large site, that's real, billable work.

Compare a block-theme site, where content already lives in standard WordPress blocks: moving between lightweight block themes is mostly a styling change, with content intact and portable. That gap — between 'restyle' and 'rebuild' — is the entire reason we flag lock-in so loudly, and Builder is what it looks like when the bill arrives.

The lasting lesson isn't 'iThemes did something wrong.' It's that a theme you can leave is worth more over a site's life than a theme that's slightly slicker today. Pick your replacement with the next exit already in mind.

07How to migrate off Builder cleanly

If you've decided to move — and on a retired framework, you should — set expectations honestly: framework layouts need rebuilding. This isn't a one-click theme switch, and treating it like one is how sites break.

• Start with a full backup and a staging copy. Never test a migration on your live site. Managed hosts that include free staging make this painless.
• Inventory your pages. List what actually earns its keep — the high-traffic, high-converting pages — so you rebuild those first and don't waste effort on dead weight.
• Rebuild layouts in the new theme's block editor. Because Builder modules aren't standard blocks, plan to recreate pages in Gutenberg rather than import them intact.
• Preserve the content itself. Your text and images are in the database — carry them across cleanly so you keep your words even as you rebuild the layout.
• Watch URLs and redirects. Keep slugs stable where you can, and redirect anything that has to change so you don't lose rankings or break inbound links.
• Re-check speed and PHP compatibility after the move. A modern block theme should be faster and current; verify with real testing rather than assuming.

The biggest mistake is treating this like a theme toggle. It's closer to a controlled rebuild of your important pages. Done deliberately on staging, it's very manageable — and infinitely better than doing it in a panic after the retired framework finally breaks.

08A note on hosting and staging

A migration off a retired framework lives or dies on having a safe place to do the work. You want to rebuild pages on a copy of your site, confirm everything holds together, and only then push it live — never experiment on the site real visitors are hitting.

That's where managed hosting earns its keep. A host like Cloudways offers managed cloud hosting for WordPress and WooCommerce with one-click staging built in, so you can clone your live Builder site, rebuild on the staging copy at your own pace, and only publish when you're satisfied it's right.

It's not the only way to stage a migration, and we'd rather you migrate carefully on any decent host than rush it on a great one. But free, frictionless staging genuinely lowers the risk of this kind of rebuild — which is the part of the advice that actually matters here.

09FAQ

Is iThemes Builder still supported in 2026?

No. iThemes refocused on plugins and rebranded as SolidWP, and the Builder theme framework was retired. It's no longer actively developed or supported, which means no new compatibility or security updates — the core reason to plan a migration rather than sit on it.

Is it dangerous to keep running a Builder site?

It's a growing liability rather than an instant emergency. An unmaintained framework drifts out of step with WordPress core and PHP, and any security issue won't be patched. Many legacy sites keep running for a while, but the risk only increases — so the safe move is to migrate before you're forced to.

What happens to my content if I switch off Builder?

Your words and images stay in the database, but the layouts live in Builder's framework format. Deactivate it and pages can fall back to unstyled content. Getting clean, portable content out usually means rebuilding pages in your new theme rather than importing them intact.

What should I migrate to?

For most people, a lightweight block theme — Astra, Kadence, GeneratePress, or Blocksy. All are actively maintained, far lighter than an old framework, and keep your content in standard WordPress blocks, so your next move (if there ever is one) is a restyle rather than another full rebuild.

This article is general editorial guidance, not professional, financial, or business advice. Product status, pricing, and features change — verify current details with the vendor (SolidWP for iThemes/Builder, and each theme maker) before you act, and choose based on your own needs.