SORTMYFILE GUIDE

Chrome Adds JPEG XL: What It Means for Image Conversion

Chrome 155 now decodes JPEG XL. Learn what .jxl changes, where browser support still differs, and how to convert supported images for everyday sharing.

JPEG XL has taken a meaningful step toward mainstream browser support. On 6 October 2026, Chrome for Developers announced that Chrome 155 would ship built-in decoding for .jxl images. That matters to photographers, designers and anyone who receives modern image files but still needs to share them with older software or upload portals. The important distinction is that Chrome is adding decoding support: this does not mean every browser, image editor or upload form can read JPEG XL, and it does not mean every converter can export it. This guide explains the format, the new browser change and a practical way to convert or compress images without losing track of compatibility.

Key takeaways

  • Chrome 155 adds JPEG XL decoding, but decoding support is not the same as encoding or full editing support.
  • Browser and application support can differ, so confirm that the recipient accepts JXL before sharing it.
  • Convert only when another format is required, then inspect the exported image for quality and dimensions.

What changed when Chrome 155 added JPEG XL decoding?

Google announced on 6 October 2026 that Chrome 155 would ship decoding support for JPEG XL. Chrome describes JXL as a next-generation image format and says it can offer substantially better compression than JPEG in some comparisons, alongside lossless compression, built-in HDR support and lossless JPEG transcoding. Those are format capabilities, not a promise that every image will be 30–50% smaller. Results depend on the source image, quality target, encoder settings and whether the comparison is lossless or lossy. The browser change means a supported Chrome build can display JXL images natively; it does not automatically add JXL export to every website or image editor.

Why photographers and web publishers are watching JPEG XL

JPEG XL is designed for high-quality photographic images and modern display requirements. It supports both lossy and lossless compression, high bit depths, wide colour gamuts, HDR, transparency and animation. It can also losslessly transcode an existing JPEG so that the original JPEG data can be reconstructed later. That last capability is useful for archival and migration workflows because it is different from opening a JPEG and saving a newly compressed copy. JXL is not automatically the best choice for every upload: a portal may only accept JPEG or PNG, a social platform may recompress the file, and an older browser may not display it. Choose a format based on the destination as well as file size.

Decoding, encoding and editing are three different capabilities

A browser that can decode JXL can display a .jxl file. That does not prove that the browser can encode a new JXL file from a canvas, nor that an image editor can preserve every JXL feature when editing and saving. This distinction matters when a website says it “supports JPEG XL”. Check whether it means upload, preview, conversion, export or all four. SortMyFile’s current Image Converter offers JPG, PNG, WebP and AVIF output. JXL input is dependent on the browser’s native decoder and is not advertised as a universal workflow; JXL output is not currently offered. If a JXL file does not preview in your browser, do not assume the converter can read it.

JPEG XL browser support is improving, but it is not universal

As of October 2026, compatibility still varies by browser and version. Chrome 155 added default decoding support on 6 October, and Firefox 158 enabled it by default on 13 October. Safari has supported JPEG XL since version 17, but its support is partial: it does not provide the same animation and progressive-loading capabilities as the newer Chrome and Firefox implementations. Do not assume every Chromium-based browser follows Chrome; Microsoft Edge support differs, and other derivatives can ship on different schedules. Mobile WebViews, older managed devices and enterprise browser builds can also lag behind desktop releases. If a file is important, test it in the exact browser and device that will receive or upload it. For websites that publish JXL images, provide a fallback such as AVIF, WebP or JPEG.

When should you keep JXL and when should you convert it?

Keep the original JXL when you need its lossless properties, HDR information, transparency or archival characteristics and your workflow supports it. Convert a copy when a receiving portal specifies JPEG or PNG, a recipient uses older software, or an application rejects .jxl. JPEG is a practical compatibility choice for photographs; PNG is useful when lossless output or transparency matters; WebP and AVIF can be efficient web formats where the destination accepts them. Do not repeatedly convert a lossy image between formats: each lossy export can introduce another generation of quality loss. Keep the original file and compare the exported copy at the size it will actually be viewed or printed.

How to convert a supported image with SortMyFile

For JPG, PNG, WebP and AVIF workflows, open the Image Converter, select the source image, choose the output format and download the result. Supported formats and previews can vary by browser. If you are testing a JXL source, first confirm that your browser can display it and then check whether the tool successfully creates a preview; a failed preview means you should use a JXL-capable desktop application or another verified converter. Do not share confidential images with an unfamiliar conversion website simply because it claims broad format support.

  • Keep an untouched copy of the original image.
  • Open SortMyFile Image Converter and select a supported image.
  • Choose JPG, PNG, WebP or AVIF as the output format.
  • Download the converted copy and open it before sharing.
  • Check dimensions, transparency, colour appearance and file size.

Reduce image size after conversion without guessing

Conversion changes the file format; compression changes how much data the image uses. They are related but not identical jobs. If an upload form specifies a maximum KB size, start with the Image Compressor or a target-size workflow and use the least aggressive setting that meets the requirement. Check small text, edges, skin tones, gradients and transparency after compression. A smaller file is not automatically a better file if a signature becomes unreadable or a photograph loses important detail. Keep the original and compare both file size and visual quality before submitting.

A practical checklist before sending a modern image format

Confirm the destination’s accepted formats rather than relying on the recipient’s browser. Check whether the image contains transparency or HDR that might change during conversion. Keep the source file, use a descriptive filename, verify the final pixel dimensions and open the downloaded copy. For a portal with a strict KB limit, check the actual output size after download. If a browser cannot preview JXL, switch to a verified JXL-aware application before converting; renaming .jxl to .jpg does not change the underlying encoding.

Sources & further reading

Primary references used for the guidance above. Check the source itself for the latest requirements.

Put the guide into practice

Open the related tool when it fits your task, and check its supported formats and limitations before downloading or submitting a file.

Frequently asked questions

Does Chrome support JPEG XL now?

Chrome 155 added built-in JPEG XL decoding, announced by Chrome for Developers on 6 October 2026. Older Chrome versions may not have the same support.

Is JPEG XL always smaller than JPEG?

No. Google describes better compression as a general format advantage. Actual results depend on the image, encoder and quality settings.

Can SortMyFile convert JXL to JPG?

The Image Converter exports JPG, PNG, WebP and AVIF. JXL input depends on whether your browser can decode the file, so it is not a guaranteed cross-browser workflow.

Does JPEG XL replace JPEG and PNG?

Not for every workflow. Browser support and upload requirements still vary. Keep a compatible fallback when sharing images widely.

Is renaming a .jxl file to .jpg enough?

No. Renaming changes the filename, not the encoded image format. Use a real image decoder and converter.