Oxygen Builder

Quick take: Oxygen is a developer-first visual site builder for WordPress that replaces the normal theme presentation layer and gives advanced users direct control over templates, dynamic data, classes, variables, components, loops, conditions, and custom code.

What Oxygen is built for

Oxygen is aimed at developers, agencies, and technical site builders who want more structural control than a typical widget-first page builder. It can design the full site rather than only individual pages, including headers, footers, archives, single templates, custom post type layouts, and WooCommerce presentation.

Oxygen also takes a different architectural approach from theme-dependent builders. Oxygen Classic disables the normal WordPress theme system while active, and the current Oxygen product continues the full-site-builder direction. That makes Oxygen powerful, but it also means the builder becomes foundational infrastructure for the site’s presentation layer.

Dynamic data, loops, and conditions

Dynamic sites are a major Oxygen use case. The builder can connect elements to WordPress data such as posts, users, taxonomies, and custom fields, including common ACF and Meta Box workflows. Its loop tools can query posts, repeaters, taxonomies, and custom query structures, while conditions can show or hide elements based on data, user roles, and custom logic.

This makes Oxygen relevant for directories, real-estate sites, listings, membership portals, knowledge bases, WooCommerce stores, and other projects where layouts are generated from structured content rather than written page by page.

Developer-oriented design workflow

Oxygen’s workflow emphasizes reusable CSS classes, variables, components, selectors, semantic HTML, and custom code. The current generation adds a stronger component and variable system while keeping PHP, JavaScript, and CSS extensibility available for projects that need custom logic.

That flexibility is useful when a team already thinks in systems rather than isolated pages. It is less beginner-oriented than builders designed around prebuilt widgets and template kits. A good Oxygen project normally benefits from clear naming conventions, reusable classes, and a defined content model before the visual build grows large.

WooCommerce and full-site control

Oxygen supports deep WooCommerce customization so product pages, shop archives, and other store surfaces can be designed visually. Current Oxygen licensing also includes access to WooCommerce-related functionality in its broader product bundle, depending on the package purchased.

As with any visual WooCommerce layer, the builder controls presentation rather than replacing WooCommerce business logic. Payment gateways, subscriptions, taxes, shipping, product add-ons, and other extensions should still be tested independently on staging.

Oxygen Classic and the newer Oxygen generation

Oxygen now spans two product generations. Oxygen Classic remains supported for existing projects, while the newer Oxygen codebase was rebuilt around a more modern developer workflow with improved selector management, variables, components, interactions, and a redesigned interface.

For an existing Oxygen Classic site, that distinction matters. A buyer comparing Oxygen with Bricks, Breakdance, Elementor, or Beaver Builder should evaluate the current Oxygen experience and also understand whether a legacy project depends on Classic-specific structures that would still need to be maintained.

Pricing and licensing

Pricing checked: September 23, 2026. Oxygen currently advertises lifetime, unlimited-site licensing. The current pricing page lists Oxygen Classic Basic at $129 lifetime, WooCommerce at $149 lifetime, and Ultimate at $179 lifetime. It also advertises a $199.50 lifetime bundle that includes Oxygen Classic, the newer Oxygen generation, and premium add-ons during the current offer period.

The vendor has publicly stated that pricing is expected to change, so the checkout page should be treated as the source of truth immediately before purchase. Existing lifetime licenses remain lifetime licenses according to Oxygen’s published policy.

Where Oxygen fits best

Oxygen fits agencies, developers, and advanced builders who value clean structural control, dynamic data, custom code, and unlimited-site lifetime licensing. It is especially relevant when the site is more like a custom WordPress application than a collection of static marketing pages.

A simpler builder may fit better when clients need the easiest possible visual editing experience, the project depends heavily on prebuilt templates and third-party widgets, or the team does not want the builder to replace the theme presentation layer.

Trade-offs to understand

The main trade-off is architectural dependency. Because Oxygen can own the whole presentation layer, migrating away usually means rebuilding templates, dynamic bindings, loops, conditions, classes, components, and custom code. That is much larger than swapping a lightweight page-builder plugin.

The second trade-off is learning curve. Oxygen gives technical users extensive control, but the same flexibility can create inconsistent projects when teams do not standardize classes, variables, components, and naming conventions. The builder does not replace the need for a sound design and content architecture.

FAQs

PluginSuggest verdict

Oxygen is most compelling when a WordPress project needs developer-level control over the full presentation layer and the team values reusable classes, dynamic data, custom code, and lifetime unlimited-site licensing. The same architecture makes migration and client handoff more consequential, so it should be chosen as a long-term site-building system rather than a casual page-editor add-on.

Related guide: 7 Best WordPress Page Builders in 2026