Firefox 153 Lands With Vulkan Video Decoding and JPEG-XL

Mozilla is shipping Firefox 153 with a feature Linux desktop users and web-performance enthusiasts have watched for months: initial Vulkan Video decode support, alongside continued rollout of experimental JPEG-XL image rendering. Per Mozilla's release-train schedule, Firefox 153 is offered to the Release channel on July 21, 2026, and it is also designated the newest Extended Support Release (ESR) — making it a landmark update for enterprise and institutional deployments that require long-term stability. This article covers the Firefox 153 release date, the feature set as it stands, how it differs from the previous ESR, and what the changes mean for developers, end users, and IT teams.

Note on sourcing: at the time of writing, Mozilla's official Firefox 153 release notes page indicates the notes are still being finalized. Feature details below are drawn from Mozilla's Nightly/Beta release notes and reputable coverage; treat exact codec coverage and edge-case behavior as subject to the final published Firefox 153 release notes.

What Makes Firefox 153 a Milestone Release

Not every monthly Firefox release pairs a significant graphics-subsystem upgrade with an ESR designation — and Firefox 153 does exactly that. That combination of timing is strategically important: organizations that adopt the ESR track will carry Vulkan Video decode capability forward across an extended maintenance window, rather than that feature being restricted to rolling-release audiences. For enterprise IT departments, that means infrastructure-wide access to hardware-accelerated video on a wider range of GPUs without waiting for a future ESR cycle.

Mozilla's recent ESR cadence designates a new ESR roughly once a year, with consecutive ESRs overlapping for about a year so IT teams have a migration window. The visible sequence of recent ESR baselines — 115 ESR, 128 ESR, 140 ESR, and now 153 ESR — reflects that annual rhythm. ESR builds receive security and stability backports for an extended period, making this the go-to build for schools, governments, and organizations that cannot afford frequent browser churn. Firefox 153 ESR thus becomes the new stable baseline those audiences will track for the foreseeable future.

Firefox 153 Release Date and Where to Get It

Firefox 153 follows Mozilla's approximately four-week release cadence and is offered to Release-channel users starting July 21, 2026 (with a staged rollout typical of Mozilla launches). Release binaries — including Windows, macOS, and Linux builds — are available directly from ftp.mozilla.org/pub/firefox/releases/153.0/. The official Firefox 153 release notes are published at mozilla.org/en-US/firefox/153.0/releasenotes/ and contain the authoritative, fully itemized changelog once finalized. Users on supported Linux distributions can also receive Firefox 153 through their package manager or via the Snap and Flatpak channels.

Firefox 153 Beta

Before the stable release landed, Firefox 153 Beta was available through Mozilla's Beta channel at mozilla.org/en-US/firefox/channel/desktop/. The Beta channel is where Vulkan Video decode was exercised outside of Nightly builds, allowing Mozilla's engineering team to collect compatibility reports and performance data before promoting the release to stable. Users who participated in the Beta program may have already seen these features in operation; the stable release represents the hardened, regression-tested version of that work.

Vulkan Video Decoding: Solving Linux's GPU Acceleration Problem

The most technically consequential feature in Firefox 153 is its initial Vulkan Video decode support. To understand why this matters, some background on the Linux video-acceleration landscape is essential.

The VA-API Limitation

Firefox on Linux has historically relied on the Video Acceleration API (VA-API) to offload video decode work to the GPU. VA-API functions well on Intel and AMD hardware, where vendor-supplied drivers implement it natively. The problem is NVIDIA. NVIDIA does not ship an official VA-API driver for Linux; users who want hardware-accelerated video through VA-API on NVIDIA GPUs must rely on the community-maintained nvidia-vaapi-driver project, which layers VA-API on top of NVIDIA's proprietary NVDEC decoder. That approach works, but it introduces an unsupported third-party dependency — a fragile link in the chain that can break with driver updates or kernel changes.

Beyond NVIDIA, a second category of hardware is left out entirely: embedded and specialized GPU drivers that never implemented VA-API. On devices like single-board computers, certain ARM-based systems, and niche accelerator hardware, VA-API support is absent, meaning Firefox has had no hardware decode path at all on those platforms — falling back to CPU-bound software decoding with the associated power and performance penalties.

Why Vulkan Video Changes the Equation

Vulkan Video is a standardized extension to the Khronos Group's Vulkan API designed to solve cross-vendor video acceleration. Unlike VA-API — developed primarily in a Linux/Intel context — Vulkan is explicitly cross-vendor and cross-platform, with AMD, Intel, NVIDIA, ARM, and Qualcomm all participating in the specification process. The result is a single decode interface that maps onto each vendor's native hardware capabilities without requiring translation layers or community-maintained shims.

As Phoronix summarized the release, "Making Firefox 153 exciting is that it's the newest Extended Support Release 'ESR' as well as introducing Vulkan Video decode support." The broader appeal, in this writer's assessment, is that a Vulkan-based decode path can reach hardware that VA-API never served well — NVIDIA GPUs without an official VA-API driver, and embedded or specialized GPUs whose drivers never implemented VA-API at all. "Initial" is the operative word: this is a foundation, not a complete implementation. Users on exotic or embedded hardware should expect incremental improvements across subsequent releases rather than a fully polished experience on day one.

The Vulkan Video specification defines decode profiles for H.264 (AVC), H.265 (HEVC), and AV1 — the three codecs most relevant to web video today. Firefox 153's initial implementation is expected to target the most widely used of these first, with the precise codec coverage that ships in 153 documented in the final release notes and broader coverage following in subsequent releases.

For NVIDIA Linux users specifically, Vulkan Video means Firefox can use NVDEC through Vulkan without a community-maintained shim sitting in between. Combined with NVIDIA's substantial Vulkan driver investment on Linux, this path is designed to be more robust long-term than the VA-API workaround — and unlike the community driver, it requires no manual installation step by the user or administrator.

JPEG-XL: Experimental but Accessible via Firefox Labs

Firefox 153 continues Mozilla's cautious march toward the JPEG-XL image format, which offers better compression than JPEG, WebP, PNG, and GIF while also supporting lossless encoding, wide color gamut, and high dynamic range. Experimental JPEG-XL first reached Nightly with Firefox 153's development cycle and was surfaced to release users through the Firefox Labs panel in Firefox 152; support remains experimental and must be manually enabled. The activation path is available through both the Firefox Labs panel and, for advanced users, an about:config flag.

How to Enable JPEG-XL in Firefox 153

There are two activation methods, depending on your preference:

Method 1: Firefox Labs (Recommended)

1. Open Firefox and navigate to the Settings menu (hamburger icon → Settings, or about:preferences).
2. Scroll to or search for the Firefox Labs section.
3. Locate the JPEG-XL toggle and enable it.
4. Restart Firefox if prompted to apply the change.

Method 2: about:config Flag

1. Type about:config into the address bar and press Enter.
2. Accept the risk warning if prompted.
3. Search for the JPEG-XL image preference (commonly image.jxl.enabled).
4. Double-click the preference to toggle its value to true.
5. Restart Firefox.

Firefox Labs is Mozilla's formalized incubation space for features functional enough to expose to interested users but not yet hardened for the general population. By routing JPEG-XL through Firefox Labs, Mozilla signals that the implementation has reached a reasonable level of stability — it simply has not yet cleared the bar for default enablement. Compatibility edge cases, decoding performance on certain image classes, or rare rendering regressions may still be outstanding items being resolved before JPEG-XL ships on by default. Because the raw about:config pref can change, the Firefox Labs toggle is the reliable, supported way to enable the feature.

JPEG-XL's Journey in Firefox and Across Browsers

JPEG-XL has had a complicated history across the browser landscape. Mozilla's own release notes describe it as generally providing "better compression than WebP, JPEG, PNG, and GIF" and note it is "designed to supersede them." Mozilla has been incrementally building out the implementation, routing it through Firefox Labs to collect real-world telemetry from power users before promoting it to default-on status.

