Oxygen Builder 6.1 Maintenance Status: What Documented Release Cadence Means for Existing Users
For teams running production WordPress sites on Oxygen, the shift to a maintenance-focused release model raises practical questions about long-term viability. This article examines what the vendor’s official releases page actually documents about Oxygen 6.1.3 and the broader 6.x cycle, how that compares to the preceding release gap, and what maintenance-only status means for feature development expectations—without projecting business strategy onto the data.
Oxygen 6.1.3: Documented Scope as a Stability Release
The vendor’s official releases page identifies Oxygen 6.1.3 as a maintenance release focused on stability. Vendor documentation states this minor release fixes a bug introduced in Oxygen 6.1.2. This follows the same pattern as Oxygen 6.1.1, which the vendor’s official releases page also describes as a maintenance release focused on stability that clears out regressions reported after 6.1 and polishes the builder experience.
The 6.1 major release itself introduced several builder-facing features: multi-element selection, variable fonts, conditional classes, component visibility, multi-class entry, and PHP 8.4 support, per vendor documentation. The vendor’s official releases page also notes faster previews as part of that release. However, subsequent 6.1.x point releases have narrowed to bug fixes rather than expanding feature scope.
| Release | Documented Type | Key Notes from Vendor Documentation |
|---|---|---|
| Oxygen 6.1 | Feature release | Multi-element selection, variable fonts, conditional classes, PHP 8.4 |
| Oxygen 6.1.1 | Maintenance release | Regressions cleared, builder experience polished |
| Oxygen 6.1.3 | Maintenance release | Bug fix for issue introduced in 6.1.2 |
This table reflects only what the vendor’s official releases page documents. No performance benchmarks or load-time figures appear in the provided material for any of these releases.
The Release Gap: December 2024 to Present
Vendor releases archives document December 9, 2024 as the release date for Oxygen 4.9.1, described on the vendor’s official releases page as a minor release with several bug fixes and one enhancement: the ability to copy and paste conditions between elements. The same archives show Oxygen 4.9.1 RC 1 on November 15, 2024 and Beta 1 on October 24, 2024.
This establishes a documented timeline: the 4.9.1 release in December 2024 preceded the 6.x line, with vendor documentation indicating the 6.1 Beta cycle began after that point. The gap between the 4.9.x maintenance line and 6.1’s feature introduction is part of the documented release history, though the material does not specify exact duration in months between final 4.9.x and 6.1 general availability.
What “Maintenance-Only” Status Means for Feature Expectations
The vendor’s official releases page provides clear language about release intent: “maintenance release focused on stability” appears for multiple consecutive 6.1.x versions. This documented pattern has specific implications for existing users evaluating whether to stay on Oxygen.
Documented characteristics of the current maintenance phase:
- Bug fixes over feature additions
- Regression cleanup from prior releases
- Polish on existing builder workflows rather than new capabilities
- Point-release increments (6.1.1, 6.1.3) rather than minor or major version bumps
The material does not contain any vendor-claimed timeline for when feature development might resume, nor does it specify performance metrics or load-time targets for maintenance releases. Users should not infer a return to feature-heavy releases based solely on the documented pattern.
For teams deciding whether to adopt or remain on Oxygen, this maintenance status means evaluating whether the existing feature set—CSS grid builder, composite elements library, WooCommerce integration, dynamic data, and the documented 6.1 additions—satisfies current project requirements without anticipating near-term expansion.
Who Oxygen Is Wrong For
Based on documented release patterns and vendor-provided feature scope, Oxygen is a poor fit for several user profiles:
Users needing frequent feature updates. The maintenance-only cadence documented on the vendor’s official releases page shows no current pipeline of builder-facing enhancements. Teams accustomed to quarterly feature drops from other builders will find the stability-focused model mismatched to their workflow expectations.
Those wanting marketplace ecosystem growth. While the vendor’s official updates page documents that the Oxygen Marketplace is open for templates and extensions, this is a platform launch rather than an indicator of rapid third-party expansion. The marketplace accepts Design Sets built with Oxygen 6, but the material does not cite vendor documentation showing marketplace volume, active developer count, or growth metrics. Users prioritizing a large, mature extension ecosystem have documented alternatives with longer marketplace histories.
Teams requiring active Gutenberg integration roadmaps. Vendor documentation lists Gutenberg & Clients as a product category, but the provided material contains no release notes or roadmap documentation showing active Gutenberg block conversion or FSE (Full Site Editing) bridge development. Maintenance releases do not expand integration scope.
Organizations dependent on predictable major-version cadence. The gap between 4.9.1 (December 2024) and the 6.x line, combined with the subsequent maintenance focus, does not establish a pattern of regular major releases that project planning can rely upon.
Competitor Release Cadence: Only Documented Figures
The provided material contains limited directly comparable figures for competitor release patterns. Published third-party benchmarks report that Elementor scores require optimization with caching/CDN to reach certain performance ranges, though the specific range is not numerically defined in the material. Published third-party coverage also notes that sites built with Oxygen consistently achieve the fastest load times in comparative testing—often faster than Bricks equivalents and significantly faster than Elementor, though these figures originate from third-party testing rather than vendor documentation.
No vendor-provided release cadence figures for Elementor, Bricks, Divi, or other builders appear in the material. Without documented comparison points, claims about relative update frequency cannot be sourced. The qualitative observation from published third-party coverage is that Bricks is “relatively new compared to Oxygen or Elementor, so the community and third-party resources are still growing”—a community-size comparison, not a release-schedule one.
| Comparison Dimension | Oxygen (Vendor-Documented) | Competitors (Material Limits) |
|---|---|---|
| Current release type | Maintenance/stability | Not specified in vendor docs |
| Most recent feature release | 6.1 (multi-element selection, variable fonts, etc.) | No comparable vendor figures |
| Marketplace status | Open, accepting Design Sets | No vendor-documented status |
| Load time claims | None claimed by vendor | Published third-party benchmarks report Oxygen faster than Bricks and Elementor |
Before Updating: Back Up First
Back up your site completely before applying any Oxygen version update. This includes:
- Full database export
- wp-content directory, with special attention to
uploads/oxygen/for custom CSS and design assets - Active theme and plugin files
- Test environment verification if available
This step is non-negotiable regardless of whether the vendor’s official releases page labels a release as “minor” or “maintenance.” Oxygen 6.1.3 specifically addresses a bug introduced in 6.1.2, which demonstrates that even point releases can carry regression risk. Apply updates first to a staging environment that mirrors production configuration.
The Oxygen Marketplace: Documented Context
The vendor’s official updates page documents the Oxygen Marketplace is open as a platform for listing templates and extensions. Vendor documentation specifies that sellers can list templates and extensions on oxygenbuilder.com, with submission categories including full site designs built with Oxygen 6 and exported as Design Sets.
This marketplace opening is a documented vendor update, not a third-party development. However, the material does not contain:
- Number of listed products or active sellers
- Revenue share percentages or fee structures
- Submission review timeline
- Geographic or payment restrictions
Users evaluating Oxygen’s ecosystem viability should treat the marketplace as newly available infrastructure rather than as evidence of mature third-party adoption. The distinction matters for teams deciding whether Oxygen’s extension ecosystem meets project requirements today versus its potential future state.
Reading the Release Notes: A Habit for Maintenance-Phase Users
During feature-heavy development cycles, release notes highlight capabilities that might accelerate project work. During maintenance phases, they serve a different function: identifying whether fixed bugs affect your specific site configuration.
The vendor’s official releases page documents specific fixes in the 6.1.x series:
- Pagination margin application in Post Loop Builder slider layouts
- Skip link behavior with Template Content Area elements
- Code editor modal scrolling
- Element Studio edit persistence and control section stability
Teams should scan these against their active template structures and custom implementations rather than skimming for new capabilities.
Verdict for Technical Evaluators
Oxygen 6.1.3’s documented status as a maintenance release focused on stability, following 6.1.1 with the same classification, establishes a clear pattern in vendor documentation. The December 9, 2024 release of Oxygen 4.9.1 anchors the timeline, showing the duration of the pre-6.x maintenance period and the subsequent transition.
For existing users, this means:
- Stability is the documented priority, not expansion
- The 6.1 feature set is likely to remain static for the near term
- Marketplace infrastructure exists but without documented maturity metrics
- Backup discipline matters more when even point releases address regressions
For prospective adopters, the evaluation centers on whether Oxygen’s current documented capabilities—visual CSS grid, composite elements, PHP 8.4 support, and the 6.1 workflow improvements—suffice without anticipating the feature cadence typical of builders in active development phases. The vendor’s own documentation provides the basis for that assessment; no extrapolation beyond what is officially stated is warranted.
If Oxygen’s Maintenance Phase Doesn’t Fit Your Project
Teams needing active feature development and predictable enhancement cycles have alternatives with documented ongoing investment. For builders in active development with consistent release cadence and established ecosystems, consider these options:
Check Elementor’s current pricing
Elementor serves as the lead pick for both DIY small business owners and agency resellers evaluating page builders, with the most consistent commission data across research rounds. It offers the active feature development and marketplace maturity that Oxygen’s maintenance phase currently does not provide.
Divi membership carries the highest-consistency commission data of any program researched, with recurring commissions confirmed identically across all research rounds. Note that this uses a bare-domain link pending affiliate approval.
Check SiteGround’s current hosting plans
SiteGround WordPress hosting fits here as a secondary recommendation for hosting infrastructure alongside your builder choice—never the answer to a builder-or-theme question, but relevant for teams undertaking a full platform migration. You trade away builder-specific guidance for hosting infrastructure support.
This post contains affiliate links. If you purchase through our links, we may earn a small commission at no extra cost to you.
