Oxygen

What Is Oxygen?

Oxygen is a visual website builder for WordPress that replaces your theme entirely and gives you direct control over the markup and CSS of every page. Instead of working inside the boundaries a theme imposes, Oxygen deactivates the theme layer and lets you design the header, footer, content, and templates from a blank canvas, outputting lean HTML and CSS rather than the heavy, shortcode-laden markup that some page builders produce. It is aimed squarely at developers, freelancers, and agencies who want pixel-level control and clean output on top of WordPress.

Oxygen is developed by Soflyy, the same company behind the WP All Import plugin, and it has built a devoted following among technical WordPress users since its modern relaunch. It is widely regarded as one of the most powerful and developer-oriented visual builders in the WordPress ecosystem, frequently mentioned alongside Elementor, Bricks, and Beaver Builder in discussions of serious site-building tools. Rather than chasing the broad beginner market, Oxygen has concentrated on users who care about performance, code quality, and unrestricted design freedom.

A defining characteristic of Oxygen is that it is sold under a lifetime license model rather than a recurring subscription, which has historically been a major draw for agencies building many client sites. The product is a premium plugin, so there is no free tier on the WordPress.org repository, and it is installed and licensed directly through the vendor.

Oxygen is not a hosted platform, a browser extension, or a standalone CMS. It is a WordPress plugin that runs on whatever server hosts the WordPress installation, and because it disables the active theme and renders pages through its own engine, it leaves recognizable fingerprints in the HTML, CSS class names, and asset paths of any site that uses it. That makes Oxygen detectable from the outside even though it is a back-end tool.

It helps to understand exactly where Oxygen sits relative to other builders. Most WordPress page builders operate inside the theme: they let you design the content area of a page while the theme still controls the surrounding structure, the stylesheet, and much of the markup. Oxygen takes the opposite approach by switching the theme off and assuming responsibility for the entire front end, from the opening tags of the document to the closing footer. That decision is the source of both its power and its learning curve. It means there is no theme fighting your styles and no inherited bloat, but it also means you are responsible for building everything yourself, which is why Oxygen rewards users who already think like front-end developers.

How Oxygen Works

When Oxygen is active, it intercepts WordPress's normal theme-rendering process. The active theme is effectively bypassed, and Oxygen takes over generating the page markup. You design inside the Oxygen editor, a visual interface that exposes the underlying structure as a tree of elements, sections, containers, columns, headings, text blocks, images, and more, each of which maps to real HTML rather than to opaque widgets.

Styling in Oxygen is built around CSS fundamentals. You can style elements individually, apply reusable CSS classes, or define selectors directly, and the builder writes clean CSS rather than wrapping everything in nested shortcodes. This class-based, selector-aware approach mirrors how a front-end developer would author a stylesheet, which is the main reason Oxygen sites tend to ship far less markup and CSS than sites built with heavier builders.

Oxygen's templating system is central to how it operates. Rather than editing one page at a time, you build Templates that control entire categories of content, for example a single-post template, an archive template, or a template for a specific custom post type. Templates use a priority and inheritance system so that the right template applies to the right content automatically. Reusable parts such as headers and footers are built once and applied across templates, and a Reusable Parts feature lets you maintain shared blocks in a single place.

Dynamic content is handled through Oxygen's dynamic data features, which pull values from WordPress fields, custom fields, and popular tools like Advanced Custom Fields. This lets you design a single template that renders many pieces of content, binding headings, images, and metadata to dynamic sources just as a developer would in a theme template. Oxygen also integrates with WooCommerce so that store templates can be built visually.

A useful way to picture the workflow is to follow one project from start to finish. A developer installs Oxygen, which disables the theme, and begins by building a global header and footer as reusable parts. They then create a set of templates: one for the home page, one for single blog posts, one for archives, and perhaps several for custom post types. Within each template they bind dynamic data so that a single design renders every matching item. Reusable parts and shared CSS classes keep the whole system consistent, so a change to the header or to a class propagates everywhere at once. The result is a tightly controlled, lightweight front end that behaves like a hand-built theme but was assembled visually.

Under the hood, the fact that Oxygen owns the entire document, rather than slotting content into a theme, is what allows it to keep output lean. There is no theme stylesheet to override and no inherited scaffolding, so the only CSS and markup on the page are what you deliberately created. This is also why Oxygen's footprint is so visible to anyone inspecting the page source: its characteristic class-naming scheme and asset directory appear throughout the rendered HTML.

How to Tell if a Website Uses Oxygen

Oxygen leaves several reliable fingerprints. Because StackOptic analyzes a URL from the server side, it looks at the same signals you can check manually with browser tools, curl, or a detection extension.

Oxygen CSS class names. The strongest signal is Oxygen's distinctive class-naming convention. Elements built in Oxygen carry classes prefixed with oxy- (for example oxy-rich-text, oxy-header-row, or oxy-nav-menu) and structural IDs in patterns like div_block-... and _header-.... Seeing these oxy- classes scattered through the markup is close to definitive.

Oxygen asset paths. Oxygen serves its generated stylesheets and scripts from predictable locations under the WordPress uploads directory, commonly within an oxygen folder (for example a path containing /wp-content/uploads/oxygen/css/). Requests to an oxygen asset directory are a strong indicator.

Plugin directory references. Some assets and scripts reference the plugin's own folder under /wp-content/plugins/oxygen/. Any reference to that path confirms the plugin is installed.

Absence of a conventional theme. Because Oxygen disables the theme, you will typically not see the usual /wp-content/themes/<theme>/style.css references that a standard WordPress site exposes. A WordPress site that is clearly WordPress but is missing normal theme stylesheets, while showing oxy- classes, is almost certainly using Oxygen.

Underlying WordPress signals. Oxygen runs on WordPress, so the usual WordPress tells remain: /wp-content/, /wp-includes/, and often the wp-json REST endpoint. Confirming WordPress first, then spotting the oxy- layer, gives a confident verdict.

Here is how to check each signal yourself:

Method	What to do	What Oxygen reveals
View Source	Open the page, right-click, "View Page Source"	oxy- class names, div_block IDs, oxygen asset paths
Browser DevTools	Inspect elements and the Network tab	oxy- classes on the DOM, requests to /uploads/oxygen/css/
curl -I and curl -s	curl -s https://example.com | grep -i oxy-	Confirms oxy- classes and Oxygen asset references in the raw HTML
Wappalyzer	Run the extension on the live page	Often identifies "Oxygen" as a page builder, and WordPress as the CMS
BuiltWith	Look up the domain	WordPress detection plus any Oxygen footprint it recognizes

A quick command-line check is curl -s https://example.com | grep -i "oxy-". If that returns matches alongside /wp-content/ references, you are almost certainly looking at an Oxygen-built WordPress site. For a deeper walkthrough of WordPress detection, see our guides on how to tell if a website is built with WordPress and how to identify a WordPress theme and plugins.

It is worth noting how these signals behave on production sites. Because Oxygen generates a cached CSS file specific to each site, the exact file name varies, but the oxygen directory and the oxy- class prefix are consistent across installations. A developer could, in principle, rename or restructure classes, but doing so works against the builder's own conventions and is uncommon, so the prefix is dependable in practice. Combining multiple signals, the oxy- classes, the oxygen asset directory, and the underlying WordPress markers, makes detection very reliable even on heavily customized sites. Server-side analysis is especially valuable here because it fetches the unmodified HTML directly, without the noise a browser introduces by executing scripts and rewriting the DOM.

Key Features

• Theme replacement. Disables the active theme and gives you full control of the entire document, header to footer.
• Clean, lean output. Produces minimal HTML and CSS without the shortcode bloat common to some builders.
• Visual templating. Build templates for posts, pages, archives, and custom post types with a priority and inheritance system.
• Reusable parts. Maintain shared headers, footers, and blocks in one place and apply them everywhere.
• Dynamic data. Bind designs to WordPress fields, custom fields, and tools like Advanced Custom Fields for fully dynamic templates.
• Code control. Add custom CSS, JavaScript, and PHP code blocks directly within the builder when needed.
• WooCommerce support. Design store templates visually, with dynamic product data.
• Lifetime licensing. A one-time license model rather than a recurring subscription.

Pros and Cons

Pros

• Outputs genuinely lean markup and CSS, which supports strong Core Web Vitals performance.
• Total design freedom because there is no theme constraining structure or styles.
• Powerful, developer-friendly templating and dynamic-data handling.
• A lifetime license is attractive for agencies building many client sites.

Cons

• A steep learning curve that assumes familiarity with HTML, CSS, and WordPress templating.
• Because it replaces the theme, switching away from Oxygen later means rebuilding the front end.
• Smaller ecosystem of add-ons and third-party tutorials than the largest page builders.
• Not a fit for non-technical users who want a simple, template-first experience.

Oxygen vs Alternatives

