Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I work customer service and the amount of people who send in HEIC files for compensation claims yet don't know or understand what HEIC is or how it was enabled in the first place is astounding. We regularly have to decline them if they're too tech illiterate to send JPGs.

It's the iTunes Connect of file formats. The world was fine with JPG and RAW.
Sounds like you're not exactly providing a good customer service then if you aren't catering to your customers' needs...
 
I'm still salty with heic. A couple of years ago I was on an important project and took at least 300 photo/video of the progress and uploaded them to OneDrive. Nobody could open them at the time. The work around was to buy some $.99 extension opener from the Microsoft Store because Microsoft was too cheap to bake it into Windows.
 
  • Like
Reactions: Chuckeee
HEIC is such a PITA and yet I just continue to live with it. It should just auto convert to JPG or something usable when you airdrop. While Im sure theres a simpler solution, I just open in preview every time
Auto-conversion tools would be nice

Unfortunately, image formats are largely dependent on daily internet usage, and as a result, they rely on whether major web browsers, like Google Chrome, Microsoft Edge, or similar, support them. Google wasn’t interested in adding it to Chromium (the open-source project behind Chrome and Edge), which is why you don’t hear much about it. However, in the GitHub world, there are several free ways to force Windows to support JPEG XL.

"Chrome is 'against' because of 'insufficient ecosystem interest' and because they want to promote improvements in existing codecs," said Sneyers, pointing to JPEG, WebP, and AVIF. "Those last two are after all codecs that were developed in part by people from the Chrome team, so it makes sense that they want to promote adoption of their own codecs."
Browsers for very obvious reasons prioritize royalty-free stuff prioritizing small file sizes and so on over stuff for premium/best representation of video/photos that is typically proprietary or not royalty-free such as a lossless format and Dolby Vision HDR.

Browsers typically don't fully align on the exceptions and formats they support making image/video CDNs invaluable to conditionally serve the best image format among the ones a browser supports using the "Accepts" header of requests a particular browser receives.

When I work on Websites, I use a Image CDN to conditionally serve JPEG-XR, WebP, or AVIF (the best one widely supported thus far) on the Websites for clients.

This is particularly invaluable for Websites highlighting fashionistas, product designers, and photographers.

Browsers evolve their media/DRM support matrix occasionally independently from each other necessitating these techniques–even the browsers that use the same engine.
 
I do hope that this will push winder adoption of JPEG-XL... Firefox recently somewhat U-Turned on dropping it... it's so much better than other..
Better than AVIF? There's trade-offs such as how they fare with illustrations (admittedly an edge case as SVGs should be prioritized for such use cases) and animated photos (AVIF is massively superior unsurprisingly being based on AV1 video codec).
 
I guess it's time to batch all the .heic back to .jpeg
Why? That would result in files with lower quality and higher file size. So worse all around. Unless you mean batch converting to jpeg xl in which case you may want to wait until more os level and app support. With Apple adding some support to Mac last year and then Google reversing course and will supporting, there is a lot of momentum for this royalty free format to take over but will take time. And more robust converters will popup.
 
I guess it's time to batch all the .heic back to .jpeg
I did this a few years ago. It was obvious .heic wasn't going to catch on and too many issues in my multiplatform ecosystem (work is Windows, home is Mac, work phone is Android, personal phone is iOS), I decided I rather have the simplicity of JPEG.
 
When I import hdr jxl files created in photoshop into photos(lossless or lossy), the colours get weird and there are subtle pastel-coloured compression-looking artifacts, especially on sky/white parts that for example heic and avif doesn't get after import. I've tried both P3 and rec.2020 and both seems to have an issue after being imported. Maybe after macos 15/ios18 are out of beta this bug gets fixed, until then i'll stick to avif for hdr photos.
 
Is there a chance that JPEG-XL will come to 15 Pro / 15 Pro Max? I'm using 48mp HEIF Max as my default camera setting and it looks like JPEG-XL is impressive enough to provide a notable image quality upgrade on its own.

The new 48mp ultrawide sensor & faster 48mp sensor on the 16 Pro / 16 Pro Max looks interesting, but I'm honestly more interested in JPEG-XL. I use google photos and Lightroom and I'd expect JPEG-XL to play a lot better with both of those than they do with my HEIF Max files once everything gets updated to provide 16 Pro series file support.
 
Last edited:
  • Like
Reactions: .wojtek
I'm still salty with heic. A couple of years ago I was on an important project and took at least 300 photo/video of the progress and uploaded them to OneDrive. Nobody could open them at the time. The work around was to buy some $.99 extension opener from the Microsoft Store because Microsoft was too cheap to bake it into Windows.
The first thing I do after any iOS upgrade is to confirm whether the camera format is still set to "Most Compatible"
 
Better than AVIF? There's trade-offs such as how they fare with illustrations (admittedly an edge case as SVGs should be prioritized for such use cases) and animated photos (AVIF is massively superior unsurprisingly being based on AV1 video codec).
From what I read and (marketing) info on their page (https://jpegxl.info/) it seems to be better. And even if it was on pair it still shines when it comes to features and benefits (and backward compatibility)
 
I work customer service and the amount of people who send in HEIC files for compensation claims yet don't know or understand what HEIC is or how it was enabled in the first place is astounding. We regularly have to decline them if they're too tech illiterate to send JPGs.
And you're apparently tech-literate enough to be able to convert them to JPGs, but decline them instead?

Sorry, but we'll have to disagree where the problem is in that process.
 
  • Like
Reactions: jhfenton
From my experience, HEIF files produced in my 15 pro are notably better than JPG. HDR, and things like colour gradations in a sky, are clearly better.

Personally, I don’t understand why anyone would use JPG. I haven’t for years
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.