Why tiny JPEGs look different in Chrome
- ID
- 13841
- Status
- summarized
- Published
- 12 Aug 2026, 10:00 PM
- Fetched
- 14 Aug 2026, 3:11 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://guillaumetech.github.io/posts/jpg-scaling-chrome/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.5
- Created
- 14 Aug 2026, 3:14 PM
- Tags
- Audience
- developersvibe_coders
What happened
Chrome uses a JPEG decoding optimization where it avoids fully decompressing large JPEGs when rendering them at small sizes, instead leveraging the DCT frequency-domain data directly. This causes tiny JPEGs to look noticeably different in Chrome versus Firefox—often thicker or less faithful to the original—because high-frequency detail is handled differently during downscaling.
Why it matters
If you ship small JPEG icons or logos (e.g., 15-20px), don't assume they render identically across browsers; Chrome's partial-decode optimization can alter appearance at small sizes. Switching to SVG for small icons avoids this entirely, as the author did.
Discussion angle
When does cross-browser rendering divergence become a real UX bug versus a curiosity—and should teams set a policy of SVG-only for sub-30px icons to avoid it?