3 ms·
I work for a company that stores and displays images for customers, and converts them to various formats for them... CMYK JPEGs are the bane of my existence. A
by amiantos 5y ago
I work for a company that stores and displays images for customers, and converts them to various formats for them... CMYK JPEGs are the bane of my existence. A recent annoyance was a realization that they don't render consistently in different browsers, so some work I put into making sure that CMYK JPEGs always get CMYK JPEG thumbnails to keep colors consistent was basically a waste of time because the end-user can still see inconsistent color previews.
In the end the idea of a CMYK JPEG makes no sense to me, because if you're generating content specifically to print, especially if it contains vector-like content, why are you storing it in a lossy format? But, whatever, that is less annoying than people who ask for the ability to modify the DPI of an image to 72 for "web exports". I built it in instead of trying to explain to them that there's no need to turn a 300 dpi JPG into a 72 dpi JPG for use on social media.
I don't even want to get into the joy of CMYK SVGs with transparency, and trying to explain to customers that since JPG doesn't support transparency I have to use PNG for generated preview images, which necessitate a conversion to PNG, and SVG doesn't have any sort of color profile support, so converting them from CMYK to RGB is kind of just lucky dip.
But in general when you're dealing with user generated content you see a lot of weird stuff... we get a lot of JPG uploads that are actually MP4 video files, and sometimes the reverse, MP4 uploads that are actually still frame JPEGs.