A DEV Community post examines the image endpoint that comes with Next.js, a popular web framework. The author's site uses Next 16.2.7 and has no images setting in its config file, so every behaviour described is a default. The author mapped it all from outside using curl, a command-line tool for sending web requests.
The endpoint accepts only 15 widths. Any other width gets a 400 error, which means the request was rejected. The author says the old 16 pixel size is no longer on the list. Quality is also locked to one value, 75. Other values are rejected rather than adjusted. The author ties this to a Next 15.4 change that stops anyone from requesting many qualities of one image and forcing the site owner to pay for each conversion.
Formats are limited too. By default the optimiser serves WebP only. AVIF, a newer format, is supported but switched off. A browser that asks for AVIF but not WebP gets the source image re-encoded instead, which the author measured as 53 per cent larger than the WebP version. The author says enabling AVIF takes one line of config, and cites published figures putting AVIF 20 to 30 per cent smaller than WebP at matched quality. The cost is longer encoding when an image is not yet cached.
The post also covers safety defaults. SVG processing is off, and no remote hosts are allowed, so the endpoint cannot act as an open image proxy. On caching, the author found the browser is told to recheck images every time, because the source files in public/ carry that instruction forward. The CDN, the network of servers that stores copies, still caches the result.
Why it matters
Framework defaults decide what your visitors download, even if nobody on your team chose them. In this case, a site that never touched its image settings serves WebP at most, at one quality, and tells browsers to recheck each image. Those are quiet costs in page weight and repeat visits.
The post also shows that you can inspect your own setup from outside, without reading code. A few test requests reveal which widths, qualities and formats your site really serves, and what your source files actually are. According to DEV Community's author, that last check even exposed JPEG files wearing a .webp name.
Treat the author's size figures as their own measurements and published claims, not a guarantee for your images.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.