Oxygen sits at the developer-focused end of the WordPress visual-builder spectrum. The table below compares it with common alternatives.

Builder	Approach	Output	Best for
Oxygen	Replaces the theme; full-document control	Lean HTML/CSS	Developers and agencies wanting clean code and total freedom
Elementor	Works inside the theme; widget-based	Heavier markup	Beginners to pros who want a huge ecosystem
Bricks	Theme-based visual builder, performance-focused	Lean markup	Developers wanting clean output with a theme structure
Beaver Builder	Theme-based, stability-focused	Moderate markup	Agencies prioritizing reliability
Divi	Theme plus builder	Heavier markup	Users wanting an all-in-one design system

If you suspect a site uses a different builder, our guides on how to find out what technology a website uses and how to identify a WordPress theme and plugins walk through the fingerprints for each. You can also compare Oxygen against the most widely deployed builder, Elementor.

Use Cases

Oxygen is most at home for developers and agencies building custom WordPress sites where performance and code quality matter. Because it strips away the theme layer and outputs lean markup, it is a frequent choice for brochure and marketing sites that need to score well on Core Web Vitals without the weight that heavier builders can introduce.

It also suits agencies standardizing on a single, license-friendly tool across many client projects, freelancers who want hand-coded quality without writing every line by hand, and technical teams building content-rich sites with custom post types and dynamic templates. WooCommerce stores that want a uniquely designed, fast storefront are another natural fit, since Oxygen can template the entire shopping experience.

Consider a few concrete scenarios. A web studio might adopt Oxygen as its house builder, creating a reusable library of headers, footers, and templates that it adapts for each new client, benefiting from the lifetime license as it scales. A performance-conscious business might rebuild a slow, plugin-heavy WordPress site in Oxygen specifically to cut page weight and improve load times. A developer with strong front-end skills might use Oxygen to deliver a fully custom design on a tight timeline, binding Advanced Custom Fields data to templates rather than hand-coding a theme from scratch. In each case the common thread is a desire for control and performance on top of WordPress.

From a sales-intelligence perspective, detecting Oxygen on a prospect's site is a meaningful signal in its own right. It suggests a technically sophisticated team or agency that values performance and clean code, which can indicate a strong fit for developer tools, performance services, or premium hosting. For agencies evaluating a maintenance or re-build opportunity, recognizing Oxygen across a portfolio of prospects helps gauge how a site was constructed and what migrating or maintaining it would involve, insight that a technology-detection scan surfaces in seconds.

Frequently Asked Questions

Is Oxygen a theme or a plugin?

Oxygen is a WordPress plugin, but it behaves unusually in that it disables your active theme and takes over rendering the entire front end. So while you install it like any plugin, in practice it functions as a theme replacement and a complete site-building system. That is why a site running Oxygen typically shows no conventional theme stylesheet even though it is clearly WordPress.

Can you tell if a site is built with Oxygen for free?

Yes. View the page source and look for class names prefixed with oxy-, structural IDs like div_block-..., and asset paths containing an oxygen folder under /wp-content/uploads/. Free tools like Wappalyzer and BuiltWith can confirm both WordPress and, often, the Oxygen builder, and a single curl -s URL | grep oxy- command works from any terminal.

Does Oxygen produce good code for SEO and performance?

Oxygen is specifically designed to output lean HTML and CSS without shortcode bloat, which tends to support good Core Web Vitals scores and fast load times, both of which help with search visibility. You still control title tags, headings, structured data, and content quality yourself, so SEO outcomes depend on how you build the site rather than on the builder alone. For a structured approach, see our guide on how to do an SEO audit.

What happens if I deactivate Oxygen?

Because Oxygen replaces the theme and renders pages through its own engine, deactivating it removes that rendering layer, and WordPress falls back to whatever theme is active. Sites built entirely in Oxygen therefore depend on it for their front end, so moving away from Oxygen generally means rebuilding the design in a theme or another builder rather than simply switching it off.

Is Oxygen better than Elementor?

They target different users. Oxygen favors developers who want lean output, full-document control, and a lifetime license, while Elementor favors a broader audience with a vast ecosystem of add-ons, templates, and tutorials and a more approachable interface. Oxygen typically produces lighter markup, whereas Elementor offers more out-of-the-box convenience. The right choice depends on whether you prioritize code quality and freedom or ease of use and ecosystem breadth.

Want to identify Oxygen and the rest of a site's stack automatically? Run any URL through StackOptic at https://stackoptic.com.