TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Is only using WEBP images “acceptable” in 2021?

5 pointsby johnnyApplePRNGover 3 years ago
Or should I support the ubiquitous JPEG as well?

3 comments

PaulHouleover 3 years ago
I did a review of this the other day.<p><a href="https:&#x2F;&#x2F;caniuse.com&#x2F;webp" rel="nofollow">https:&#x2F;&#x2F;caniuse.com&#x2F;webp</a><p>The biggest holdout I can see is that users of older Macs don&#x27;t have webP support on Safari. I have an old Mac Mini that my wife uses to read her email that is that old and confirmed that webP doesn&#x27;t work. On that machine, WebP works just fine with Firefox.<p>I decided it was marginal and that I was going to support JPEG and WEBP in my current project because:<p>1. I&#x27;m not publishing a huge amount of content and the storage cost of the JPEG isn&#x27;t a problem, and 2. I want the system to be adaptive to what image formats the client supports (looking forward to JPEG XL even though I&#x27;m disappointed with AVIF) I am building the facility in and might as well demonstrate it works with JPEG.
moxylushover 3 years ago
Yes, I thinks so but it might depend on your audience, mobile bounce rate, content churn, and image automation build. Meaning you might find it preferable to serve most of your visitors images 60% smaller then worry much about those that are not evergreen.
ParameterOneover 3 years ago
Why would you not support jpeg?
评论 #28898743 未加载