惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Martin Fowler
Martin Fowler
V
Visual Studio Blog
有赞技术团队
有赞技术团队
T
Tailwind CSS Blog
B
Blog
I
InfoQ
博客园 - 三生石上(FineUI控件)
阮一峰的网络日志
阮一峰的网络日志
F
Fortinet All Blogs
H
Help Net Security
博客园 - Franky
宝玉的分享
宝玉的分享
博客园 - 司徒正美
C
Check Point Blog
G
Google Developers Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Jina AI
Jina AI
T
The Blog of Author Tim Ferriss
MongoDB | Blog
MongoDB | Blog
云风的 BLOG
云风的 BLOG
A
About on SuperTechFans
罗磊的独立博客
大猫的无限游戏
大猫的无限游戏
IT之家
IT之家

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
WebP Isn't the Villain
hamasaki · 2026-05-19 · via DEV Community

Let's talk about WebP. Google created it back in 2010 with a dead-simple goal: make image files smaller without losing quality. And honestly, it works flawlessly.

A lossy WebP is about 25% to 35% smaller than a JPEG. A lossless WebP is way smaller than a PNG. It supports transparency. It supports animation. It’s basically the ultimate Swiss Army knife of image formats.

But then you download an image from Google Images, and it saves as a .webp. You try to drop it into MS Paint... nothing. You drag it into Photoshop (depending on the version)... error. Clip Studio Paint? Nope. Figma? Sure, it opens, but sometimes it glitches out out of nowhere.

The internet's collective rage is perfectly summarized by this classic copypasta:

THE CLASSIC:

"Why is this a webp?! I hate webp! Just give me a png, please. MS Paint won't open a webp. Photoshop won't open a webp. Clip Studio Paint won't open a webp. I have to google 'webp to png converter' and pray it keeps transparency. I hate it."

Enter fullscreen mode Exit fullscreen mode

The pain is real. I get it. But the fault lies with sluggish software that refuses to update, not with a format that actually evolved. (¬_¬)

WebP is technically superior.

Let’s look at the facts. WebP uses much more modern compression algorithms than JPEG and PNG. It gives you:

Better lossy compression than JPEG: Way smaller files, same visual quality.

Better lossless compression than PNG: Perfect transparency at a fraction of the file size.

Animation support: Like a GIF, but way smaller and without that terrible 256-color limit.

8-bit Alpha Channel: Smooth, beautiful transparency gradients, not just binary (on/off) transparency.

Enter fullscreen mode Exit fullscreen mode

If the entire web fully embraced WebP, websites would load faster, apps would consume less data, and servers would save massive amounts of bandwidth. It’s a win-win for everyone.

But no. We still prefer to manually convert things back to PNG and send a 3x larger file over Discord or WhatsApp. Why? Because the software opens it. ¯(ツ)/¯

The Creator’s Response

There’s a famous tweet floating around where someone said, "I hope the inventor of WebP gets run over by a bus." The creator of the format casually replied: "I invented the WebP lossless format in 2011."

It feels a bit smug, right? But at the same time, I completely get him. The guy built a genuinely great piece of technology, and the whole world decided to hate his guts because Windows 7 Paint couldn't open it. (T_T)

If WebP had been invented in 1995 and everyone had 30 years to implement it, things would be different. The blame for the lack of adoption lies squarely on Microsoft, Adobe, Corel, and every other company that took an absolute eternity to roll out decent native support.

Things are finally getting better

Fast forward to today, and support is actually pretty solid. Windows 11 Paint opens WebP natively. The latest Photoshop CC handles it. Every major browser supports it. Even FFmpeg deals with animated WebP like a champ. Yet, the reputation of being a "bothersome format" stuck around.

It’s completely unfair. Imagine if we hated MP4 because Windows Media Player back in 2004 couldn't play it. Or if we hated PDF because some old, crusty reader crashed. We would blame the software, not the format. With WebP, we do the exact opposite. (⌐■_■)

What really pisses me off is when a site serves a WebP for download, and a regular user just can't use it for their everyday stuff. It's not their fault. They just want to open a picture. The ecosystem failed them.

So, what's the solution?

The solution isn't to retreat back to PNG and JPEG forever. It’s to demand that the software we use supports modern formats. Microsoft, Adobe, Affinity, Corel—all of them. WebP is over 15 years old now. It’s not a niche, experimental thing anymore.

And if you are a web dev, serve WebP to the browser but always provide a fallback. HTML has the tag specifically to solve this exact headache. Don’t force a user to download a format they might struggle to open in their favorite desktop app if they hit "Save Image As".

Look, WebP doesn't deserve the hate. It just wanted to make the web lighter and prettier. The blame lies on Photoshop and friends, who took too long to give it some love.

Sorry, WebP. We treated you poorly. (´。• ᵕ •。`)

By