Short answer: no, Oxygen Builder isn't dead. It just shipped the biggest release in its history. But if you built client sites on Oxygen Classic, the real situation is more nuanced than a yes or no — and that nuance is exactly why so many developers are confused right now. Let's untangle it.

If you've typed "is Oxygen Builder dead" into Google recently, you've probably landed on a wall of two-year-old Reddit threads, a vendor page or two, and a lot of contradictory takes. Some of that information is genuinely out of date. So here's where things actually stand in 2026, and more importantly, what it means for the sites you've already built.

Where the "Oxygen is dead" rumor came from

The anxiety didn't come from nowhere. For a stretch of several years, Oxygen Classic updates slowed to a trickle. Long-standing bugs lingered. The forums filled with the same unresolved complaints. For a tool that agencies had bet their entire production workflow on, the quiet was unnerving.

Then came the part that really lit the fuse: Soflyy, the company behind Oxygen, launched a brand-new page builder called Breakdance. To a lot of people, that looked like the writing on the wall — why would a small team pour resources into a second builder unless the first one was being quietly retired? "They've abandoned Oxygen for Breakdance" became the default assumption across Reddit, Facebook groups, and developer Slacks.

It was a reasonable fear. It also turned out to be wrong.

What actually happened: Oxygen 6

Instead of abandoning Oxygen, Soflyy did something harder. They rebuilt it from scratch.

In February 2026, after roughly a year of development and a long beta cycle, Oxygen 6 launched as a complete, ground-up rewrite. The honest reason they gave is one any developer will recognize: the original codebase was built on aging technology (an Angular-based architecture from over a decade ago) that had become unsustainable to maintain. Every new feature meant more workarounds on a foundation that was fighting back. Rather than keep patching it, they started over with a modern stack designed to actually move fast.

That's the source of the naming confusion you're seeing. There are now effectively two Oxygens:

Oxygen Classic — the builder you've been using for years (now documented on a classic. subdomain).
Oxygen 6 ("New Oxygen") — the rewrite, with a new editor, components, variables, loop and taxonomy tooling, conditional visibility, and ongoing rapid updates.

So when someone asks if Oxygen is dead, the accurate answer is almost the opposite: it's seeing more active development than it has in years. The builder isn't the problem. The transition is.

Is Oxygen Classic still supported?

This is the question that actually matters for most people reading this, and the good news is reassuring.

Soflyy has committed to a dual-path approach: Oxygen Classic continues to be maintained alongside Oxygen 6, more or less as it has been. Your existing Classic sites are safe. They will keep working, keep receiving maintenance, and do not need to be rebuilt tomorrow, next month, or in a panic.

There's a catch worth being clear-eyed about, though. "Maintained" is not the same as "actively developed." Classic is now the legacy path — it will get stability and compatibility fixes, but the new features, the performance work, and the long-term roadmap all live in Oxygen 6. For a personal site or a finished project that just needs to keep running, that's completely fine. For client work you expect to extend and maintain for the next five years, building new sites on a legacy builder is a harder position to defend.

The decision Oxygen Classic users actually face

If you're on Oxygen Classic in 2026, you have three legitimate paths. None of them is wrong — they just fit different situations.

Path 1: Stay on Oxygen Classic

Perfectly reasonable when a site is finished, stable, and not slated for major changes. Classic is maintained, your builds work, and there's no urgency. The risk is slow accumulation of technical debt: you're on a frozen feature set, your team's skills drift toward a legacy tool, and "we'll deal with it later" quietly becomes "we have forty client sites on a builder nobody develops anymore."

Path 2: Move to Oxygen 6

The natural same-family upgrade, and the most appealing option for teams already invested in the Oxygen way of working. You get the modern editor and a roadmap that's actively moving. And if you hold a lifetime Classic license, here's the part people miss: Oxygen 6 is included for you — the new builder and its premium add-ons (including several Breakdance element collections) come with your existing license. The cost isn't the licence; it's the migration, which we'll get to.

