Why Does My Product Image Download Instead of Opening in the Browser?

The response can tell the browser to download

The HTTP Content-Disposition response header describes how content should be handled. MDN documents inline for ordinary inline presentation and attachment for download-oriented handling. An attachment response may also suggest a filename.

For a product photograph, the server might return a valid JPEG with Content-Type: image/jpeg and Content-Disposition: attachment; filename="organizer-front.jpg". The browser can offer a download even though the bytes are recognizable as a photograph. Changing the extension to PNG does not change that response instruction.

Do not infer the header from the visible URL. A path ending in .jpg can still return an attachment disposition, a redirect or an entirely different resource. Conversely, an image URL without a familiar extension can still be displayed when its response and content are suitable.

Inspect the clicked request rather than the asset name

Have the site maintainer reproduce the click with the browser's network inspector open. Record the actual clicked element, final URL after redirects, response status, Content-Type and Content-Disposition. Check whether the link includes an HTML download attribute, because link behavior can also affect the result under applicable browser rules.

Distinguish three observations. If the final response declares attachment, inspect the hosting or download endpoint configuration. If it declares inline or has no attachment instruction, inspect the link and browser handling rather than assuming the server forced a download. If the photograph opens directly but the merchant wanted an in-page zoom viewer, the missing piece is a gallery interaction, not necessarily a response-header defect.

Inspect the final response, not only the initial redirect. A signed or protected delivery endpoint may redirect to a storage service that sets its own headers. Any repair must be made in the service that actually controls the response.

Hypothetical case: an approved detail image is served as an attachment

Hypothetical illustration, not a live request: A fictional organizer listing links its front-view thumbnail to an asset-delivery endpoint. The approved JPEG is 1200 by 1200 pixels. Assume the final response is successful, identifies JPEG content and includes Content-Disposition: attachment.

The seller wants visitors to view the larger photograph, not save it immediately. The maintainer compares two proposed routes. Route A keeps the download endpoint, which is appropriate for an intentional file-download action but not the requested gallery interaction. Route B serves the approved image through a viewing-oriented endpoint and configures the page's intended viewer.

These are proposed configurations, not observed outcomes. The correction is accepted only after the final page is checked in the intended browser, including how the visitor returns to the product listing. The worksheet records the stipulated response and the separate interaction decision.

Fix the owner of the behavior

If a public image-viewing endpoint wrongly sends attachment, ask its owner whether the supported configuration can serve the image inline. Do not bypass authentication, remove access controls or expose a private result URL merely to make the browser display a file. If the destination intentionally offers downloads, preserve that behavior and use a different approved route for viewing.

If the response is already suitable for inline display, inspect the actual gallery component. A lightbox requires an implemented viewer; an ordinary media-file link does not automatically become one. The existing WordPress gallery link guide covers that application-specific choice.

Recheck the image identity and approved version after any routing change. A technically successful inline response can still display an obsolete variant or an undersized derivative. Record access, navigation and content approval separately. No server or browser was operated for this illustrative case.

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

• MDN — Content-Disposition header: Defines inline and attachment response dispositions, filename parameters and relevant interactions with browser download behavior.
• MDN — a HTML element: Documents the download attribute and link navigation behavior; its interaction with response headers and origins must be evaluated in the actual browser.