Why Does My Product Image URL End in JPG While the Browser Receives AVIF or WebP?

Distinguish the source name from the delivered representation

A product photograph may have been uploaded as bottle.jpg while a CDN returns a different encoded representation to the browser. The URL's extension describes a source naming convention or route; it does not necessarily identify the bytes delivered by a transformation service.

Cloudflare's official Images documentation states that hosted images can be automatically transcoded to supported modern formats. Its image-transformation documentation also describes format=auto as choosing an efficient format supported by the requesting browser.

These are provider-specific behaviors, not a rule that every image host changes formats. Determine which CDN or image-processing service actually owns the URL before diagnosing it.

A legitimate format transformation should not silently change the product's identity, label or variant. Encoding choice and visual fidelity remain separate approval questions.

Inspect the HTTP response

Open the exact product page in browser developer tools and select the image request in the Network panel. Record the requested URL, response status, response Content-Type and transferred size.

For example, a URL ending in .jpg may return a response declared as image/avif. That is consistent with an automatic transformation route when the provider documents such behavior.

Check the request's Accept header when investigating format negotiation. Cloudflare's Worker transformation documentation explains that custom Workers using automatic format selection need to inspect the Accept header and select an appropriate supported format.

Do not infer that every browser sends identical Accept values. Do not assume a CDN applies the same transformation to every file size, content type or client.

If the image fails to display, inspect the actual response and browser compatibility before changing its filename. A wrong content type, failed request or corrupt payload is a different problem from a valid negotiated format.

Separate a valid format change from a delivery defect

Compare the CDN-delivered image with the approved master at the same meaningful viewing size. Inspect the product label, texture, transparency and variant identity.

If the browser successfully displays the intended image and the encoding is supported, the extension difference alone is not a defect. If fine lettering becomes unreadable, investigate the transformation's quality and resizing settings.

If an external system downloads the image and expects literal JPEG bytes because the URL ends in JPG, verify that system's documented requirements. It may need a fixed-format export rather than an automatically negotiated browser rendition.

Keep the source file and served derivative separately identified. A transformed image may also have different metadata, so provenance requirements need independent inspection of the delivered response.

Do not force every client to receive JPEG merely to make the URL suffix and content type agree. Choose the delivery route according to actual compatibility and fidelity needs.

Hypothetical case: a product image changes encoding

Hypothetical CDN example; no request was sent. A fictional store uploads blue-bottle.jpg and uses a Cloudflare image-delivery route with automatic format selection.

Candidate A represents a browser whose request supports AVIF. The stipulated response declares image/avif and displays the approved blue bottle correctly. The format difference is not automatically a failure.

Candidate B represents an external processor that requires JPEG input and cannot handle the received AVIF response. B needs an explicitly supported fixed-format delivery route or a properly converted JPEG copy.

Candidate C displays the wrong bottle color despite a valid AVIF response. That is an asset-mapping or content-fidelity failure, not evidence that AVIF is inherently unsuitable.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Cloudflare Images — Features: Primary provider documentation for automatic output format selection and supported image transformations.
• Cloudflare Images — Serve Uploaded Images: Documents automatic transcoding of uploaded images according to client capabilities.
• Cloudflare Images — Transform via Workers: Documents custom Worker handling of Accept headers for image-format negotiation. The blue-bottle response is hypothetical.