Path 3: Switch to Breakdance or Bricks

If you're rethinking your stack anyway, this is the moment to evaluate alternatives honestly. Breakdance (also from Soflyy) trades some of Oxygen's raw control for a friendlier, guardrails-on workflow. Bricks has become the darling of the developer-and-agency crowd, with the largest community momentum of any of these builders right now. A platform change is more disruptive than moving to Oxygen 6 — but if your team's needs have outgrown Oxygen, doing it deliberately beats drifting.

The catch nobody mentions: your sites don't come along automatically

Here's the detail that turns this from a philosophical decision into a practical one.

Oxygen 6 is not backwards compatible with Oxygen Classic. You cannot install the new version, click update, and have your Classic sites carry over. The two use fundamentally different data structures under the hood. This was a deliberate choice — Soflyy dropped backwards compatibility so the new codebase wouldn't be shackled to the old one — and they've been upfront that it was one of the hardest calls they've made.

What that means in practice: every path except "stay on Classic" involves a migration, not an upgrade. Moving Classic → Oxygen 6 is a migration. Classic → Breakdance is a migration. Classic → Bricks is a migration. And historically, "migration" between page builders has meant the thing every developer dreads — rebuilding layouts by hand, page by page, recreating every section, every class, every breakpoint from scratch.

That manual rebuild is the real reason people put this decision off. It's also the problem TransferForge was built to solve. It converts your Oxygen Classic templates and components into Oxygen 6 or Breakdance format directly — preserving structure, classes, and styling — so choosing a path forward doesn't mean throwing away the work you've already done. You can convert your first handful of pages free to see how clean the output is before committing to anything.

The point isn't that you must migrate today. It's that "the builds don't transfer themselves" should be a known factor in your decision, not a nasty surprise you discover three sites in.

Frequently asked questions

Is Oxygen Builder still worth using in 2026? Yes — arguably more than it has been in years, thanks to the Oxygen 6 rewrite. The question isn't whether the builder is worth using; it's whether you build new work on Oxygen Classic (legacy, maintained) or Oxygen 6 (active, modern). For new projects, Oxygen 6.

Is Oxygen 6 free if I have an Oxygen Classic license? If you hold a lifetime Classic license, the new Oxygen is included at no extra cost, along with the Breakdance element add-ons. Always confirm the current terms on the official site, since launch pricing and add-on structures change.

Is Oxygen Builder better than Elementor? They aim at different users. Oxygen (and Bricks) prioritize clean code output and granular control, which developers and performance-focused agencies tend to prefer. Elementor prioritizes a friendly, mass-market editing experience at the cost of heavier markup. "Better" depends on whether you value control or convenience.

Does Oxygen Builder slow down my site? Oxygen has a long-standing reputation for lean output compared to heavier builders, and the Oxygen 6 rewrite was partly motivated by performance. As always, real-world speed depends far more on your hosting, images, and third-party scripts than on the builder itself.

Will Oxygen Classic eventually stop working? There's no announced end-of-life. Classic is on the maintained-but-not-actively-developed track. Existing sites are safe for the foreseeable future — but planning a path forward beats waiting until a future WordPress or PHP change forces your hand.

Bottom line

Oxygen Builder isn't dead. It was rewritten, and Oxygen Classic users now sit at a genuine fork in the road.

Your situation	Best path	What's involved
Finished, stable sites; no big changes coming	Stay on Oxygen Classic	Nothing — keep running on the maintained legacy build
Invested in Oxygen, want the modern builder	Move to Oxygen 6	A migration (not an update); included with a lifetime Classic license
Rethinking your stack entirely	Switch to Breakdance or Bricks	A platform migration; biggest change, best done deliberately

Whichever fork you take, the work you've already built is the asset worth protecting. The decision is which builder fits your next five years — and the migration is a solvable problem, not a reason to stay stuck.

Weighing Oxygen 6 against Breakdance specifically? That comparison deserves its own breakdown — and it's the next piece in this series.