According to a post on DEV Community, a developer tested a popular trick for avoiding WebP images. Some people use a browser extension to remove image/webp from the Accept header, the line Chrome sends to tell a server which image formats it can handle. The hope is that the server then sends a JPEG instead.
The author ran the test on 15 November 2026 against five image hosts, using curl with a Chrome user agent. Each request was sent three times. One version used Chrome's normal header. Another removed both image/webp and image/avif.
Three of the five hosts prefer AVIF over WebP. For those, removing WebP changed nothing, because AVIF was still allowed and was already what they sent. Only the Shopify CDN, which tops out at WebP, fell back to the original PNG. The Nike URL uses a fixed named preset with no format option, so it sends the same PNG to everyone. Its response had no Vary header, which is the signal that a format depends on the request. The other four sent Vary: Accept.
A request with Accept: */* returned the original format from all five hosts. That is what curl and wget send by default, which explains why a command-line download often gives a JPEG while Save image as in the browser gives WebP or AVIF. The browser saves the bytes it already received.
The author also found that changing the URL can work better. With Chrome's normal header, imgix returned a real JPEG for fm=jpg, and Cloudinary did the same for f_jpg in place of f_auto. Shopify's CDN did not: format=jpg and format=pjpg still returned WebP. The author notes they make PixLasso, a Chrome and Edge extension that converts images on right-click.
Why it matters
Many image CDNs, which are services that deliver images from servers close to the visitor, choose the file format based on what the browser says it accepts. This test shows that the choice is not simply WebP or JPEG. Visitors with a modified header may still get AVIF. Visitors with both formats removed may get larger files and slower pages, according to the article.
For site owners, the point is that your image URLs and CDN settings decide what people receive. If your host uses a fixed preset, the format is the same for everyone. If it varies by Accept header, the Vary header tells caches to store separate versions. Knowing which setup you have helps you predict what users and downloaders will see.
The results come from five hosts on one day, so they may not match every setup.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.