# JPEG XL support with new Microsoft WIC codec

**URL:** https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787
**Category:** Help & Support
**Tags:** feature-request
**Created:** [March 4, 2025, 3:11pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787 "2025-03-04T15:11:35Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![what](https://resource.dopus.com/letter_avatar_proxy/v4/letter/w/5f9b8f/32.png) [@what](https://resource.dopus.com/u/what)
#### Post date: [March 4, 2025, 3:11pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/1 "2025-03-04T15:11:35Z")

</div>

Recently Microsoft released a [new plugin](https://apps.microsoft.com/detail/9mzprth5c0tb) to add .jxl support to Windows, similar to the ones mentioned in [this](https://resource.dopus.com/t/how-to-enable-fix-playback-of-various-media-formats-in-opus/1974#h-1-codecs-provided-by-microsoft-3) FAQ entry.

Currently with the plugin installed:

- thumbnails are generated
- preview pane works, although it is quite slow for some reason, the whole pane goes completely dark for a second and then the image loads
- DOpus viewer cannot handle the format

As far as I understand this new codec would fall within the current "Windows Imaging Component" Viewer Plugin present in DOpus and I was wondering if full JPEG XL support could be added to the program this way.

Thanks!

---

<div class="post-metadata">

### Author: ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [March 4, 2025, 5:50pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/2 "2025-03-04T17:50:38Z")

</div>

We should be able to add it to the WIC plugin if the new codec works OK.

The preview pane taking a long time to display the image suggests it might not work OK, though. 🙂 It'll probably be coming via the shell thumbnailer in that case (the same one thumbnails in Opus and File Explorer use), which likely calls the same codec.

---

<div class="post-metadata">

### Author: ![what](https://resource.dopus.com/letter_avatar_proxy/v4/letter/w/5f9b8f/32.png) [@what](https://resource.dopus.com/u/what)
#### Post date: [March 4, 2025, 6:40pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/3 "2025-03-04T18:40:07Z")

</div>

> [@Leo](#):
>
> It'll probably be coming via the shell thumbnailer in that case

Seems so  
 ![image](https://resource.dopus.com/uploads/default/original/3X/0/e/0eacf3cfd6b83ee848eb5e3ed46983fafc491a55.png)

Looking forward to future updates!

---

<div class="post-metadata">

### Author: ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [March 5, 2025, 11:32am UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/4 "2025-03-05T11:32:33Z")

</div>

For some ridiculous reason that codec requires Windows 11.

---

<div class="post-metadata">

### Author: ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [December 3, 2025, 10:35am UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/5 "2025-12-03T10:35:15Z")

</div>

We've added support for this in the next beta.

---

<div class="post-metadata">

### Author: ![Konrad\_Klar](https://resource.dopus.com/user_avatar/resource.dopus.com/konrad_klar/32/26344_2.png) [@Konrad\_Klar](https://resource.dopus.com/u/Konrad_Klar)
#### Post date: [December 3, 2025, 10:23pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/6 "2025-12-03T22:23:05Z")

</div>

> [@Leo](#):
>
> We should be able to add it to the WIC plugin if the new codec works OK.

Does it mean that each time a new WIC codec appears the DOpus WIC plugin needs to be updated? In other words: the DOpus WIC plugin knows particular WIC codecs by name and does not support other WIC codecs?

---

<div class="post-metadata">

### Author: ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [December 3, 2025, 11:40pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/7 "2025-12-03T23:40:09Z")

</div>

Yes, it needs to know which codec to use for which extension.

---

<div class="post-metadata">

### Author: ![Morbid](https://resource.dopus.com/letter_avatar_proxy/v4/letter/m/f475e1/32.png) [@Morbid](https://resource.dopus.com/u/Morbid)
#### Post date: [December 4, 2025, 5:56pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/8 "2025-12-04T17:56:23Z")

</div>

Any downsides to use this WIC plugin and extension combo in DOpus? Can it be slow or be resource hog if i have a lot of files inside my folders and convert them to JPEG XL and then showing them as thumbnails in DOpus?

---

<div class="post-metadata">

### Author: ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [December 4, 2025, 11:54pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/9 "2025-12-04T23:54:46Z")

</div>

I don't know, sorry.

I wouldn't convert anything to JXL myself if it's already in another format. No reason to for most people/situations as the best you can hope for is saving a small amount of space per image.

---

<div class="post-metadata">

### Author: ![travibe](https://resource.dopus.com/user_avatar/resource.dopus.com/travibe/32/32530_2.png) [@travibe](https://resource.dopus.com/u/travibe)
#### Post date: [January 28, 2026, 3:47pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/10 "2026-01-28T15:47:05Z")

</div>

i just saw in the beta released the new functionality with this extension. This is strictly Windows 11 correct? I'm still running 10 and I cant install that windows app you linked to.

---

<div class="post-metadata">

### Author: ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [January 28, 2026, 4:13pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/11 "2026-01-28T16:13:27Z")

</div>

As far as I know, yes; Microsoft only released it for Windows 11.

---

<div class="post-metadata">

### Author: ![Morbid](https://resource.dopus.com/letter_avatar_proxy/v4/letter/m/f475e1/32.png) [@Morbid](https://resource.dopus.com/u/Morbid)
#### Post date: [January 28, 2026, 5:48pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/12 "2026-01-28T17:48:23Z")

</div>

> [@Leo](#):
>
> a small amount of space per image.

30-40% lossless gain (at level 7, level 10 lossless JPEG-XL is too slow and will get you just a little more over level 7) vs PNG which was already compressed to the maximum level (9) is not a small amount... At least to me. I think you may want to look at JPEG-XL more closely, as i think (perhaps wrongly) that you are somewhat not impressed by this format. 😄

---

<div class="post-metadata">

### Author: ![Leo](https://resource.dopus.com/user_avatar/resource.dopus.com/leo/32/69732_2.png) [@Leo](https://resource.dopus.com/u/Leo)
#### Post date: [January 28, 2026, 6:22pm UTC](https://resource.dopus.com/t/jpeg-xl-support-with-new-microsoft-wic-codec/54787/13 "2026-01-28T18:22:32Z")

</div>

Still images are already such a small percentage of my data that making them smaller doesn't change much for me.

I can see how it can be useful for work that needs to store huge amounts of high-res lossless images. It has uses, for sure, but I don't see it as something the general public desperately needed, in terms of file sizes.

Anyway, you can view this format in Opus now, at least on Win11. 🙂 You can even convert images into if you set up a converter via **Preferences / Miscellaneous / External Tools**.
