The discussion revolves around the auto-conversion of image uploads to JPG in Discourse. MarcP started the conversation, highlighting the issue with images having transparent elements and dark/light mode being affected by the conversion.
MarcP tried uploading images in webp and png formats, but they were still converted to jpg. piffy suggested turning off compression in the settings to prevent the conversion.
mattdm listed three relevant settings: recompress original jpg quality, png to jpg quality, and composer media optimization image encode quality. However, the interrelation between these settings and their impact on different file types is unclear.
Falco explained that the last setting relates to a blog post about using Rust, WebAssembly, and MozJPEG for faster and smaller uploads, which is separate from the server-side image optimization pipeline.
mattdm rephrased the concerns, highlighting the need to balance page load time, server-side storage, server load, upload speed, and image quality. JammyDodger mentioned a GitHub pull request that addresses the inconsistent use of JPEG and JPG.
sam clarified that the first two settings are server-side changes, while the last one is applied in the browser, reducing the payload sent to the server.
I have noticed that some image uploads always convert to jpeg, this creates ugly situations with images with transparent elements and dark/light mode. I couldn’t find a setting for this, can we somehow turn this off?
I’ve tried uploading an image in webp, png and it always converts it to jpg, how so?
I’ve had this issue. I believe if you turn the compression off in the settings, it will upload properly. Not an idea place to leave that setting though for obvious reason
There are several settings which seem relevant:
recompress original jpg quality (“Quality of uploaded image files (1 is lowest quality, 99 is best quality, 100 to disable).”)png to jpg quality (“Quality of the converted JPG file (1 is lowest quality, 99 is best quality, 100 to disable).”)composer media optimization image encode quality (“JPEG encode quality used in the re-encode process.”)I am not sure how the last one relates to the first two — or what happens to webp or other file types that aren’t PNG or JPEG.
(Also, note for any Discourse UX people reading this: inconsistent use of JPEG and JPG makes this harder to find.)
Last one is about Faster (and smaller) uploads in Discourse with Rust, WebAssembly and MozJPEG | Blog while the first two are about a server-side image optimization pipeline, so while both are about images they aren’t about the same feature.
Let me rephrase.
I can see several separate concerns:
… and I am unclear on how exactly the available settings impact these, especially with that new feature.
First 2 are server side only changes. (that can run regardless of client side support)
Last one is applied in the browser and means that you end up sending smaller payloads to the server.