Google removed JPEG-XL from Chromium in late 2022, citing insufficient evidence of ecosystem value, before later moving to re-add support. Apple added JPEG-XL support in Safari 17. The format's slow path to universal browser support reflects both genuine technical complexity — JPEG-XL's feature set is substantially richer than JPEG — and the competitive dynamics among browser vendors around image-format adoption. Mozilla's measured approach (ship it in Labs, gather data, promote to default) is consistent with how it has handled other significant format transitions.

Settings Redesign, PDF Improvements, and HDR Video Context

Vulkan Video is the marquee Firefox 153 feature, but the recent Firefox release cadence has also delivered several quality-of-life improvements that carry into the 153 ESR baseline.

The Redesigned Firefox Settings

The Firefox settings interface received a major overhaul in Firefox 152, which introduced, in Mozilla's words, "a brand-new look with streamlined organization, clearer groupings, and improved navigation for easier customization." Firefox 153 carries that redesigned settings architecture forward. For users upgrading to the Firefox 153 ESR from significantly older versions (for example, from the 140 ESR), the new settings UI is a visible change: the layout rethinks how options are categorized to reduce time spent hunting through long, flat preference lists. The Firefox Labs panel through which JPEG-XL is enabled lives within this redesigned Settings surface.

PDF Enhancements

Recent Firefox releases have continued to invest in the built-in PDF viewer (PDF.js), including capabilities such as merging PDFs via drag-and-drop into the PDF sidebar and adding images as new pages within PDFs. This sustained investment reinforces Mozilla's push to make Firefox a capable document-handling tool without third-party plugins — a meaningful consideration for enterprise deployments where Adobe Reader or similar dependencies introduce security and licensing overhead. The complete list of PDF.js changes that ship in 153 is documented in the official Firefox 153 release notes.

HDR Video Playback on Windows (Introduced in Firefox 152)

For context, HDR video playback on Windows was added in Firefox 152, not 153. Per Mozilla's release notes, "High dynamic range video is now supported in Firefox on Windows 10 and 11 for HDR displays connected to AMD and NVIDIA GPUs (notably this excludes Intel+NVIDIA laptops for now)." Because Firefox 153 is the new ESR, that HDR capability is now part of the long-term ESR baseline. The feature complements the Vulkan Video work — both represent Mozilla treating media fidelity as a competitive axis where it had previously lagged, though the Intel+NVIDIA laptop exclusion means coverage is not yet universal.

Firefox 153 Release Notes: Feature Comparison Table

Feature / Area	Prior Stable Release (152)	Firefox 153
Video decode acceleration (Linux)	VA-API only	VA-API + initial Vulkan Video decode (codec coverage per final release notes)
JPEG-XL support	Experimental via Firefox Labs (introduced in 152)	Experimental via Firefox Labs (carried forward)
HDR video (Windows)	Added in 152 (AMD/NVIDIA GPUs; excludes Intel+NVIDIA laptops)	Carried into the ESR baseline
Settings UI	Redesign introduced in 152	Redesign carried forward
PDF viewer (PDF.js)	Ongoing enhancements	Further enhancements (see release notes)
ESR status	No	Yes — designated newest ESR release

The ESR Designation: Why Enterprises Should Pay Attention

Firefox ESR releases are not simply a stability label — they represent a deliberate product commitment. Organizations on the ESR track receive security patches and critical bug fixes for an extended period without being required to adopt new features from monthly releases. When a new ESR version is designated, IT teams get a defined validation window to test and deploy the update across managed fleets before the previous ESR reaches end-of-life — the overlap between the 140 ESR and the new 153 ESR provides exactly that runway.

