-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
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:
|
Yeah it seems like point number three is fairly promising.
|
Very interesting, I hadn't seen |
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. |
@scofennell thanks for the additional details and sharing your real-world data. Will definitely continue working with this consideration in mind. |
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?
The text was updated successfully, but these errors were encountered: