Mozilla shipped Firefox 153 in July 2026, and for the first time, the browser natively passes through high-dynamic-range video signals on Windows 10 and Windows 11. It’s a long-overdue fix that erases one of the most stubborn feature gaps between Firefox and its Chromium-based rivals. But early adopters will encounter a bumpy road: missing tone mapping, a known memory leak, and GPU-specific quirks mean the rollout is less a polished finale and more a working beta.
The HDR Pipeline, Finally Wired Up
Firefox can now detect when a video stream uses BT.2100 PQ (the foundation of HDR10) or BT.2100 HLG, preserve the associated brightness and color metadata, and hand it off to the Windows display stack. No hidden flags, no about:config switches — as long as you’ve switched on HDR in Windows Settings, the browser automatically requests the highest-quality stream that a service offers.
Until now, Firefox would forcibly down-sample HDR video into standard dynamic range. The result was a flat, washed-out picture that stripped away the specular highlights and deep shadows that make HDR content pop. The new behavior works with VP9, AV1, and, on systems that support it, HEVC-encoded streams, though codec availability still depends on your Windows edition (N and KN releases may need additional media packs) and your GPU’s hardware decoding capabilities.
Behind the scenes, the feature didn’t land fully formed in a single update. Mozilla’s bug tracker shows that core pieces — color-space recognition, metadata plumbing, and hardware overlay paths — were merged during the Firefox 151 and 152 development cycles. Firefox 153 is simply the first release where the feature is enabled broadly enough that everyday users will encounter it. That distinction matters: if you’re troubleshooting on Firefox 152, you may already have partial support; if you’re on 153 and something breaks, the cause could be a regression introduced alongside the current batch of fixes.
What HDR Playback Means for Your Daily Browsing
Home Users and Casual Streamers
The biggest practical win is that you no longer need to launch Edge or Chrome just to watch a YouTube HDR trailer or a Netflix show in its full glory. If you prefer Firefox for its privacy controls, container tabs, or independent engine, you can now stick with it for entertainment, too.
Don’t expect every “HDR” badge to deliver a dramatic improvement. Many budget monitors and laptops slap an HDR label on panels that can barely exceed standard brightness, lack local dimming, or cover only a fraction of the wide color gamut. On those screens, Firefox’s output may look only marginally different from SDR — and if Windows HDR mode makes the desktop look washed out, the display itself is the culprit, not the browser.
Content Creators and Video Professionals
For video editors, color graders, and motion designers who review work through web links, Firefox’s HDR pass-through is a step up from forced SDR. It means a graded timeline shared via Frame.io or Vimeo will look closer to what was intended, assuming both ends use calibrated HDR hardware.
But treat it as a quick-look tool, not a reference monitor. The initial release deliberately omits browser-level tone mapping. If your monitor can’t hit the luminance peaks of the source material, ultra-bright highlights may blow out to pure white rather than being gracefully compressed. Mozilla has acknowledged this and says a display-aware tone mapping slider is under development for a future point release. In the meantime, checking grades in a dedicated app with color management remains essential.
IT Administrators and Enterprise Environments
Managed deployments can enable the feature without group policy gymnastics — it’s on by default. The main concerns are stability and driver consistency. A memory leak linked to HDR playback has already surfaced in the Firefox 153 bug tracker, so machines that run the browser for extended periods or keep multiple video tabs open may need closer monitoring. Pushing the latest GPU drivers (from AMD, Intel, or NVIDIA) and keeping Windows up to date will be the first line of defense. Also note that Firefox’s HDR path requires hardware acceleration to be enabled; environments that disable it for compatibility reasons will see no HDR benefit.
How We Got Here: A Gap Years in the Making
Chromium-based browsers have supported HDR video on Windows for several years, thanks to deep platform integration and Google’s investment in the media stack. Firefox, with its own Gecko engine, had to build an equivalent pipeline from scratch.
Mozilla’s media team began landing HDR foundations in the Firefox 151 nightly builds, with wider testing in 152. The work involved teaching the browser to parse HDR metadata from MP4, WebM, and other containers; routing it through Windows Media Foundation and DirectX; and handling fallbacks when a GPU driver couldn’t process a particular transfer function. By Firefox 153, enough of the plumbing was stable to flip the switch for the release channel.
That timing coincides with broader industry shifts. Streaming platforms increasingly default to HDR delivery for premium content, and even mid-range PC hardware now ships with displays that can accept an HDR signal. For Mozilla, staying competitive on media quality wasn’t just a feature request — it was table stakes for keeping Firefox relevant among power users.
What to Do Right Now: A Hands-On Checklist
Before you judge Firefox’s HDR performance, run through these steps:
- Update Firefox to the latest 153 release or later (check in Menu > Help > About Firefox).
- Enable Windows HDR: Go to Settings > System > Display, select your HDR-capable screen, and turn on “Use HDR.” If the toggle is missing, update your GPU driver.
- Stay on current drivers: Get WHQL-certified drivers directly from NVIDIA, AMD, or Intel — don’t rely on the ones Windows Update provides.
- Confirm your display is truly HDR-capable: Look for DisplayHDR certification (at least 400) or check the specs for peak brightness above 400 nits and 90% DCI-P3 coverage. Ignore marketing terms like “HDR-ready” or “HDR effect.”
- Keep hardware acceleration on: In Firefox, go to Settings > General > Performance and make sure “Use recommended performance settings” is checked. If you must disable acceleration for other reasons, expect HDR to stop working.
- Test multiple sources: Try a YouTube HDR test video, a Netflix HDR title (with the premium plan), and a local HDR file if possible. Inconsistencies between services often point to DRM or codec quirks, not a Firefox bug.
- Note the video format: If you encounter issues, check whether the stream is PQ or HLG. HLG may fail on some Intel integrated GPUs due to driver limitations; in those cases, Firefox will fall back to wide-gamut SDR. AMD and NVIDIA systems generally handle both formats.
- Don’t trust screenshots: A screenshot taken in HDR mode will look wrong on an SDR panel. Judge playback by eye on the actual display.
- Restart Firefox after changing any HDR or driver settings — the media pipeline may not pick up changes on the fly.
Known Issues and Red Flags
Memory leak: Mozilla’s tracker has logged a leak tied to HDR video sessions. If you notice Firefox’s RAM usage climbing during extended playback, restart the browser. A fix is likely to arrive in a point release.
Extreme color errors: On rare configurations (especially when software WebRender is forced), video can turn magenta and white — a sign that a color conversion has failed. Keep hardware acceleration enabled to avoid this.
Missing tone mapping: Without browser-level tone mapping, bright specular details on a display with limited luminance may look blown out. For example, a sunset might appear as a solid white blob instead of showing cloud detail. Microsoft Edge and Chrome use their own tone mappers, so the same video may look better there. Until Mozilla ships its tone mapping control, the only workaround is to use a higher-quality HDR monitor that can reproduce the content’s peak brightness directly.
HEVC support: If a streaming site uses HEVC for HDR delivery, Windows must have the appropriate codec. Some systems come with it preinstalled; clean Windows installations or N/KN editions may need the “HEVC Video Extensions” package from the Microsoft Store (a paid add-on for many users).
Smartphone orientation glitches: A few HDR clips recorded in portrait or unusual orientations may still trigger playback errors. This is a known corner case that Mozilla is tracking.
What’s Next for Firefox HDR
Mozilla isn’t treating HDR as done and dusted. Public comments from developers and the bug tracker point to a rapid sequence of improvements:
- Firefox 153.0.1 is expected to integrate HDR diagnostics directly into
about:support, letting you see at a glance whether your display, GPU, and Windows config are HDR-ready. - Display-aware tone mapping with a user-facing toggle is in active development. Once shipped, it will let you choose between a pass-through approach (today’s behavior) and a profile that adapts scene brightness to your screen’s limits, similar to what’s common in media players.
- Broader GPU compatibility work continues, particularly for Intel’s HLG handling and for Qualcomm Snapdragon X Elite systems running Windows on Arm.
Firefox’s HDR journey is a classic open-source success story: years of catch-up compressed into a few version cycles, with the community and the media team finally delivering a feature that was starting to feel like a permanent omission. It’s imperfect, it demands a decent display and a bit of patience, but for Windows users who want to stay in Firefox without sacrificing modern video quality, the foundation is finally in place.