Glitchy JXL fullscreen view

(#3516) Bug Closed: Fixed Priority: P2 desktop

Reproduction steps

  1. Download the attached jxl file
  2. Upload it somewhere
  3. Click on the preview to view it in full-screen view

Observed behaviour

It looks like a car drowned in rainbows! This might just be an electron bug btw

Build information

Stable Desktop 2026.1004.13532, Web 2026.1005.184841, Linux 7.2.5-200.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

Linux

Evidence

Details

Expected behaviour It should look like a car.
  1. Hampus changed the status from Confirmed to Fix pending
  2. Fullest changed the status from Awaiting confirmation to Fixed
  1. The pull request fluxer#3446 mentions this post Merged

7 comments

Sign in with Fluxer to comment and vote.
Comment by roufang
roufangReviewer 1 vote
Status changed from Needs triage to Confirmed
CR: Stable Desktop 2026.1006.171735, Web 2026.1007.140750, Linux 7.2.7-ogc1.1.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US
Comment by Rex
RexSystem 1 vote
Status changed from Fix pending to Awaiting confirmation
Fixed in media proxy 2026.1013.32826, which is live now. Large images in the fullscreen viewer could be stitched together from pieces made by different servers, which broke them from some point down. Please check an image that was broken before.
Comment by ternera
terneraMod 1 vote
Can reproduce CR - Stable Desktop 2026.1004.13532, Web 2026.1006.1600, macOS 27.0.1 (arm64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US
Comment by cloud
cloud 1 vote edited 2 replies
I posted that image some time ago, but want to expand on this now that I found the report and found out some more details. What's interesting is that I remember being able to send these larger JXLs in my small personal notes and private guild without this corrupted/glitched/artifacted preview. The embed was always normal, but clicking to view it would show a corrupted preview in a large public one. Testing this again shows that the corruption is present everywhere, unless I sent smaller ones that were not affected and mixed that up with larger images. But something I noticed is that the compression level/size can affect how the corruption looks, though not always. I uploaded a 1440p Minecraft screenshot at distance 1.0 and distance 0.8 to personal notes (lower is higher quality, larger) and more of the image was normal on the distance 1 version compared to 0.8. I originally sent those as a size comparison with the PNG in a public guild before writing this and both had the same behavior. However, I uploaded those two later (so a third time) and the amount of corruption is the same. To add to the variance of this behavior, I uploaded the more compressed version of that car photo (Subaru for reference as I will post more) to personal notes again while typing this up and it behaves normally like a PNG. I uploaded it to a public guild and it is corrupted, but less than the slightly larger one Fullest attached. In that larger one, the corruption starts at the top of the car and in the smaller one, the corruption starts a little under halfway through the image. Another thing is that small JXL file sizes are not affected. That image Fullest attached was upscaled from 1080p and the original looks completely normal as if it was a PNG or something else. Small screenshots that I take of things on the desktop also behave normally. I also found out later while typing again that the threshold for the JXL to not corrupt in personal notes is around 600 KB or so, and just over 400 KB for if posted in a public guild. Hopefully what I explain is not confusing; I will attach many examples to test in different resolutions, compression levels and sizes, though really the main thing affecting this is the actual size itself and not resolution/compression since the same 1080p image with distance 0.4 won't corrupt in public but 0.3 will, and the distance numbers to "pass" this size threshold would be higher for larger images. It's based on file size. Reproducible on current desktop Canary and Stable, Web on Firefox and Chromium, and different mobile builds but not when you open the fluxerusercontent CDN link in the browser, suggesting that maybe the issue lies in the app itself. On mobile, both the the preview and embed are corrupted. If on Firefox, make sure JXL is enabled if not on 158 yet so you'll be able to view the image link in the new tab and not get immediately prompted to download. All builds tested (including other people's):
  • Version 2026.10.100, Beta 5, Channel Beta, Build 666, Android 17 (arm64), Device Google Pixel 9 Pro XL, Locale en-US, Push fcm, Flutter 3.47.7, Dart 3.13.5
  • Version 2026.10.100, Beta 5, Channel Beta, Build 2666, Android 17 (arm64), Device Google Pixel 10a, Locale en-FI, Push fcm, Flutter 3.47.7, Dart 3.13.5
  • Version 2026.10.100, Beta 5, Channel Beta, Build 2667, Android 17 (arm64), Device Google Pixel 11 Pro Fold, Locale en-US, Push unifiedpush, Flutter 3.47.7, Dart 3.13.5
  • Canary Desktop 2026.1012.154032, Web 2026.1012.194217, Linux 7.2.9-200.nobara.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US
  • Canary Web 2026.1012.220013, Linux (x64), Firefox 157.0, Locale en-US
  • Canary Web 2026.1012.220013, Linux (x86), Chrome 155.0.0.0, Locale en-US
Comment by cloud
cloud 1 vote 1 reply
Additional attachments:
Comment by cloud
cloud 1 vote
Images to test out yourself: