What Does Jpegli Offer? Technical Advantages and Google’s Reported Test Results

ProcrustesPR

Jpegli is a JPEG encoding library focused on improving image quality and compression efficiency while maintaining compatibility—not simply being “faster than JPEG.” According to Google documentation summarized by welly.tw in April 2024, Jpegli’s encoding speed is comparable to libjpeg-turbo and MozJPEG. Tests cited in the article showed higher ELO ratings for Jpegli, and the article reported that it could compress high-quality images 35% more than traditional JPEG codecs. These are the article’s reported results, not a guarantee of the same improvement for every image.

ProcrustesPRProcrustesPRHow Should a CMS Handle Images? From Upload Optimization to Descriptions and URL Management

Maintaining JPEG compatibility while improving image quality and compression efficiency

Using Jpegli does not require switching to a different image format. welly.tw describes it as an encoder and decoder that complies with the original JPEG standard and its conventional 8-bit form. Its API/ABI is also compatible with libjpeg-turbo and MozJPEG. Its technical features include:

  • Image quality: More precise calculations that better preserve visual quality during compression or decompression can produce clearer images with fewer artifacts.
  • Compression efficiency: More efficient image compression can save storage space and bandwidth.
  • Encoding speed: While improving image quality and compression efficiency, its speed is comparable to libjpeg-turbo and MozJPEG. It has not been shown to be faster in every situation.

Support for 10 bits or more, but advanced features require code changes

According to welly.tw’s description, Jpegli can encode each image component using 10 bits or more, and the resulting images can still be viewed with 8-bit viewers. However, higher-precision encoding does not mean that every viewer can display the full higher bit depth.

These advanced features are available through API extensions and require application code changes to use. Compatibility with existing APIs/ABIs does not mean that advanced features can be used without modification.

Useful test results, but not universally applicable

The Google test screenshot shared by welly.tw shows higher ELO ratings for Jpegli than for libjpeg-turbo and MozJPEG. The article also cited Google documentation stating that Jpegli could compress high-quality images 35% more than traditional JPEG codecs. One result compares ratings; the other describes compression performance. Neither measures an increase in encoding speed.

The summary does not include the complete test image set, encoding settings, versions, or scoring procedure. These details are insufficient to reproduce the comparison, and you should not expect 35% more compression every time. Likewise, adopting Jpegli does not imply that an entire website will load 35% faster. That figure describes compression performance for high-quality images, not the results of a website speed test.

ProcrustesPRProcrustesPRHow should images of different sizes on the same website be named?

Jpegli: perspectives from across the web

How should you compare results to determine whether Jpegli is suitable for your images?

Test the images you actually intend to process. Compare output file sizes and check whether the image quality meets your needs before deciding whether to adopt Jpegli. The tests summarized by welly.tw do not include a complete list of images, versions, and encoding settings. They can guide further testing, but you should not assume that your images will produce the same results.

Can you assume that adopting Jpegli will make your website faster?

No. More efficient image compression may reduce the amount of data transferred, but welly.tw’s summary provides no before-and-after website loading tests. If your goal is to improve page speed, you still need to compare results using actual pages and images. Image compression results cannot be directly converted into a speed improvement for an entire website.

What integration requirements should you assess for an existing JPEG workflow?

Check two things: whether your existing encoding, decoding, and viewing workflows work correctly, and whether you need higher-bit-depth features. Interface compatibility does not mean advanced features are ready to use without code changes. If you need them, assess what application changes and testing will be required.

ProcrustesPRHow many image variants should you prepare, and how should you manage them?

References

  1. Google 新的 Jpeg 編碼函式庫-Jpegli 介紹welly.tw · 2024-04-26T08:44:38.219Z — Discusses: How should you compare results to determine whether Jpegli is suitable for your images?; Can you assume that adopting Jpegli will make your website faster?

Related articles

How Should a CMS Handle Images? From Upload Optimization to Descriptions and URL ManagementHow should images of different sizes on the same website be named?How many image variants should you prepare, and how should you manage them?How do visual and short-form video trends in search results affect SEO?How can photography websites use SEO to increase visibility and attract clients?How can service and e-commerce websites improve search visibility? Start by distinguishing local needs from buying intentWhy optimize a website, and which tasks can be done for free?How can you use search results page features to attract traffic?
ProcrustesPR
ProcrustesPR