The fact that Firefox 153 ESR ships with Vulkan Video decode is strategically significant for mixed-hardware enterprise environments. Organizations running a blend of NVIDIA, Intel, and AMD GPUs on Linux previously needed to ensure the community nvidia-vaapi-driver was deployed on every NVIDIA machine to achieve consistent hardware-accelerated video — an extra, unsupported dependency to manage across potentially thousands of endpoints. With Vulkan Video in the ESR baseline, those organizations gain a more uniform, in-tree path to GPU-accelerated video playback, provided Vulkan drivers are present. On modern Linux distributions — including enterprise-focused distributions like RHEL 9, Ubuntu 22.04 LTS, and SUSE Linux Enterprise — Vulkan driver availability is increasingly safe to assume, though administrators should still validate against their specific driver versions.

For enterprise deployments that also manage document workflows, the PDF enhancements in recent Firefox releases add incremental value. Firefox's PDF.js implementation already eliminates the need for Adobe Reader browser plugins in many enterprise environments, and each iteration strengthens that case — reducing third-party plugin dependencies that represent both security attack surface and licensing cost.

Why it matters for enterprise: Firefox 153 isn't just a feature release — its ESR designation means initial Vulkan Video decode, improved PDF handling, the HDR video support introduced in 152, and the redesigned Settings become the stable, long-term baseline for institutional Firefox deployments. Organizations still relying on VA-API workarounds for NVIDIA hardware on Linux now have a supported, in-browser migration path baked into the ESR channel itself.

Key Takeaways: Firefox 153 at a Glance

• Firefox 153 is offered to Release users on July 21, 2026, and is the newest designated Extended Support Release (ESR), following Mozilla's roughly one-year ESR cadence (115 → 128 → 140 → 153).
• Vulkan Video decode support is introduced as an initial implementation, providing a cross-vendor hardware-acceleration path — directly addressing VA-API's lack of official NVIDIA support and gaps in embedded driver coverage; exact codec coverage in 153 is defined by the final release notes.
• JPEG-XL support is experimental and must be enabled through the Firefox Labs section of Settings (or via the JPEG-XL image preference in about:config) — it is not on by default and was surfaced to release users in Firefox 152.
• HDR video playback on Windows shipped in Firefox 152 (AMD and NVIDIA GPUs, excluding Intel+NVIDIA laptops for now) and is now part of the 153 ESR baseline.
• PDF enhancements continue in Firefox's built-in PDF.js viewer, reducing enterprise dependency on third-party document plugins.
• The settings redesign introduced in Firefox 152 carries forward, giving users — including new ESR adopters upgrading from older versions — a modernized preferences interface with clearer organization and the Firefox Labs panel.
• The ESR designation means the full Firefox 153 feature set becomes the long-term stable baseline for enterprise, education, and institutional deployments for an extended maintenance window.
• Release binaries and the full Firefox 153 release notes are available at ftp.mozilla.org and mozilla.org respectively.

What Comes Next

With Vulkan Video decode landing as an "initial" implementation, the roadmap trajectory is well-defined even if specific timelines are not yet announced: broader codec coverage, performance parity with the VA-API path on supported hardware, and eventually default enablement once the implementation is sufficiently mature. JPEG-XL's trajectory in Firefox Labs similarly follows a clear pattern — incubation through Labs typically precedes default-on promotion once telemetry shows acceptable compatibility rates across the web and no significant regressions.

For the ESR track, organizations now have the standard ESR validation window to test Firefox 153's Vulkan Video integration in their specific environments — evaluating whether their Linux distributions, Vulkan driver versions, and GPU configurations produce the expected hardware-accelerated decode behavior before broad fleet deployment.

The broader platform context favors Mozilla's direction here. The wider browser and graphics ecosystem continues to consolidate around Vulkan as a cross-platform GPU primitive, with adoption extending across Linux, Android, and ChromeOS. Firefox's Vulkan Video investment keeps it aligned with where platform-level GPU access is heading rather than doubling down on a Linux-specific API in potential long-term decline. Combined with the pace of graphics and media investment visible across recent Firefox releases, the next several monthly releases are positioned to deliver meaningful maturation of both Vulkan Video decode and JPEG-XL — moving them from carefully flagged experimental features toward fully supported, default-on capabilities that benefit the entire Firefox user base.