A new image format can make a web page lighter without making its photographs look obviously worse. It does not automatically make every upload form, PDF converter or recipient's device understand that format. Chrome's latest JPEG XL change is useful, but document teams still need a compatibility handoff.
What Chrome released
On 6 October 2026, the Chrome team announced that JPEG XL decoding is shipping from Chrome 155. Google says the format can offer 30–50% better compression than JPEG, alongside lossless compression, HDR, progressive decoding and lossless transcoding of existing JPEG images.
Chrome uses `jxl-rs`, a decoder written in Rust. The team says it chose a memory-safe implementation because image decoders process complex, untrusted files inside the browser. It also reports using fuzzing, code review and performance work to harden and speed up the implementation. That is a browser-decoding improvement, not a promise that every document application can import or export `.jxl` files.
Why this matters for documents
Photographs, scans and diagrams often dominate a PDF's file size. JPEG XL may become a useful source or web-delivery format for high-fidelity images, especially when teams want lossless storage, HDR or progressive loading. But the image that works in a current Chrome tab may still fail in an older browser, a form upload, an email preview or a PDF creation tool.
Use this practical workflow when a JPEG XL image must become part of a document:
1. Keep the original. Preserve the `.jxl` file and its source details before making delivery copies. Do not rename the extension to `.jpg`; a new filename does not change the encoded format. 2. Test the receiving workflow. Open the image in the exact browser or application your team supports. If a portal publishes an accepted-format list, follow it rather than assuming browser support is enough. 3. Export a compatible copy. When the final PDF tool expects JPG, PNG or WebP, create that copy with an image editor that explicitly decodes JPEG XL. Check dimensions, colour, transparency and the smallest details after conversion. 4. Inspect the final PDF. Reopen the exported PDF and compare it with the approved image. Check cropping, orientation, page margins and any colour shift. Record which copy was actually delivered.
Important limits
Chrome's announcement recommends testing both AVIF and JPEG XL instead of treating one format as a universal winner. Compression results depend on the image and quality target. HDR, wide colour, metadata, animation or progressive behaviour may also be flattened or lost when an image becomes an ordinary PDF page.
Browser decoding is not the same as safe-content validation, accessibility review or archival suitability. Alternative text and document structure still need to be handled in the authoring workflow; a sharper image alone does not make a PDF accessible.
FileStation currently documents JPG, PNG, BMP, GIF and WebP for Images to PDF, so prepare a supported copy before using that tool. Then open the result in PDF Reader for a page-by-page check. Keep the JPEG XL source beside the reviewed PDF rather than assuming the conversion preserved every property.
Primary sources: Chrome for Developers: Shipping JPEG XL in Chrome, 6 October 2026 and Chrome 155 beta notes.