Firefox 158 Enables JPEG XL: What Creators Need to Know
Mozilla has officially launched Firefox 158, bringing a major milestone for modern web media. After months of testing memory-safe decoding, the browser now enables JPEG XL support by default for everyday browsing. This release also introduces useful PDF accessibility upgrades and a smarter autofill system that helps you work faster online.
For photographers, site owners, and digital artists, image delivery has always been a delicate compromise between picture quality and file weight. Formats like WebP and AVIF made noticeable strides, but JPEG XL is built with the explicit goal of being a long-term, universal replacement for traditional raster graphics. Understanding where this format shines helps you decide how and when to incorporate it into your publishing workflow.
What Arrives in Firefox 158
The headline addition in Firefox 158 is the default activation of JPEG XL decoding. Mozilla had previously kept optional support inside Nightly builds, citing concerns in 2024 about the size and complexity of the original C++ reference decoder. To avoid increasing the browser's attack surface, Mozilla endorsed an effort by Google Research to develop a memory-safe decoder written in Rust. That memory-safe implementation replaced the reference decoder in January 2026, leading up to Firefox 158 turning on default viewing capabilities for all users.
Beyond image decoding, Firefox 158 improves how the browser handles documents and daily browsing tasks. When you save a webpage as a PDF or print documents on macOS and Linux, the browser generates more accessible files and resolves earlier rendering bugs, such as missing mathematical symbols. The update also rolls out a Smart Window tool that suggests form entries based on open tabs and saved data, fixes high-contrast menu readability in Windows, and removes scroll position rounding for smoother page movement on high-resolution screens.
Understanding the Strengths of JPEG XL
JPEG XL (often shortened to JXL) is an open, royalty-free standard standardized under ISO/IEC 18181. Developed by the Joint Photographic Experts Group alongside contributors from Google and Cloudinary, it is engineered to overcome the limits of legacy formats. The specification called for a 60 percent improvement in compression efficiency compared to standard JPEG, while aiming to outperform formats like HEIC, AVIF, and WebP for still images.
Unlike older choices where you had to pick between lossy compression or lossless clarity, JPEG XL natively handles both. It features a lossy system called VarDCT, which enhances block-based transform coding, as well as a modular mode suited for lossless compression and unique data arrangements. It supports progressive decoding, HDR imagery, wide color gamuts, transparency, and animated sequences, all within the same specification.
Lossless Precision Versus Legacy Files
For decades, designers relied on PNG whenever lossless fidelity or alpha transparency was mandatory. However, uncompressed or losslessly compressed PNG files can be massive, especially on multi-density displays where a 2x screen quadruples the total pixel count. JPEG XL modular mode provides a modern lossless path that retains full image detail while keeping file sizes significantly lower than older PNG archives.
Browser Support and the Fallback Strategy
Firefox 158 joining the default support list is a massive boost for JPEG XL, but cross-platform adoption is still developing across the broader web landscape. Apple added native support across Safari 17, iOS 17, and macOS Sonoma, while iPhone 16 Pro models use JPEG XL compression when capturing ProRAW photos. Google made JPEG XL generally available in Chrome 155, and Windows 11 added support through an extension in the Microsoft Store.
Because not every legacy visitor runs an updated browser, publishing guides from Mozilla and web performance documentation recommend using fallback approaches. The HTML <picture> element allows you to serve cutting-edge formats to compatible browsers while delivering dependable backups to older software:
<picture>
<source srcset="sample.jxl" type="image/jxl">
<source srcset="sample.avif" type="image/avif">
<source srcset="sample.webp" type="image/webp">
<img src="sample.jpg" alt="A clear visual description" loading="lazy">
</picture>By layering your media declarations like this, visitors using Firefox 158 or Safari get the benefit of lower data consumption and HDR fidelity, while legacy clients quietly receive a standard JPEG or WebP file without breaking the layout.
Optimizing Your Image Pipeline Right Now
While browsers continue rolling out wider native integration, you do not need to pause your optimization efforts. You can reduce bandwidth right now by auditing your current media assets and converting legacy photographs into lightweight modern formats. Follow these four steps to clean up your visual assets directly on your device without compromising client privacy:
- Review your website media library and look for oversized PNG or uncompressed JPEG files that slow down initial page loads.
- Open our private Image Format Converter to transform heavy graphics into efficient WebP or AVIF files, giving your readers immediate performance gains across all major browsers.
- Run your converted assets through the in-browser Image Compressor to trim remaining bytes without degrading visible image quality.
- If your projects involve downloadable printables, presentation slides, or portfolio proofs, organize them into clean documents with our client-side PDF Converter so your files download instantly and display properly across devices.
Everything in these steps runs entirely within your local browser sandbox. No pictures or personal files get sent to remote servers, giving you complete peace of mind while preparing assets for production.
Picking the Right Format for Every Project
No single file extension fits every creative project. Vector graphics like SVG remain the undisputed choice for logos, simple icons, and geometric artwork because they scale infinitely to any screen density without losing clarity. Similarly, text should almost always remain live HTML accompanied by web fonts rather than flattened pixels, ensuring it stays selectable, accessible, and searchable.
For complex scenes like portraits, product photography, and textured art, raster images remain essential. AVIF and WebP deliver excellent compression today with broad baseline support. With Firefox 158 enabling JPEG XL by default, creators gain a clearer path toward a future-proof standard capable of handling everything from high-bitrate studio RAW masters to fast, progressive web thumbnails.
Frequently asked questions
What makes JPEG XL different from older JPEG formats?
JPEG XL supports both lossy and lossless compression, progressive decoding, wide color gamuts, and high dynamic range. It was designed to achieve substantially better compression efficiency than legacy JPEG while offering advanced features like transparency and animation.
Does Firefox 158 require any setting changes to view JPEG XL?
No setting adjustments are needed. Mozilla has enabled JPEG XL decoding by default in Firefox 158, replacing earlier experimental flags with a memory-safe Rust decoder.
Should I replace all my website images with JPEG XL today?
You should not serve JPEG XL exclusively quite yet. Instead, use the HTML picture tag to deliver JPEG XL to supporting browsers like Firefox 158 and Chrome 155, while providing WebP or JPEG fallbacks for older devices.
What PDF improvements were added to Firefox 158?
Firefox 158 improves PDF accessibility when saving or printing pages on Linux and macOS. The release also resolves specific rendering problems, such as missing math symbols.
Sources
- Firefox (firefox.com)
- Image file type and format guide (developer.mozilla.org)
- Choose the right image format | Articles | web.dev (web.dev)
- JPEG XL - Wikipedia (en.wikipedia.org)
How we made this post: we researched the public sources listed above and drafted the article with the help of an AI writing tool (Google Gemini). Automatic checks look for copied wording, numbers that are not in the sources and broken links, but they cannot catch every mistake. Spotted a mistake? Tell us.