Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve email compatibility for WebP images #25

Open
scofennell opened this issue Oct 29, 2021 · 5 comments
Open

Improve email compatibility for WebP images #25

scofennell opened this issue Oct 29, 2021 · 5 comments

Comments

@scofennell
Copy link

Unfortunately, the webp image format is not well supported in some versions of Outlook:

https://www.caniemail.com/features/image-webp/

Although it's not a large % globally, I run a fairly run-of-the-mill platform for law firms, and for our audience the number is more like 15%.

In our case, our emails come from MailChimp scraping our RSS feeds, and so it would be nice to have a jpeg version available for use in RSS (assuming the blog author has uploaded a jpeg that we are converting to webp). And it would be nice if it were not the "full" image file, which can be way, way too large.

I'm not sure of the best way to go about this.

Any thoughts? Plans? Suggestions?

@adamsilverstein
Copy link
Owner

Hi @scofennell - thanks for raising this issue. Good point about mail clients not supporting WebP, I hadn't thought of images in that context.

Some thoughts:

  • we are working on supporting "multiple image formats" in Enable <picture> element & convert to multiple formats #1, this approach would use the <picture> element which enables supporting multiple formats, letting browser "fall back" top a type they support. The original intent was to support AVIF and JPEGXL which have limited browser support, but the same approach could be used for WebP. Still I'm not certain this approach works for Outlook, we would have to test that!

  • Consider opening a ticket with Mail Chimp where you are a customer - since a part of what their service does is prepare your content for emailing and the various idiosyncratic email clients out there. Given the increasing adoption of WebP on the web, they may (or maybe should) have plans to do their own WebP handling. Although given the fact that they would have to re-compress the lossy WebP files, this isn't really an ideal solution - image quality will sufer.

  • Final option once Enable <picture> element & convert to multiple formats #1 is in place: could could use WordPress filters to set image format for the RSS feed to JPEG, while keeping WebP for the front end/main site. This capability - to use specific image types for RSS - might also be appropriate for core, if we determine that mail client (or other RSS consumers) WebP support is poor.

@scofennell
Copy link
Author

scofennell commented Nov 1, 2021

Yeah it seems like point number three is fairly promising.

picture support in email is quite poor: https://www.caniemail.com/search/?s=picture

@adamsilverstein
Copy link
Owner

Very interesting, I hadn't seen caniemail before, thanks for sharing those links Looks like WebP support is pretty good fortunately, only outlook on windows completely lacks support. Does this apply to all versions of Windows? I'm a little surprised support isn't contingent on the version of the underlying operating system.

@adamsilverstein adamsilverstein changed the title Webp & Email Improve email compatibility for WebP images Nov 2, 2021
@scofennell
Copy link
Author

That's a good question and I don't quite understand it myself. Here's where I'm coming from:

In MailChimp, they offer an integration with the excellent "Litmus" service, for getting screenshots from various email clients. I'm getting the webp's NOT rendering in a variety of Outlook versions, and it totals to approx 15% of my stodgy, corporate audience.

It's unclear to me how those versions correspond to the caniemail numbers.

Regardless, it seems like the roadmap here is to leverage some ability to convert to multiple formats.

@adamsilverstein
Copy link
Owner

@scofennell thanks for the additional details and sharing your real-world data. Will definitely continue working with this consideration in mind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants