Find where the product image disappears
A missing Magento product image can be a catalogue-data problem, a missing source file, a generated-image failure or a delivery issue between the server and browser. The visible placeholder does not identify which layer failed. Midoriweb starts with the exact product and page context, then traces the image from its assigned role to the URL requested by the customer’s browser.
Record whether the problem affects product pages, category listings, search results or all of them. Check one affected SKU and one working SKU using the same storefront. If only one size or context fails, that is a useful clue about image roles or generated variants rather than proof that the entire media library is missing.
For catalogue-wide failures after a deployment or migration, preserve the timing and recent changes. The Magento migration checklist provides broader planning context, while this guide focuses on the image path itself.
Check the image assignment and store context
Magento uses different image roles for different presentation contexts. Adobe’s product images documentation describes those roles. Confirm that the affected product has the intended image assigned for the page being tested and that store-view overrides are understood.
A gallery image existing in Admin does not automatically mean it is selected for every required role. Compare the effective product data with a working example of the same product type. For configurable products, also check the relationship between parent presentation and the selected child variant.
Avoid re-uploading the same file repeatedly before checking assignment. Duplicate media entries can make the catalogue harder to maintain without addressing a scoped role or frontend selection problem. The correction should leave a clear, intentional image configuration.
Inspect the requested URL and response
Use the browser’s actual image request to establish what fails. A missing file response, access error, server exception and successful response with an unsuitable content type are different findings. Compare the URL with the expected media base and the current environment rather than guessing a filesystem path from the product name.
Check whether the failure comes from the origin or a CDN. A cached missing-file response may persist after the source is restored, while an origin failure will continue even when edge caching is bypassed through an authorised diagnostic route. Do not clear unrelated caches without first identifying the affected layer.
Also inspect whether the page references an old domain or scheme after a migration. A correct image in Admin may still be presented through a stale frontend URL. The evidence should identify the exact generated URL and the configuration or template responsible for it.
Separate source media from generated variants
Product presentation often requires resized or transformed versions of an original image. Establish whether the original file exists and is readable, then whether the required variant can be generated and served. A missing original cannot be repaired by repeatedly regenerating derivatives.
If generation fails, inspect the relevant application error, available storage and image-processing dependencies. File ownership and directory permissions should match the deployment model. Making the whole media tree universally writable is not an appropriate substitute for correcting the intended account or permission boundary.
A broad regeneration can consume substantial resources on a large catalogue. Plan its scope and timing, observe progress and stop if it threatens customer traffic. A limited test on representative affected products is a better first diagnostic step than an unmeasured rebuild of every image.
Investigate imports and external media sources
If images disappear after an import, compare the source file, import mapping and resulting product data. Check whether blank values, replacement behaviour or incorrect paths changed existing assignments. Preserve the original import and validation output so the failure can be reproduced with a small sample.
Adobe’s product image import guide documents supported input conventions. The exact process depends on the installed version and whether a third-party importer is involved. Do not assume that a path accepted by one integration is valid for another.
For remote images, establish whether the importer can reach the source at the time it runs. A URL that opens in your personal browser may require access or behave differently for the server. Avoid placing private access tokens in permanent catalogue image URLs or general troubleshooting notes.
Check the theme and frontend selection logic
When the image request succeeds but the picture is invisible, inspect the rendered element and presentation. A layout rule, lazy-loading component, gallery script or custom product-view logic may prevent display. Compare the affected viewport and interaction with the same image in a working context.
Mobile-only failures deserve their own reproduction. A responsive source selection or gallery transition may request a different asset or apply different dimensions. Do not call the issue resolved after checking only a desktop product page. Include category and search cards where the merchant first noticed the problem.
Midoriweb can connect catalogue evidence with Magento frontend development. The aim is to correct the responsible data or rendering behaviour while preserving image quality, accessibility and the approved design.
Repair the smallest affected layer
A targeted fix might restore missing source media, correct product roles, repair URL generation or adjust the frontend component. The recovery plan should state which layer is changing and what evidence supports that choice. Preserve the original assignments and files before a bulk operation.
If a CDN has retained stale responses, invalidate the relevant assets through the configured process after the origin is correct. Repeatedly purging the entire delivery layer before repairing the source can increase traffic without producing a lasting improvement.
After a bulk import correction, sample products from each affected class. Include products that were already correct, so the repair is checked for unintended changes as well as successful recovery. A count of processed records is not proof that all image roles now match the intended catalogue.
Verify presentation, accessibility and performance
Check that the right image appears in listings, search, product galleries and selected variants. Confirm that it remains sharp enough for its displayed size without forcing unnecessarily large downloads. Where images convey product information, alternative text should describe that information rather than repeat a string of keywords.
Measure layout behaviour as the image loads. Reserving the intended space helps prevent visible movement, and the most prominent image should not be delayed by inappropriate loading behaviour. Our Core Web Vitals guide explains how image loading and layout stability relate to customer experience.
For a support brief, include affected SKUs, page URLs, the contexts that fail, the first observed time and recent imports or deployments. Redacted screenshots help, but the actual failed request and product configuration are usually needed to establish the cause.
Product image questions
Why is the image visible in Admin but missing in the shop?
Admin visibility proves only part of the path. Store-specific roles, generated variants, delivery URLs and frontend rendering still need checking.
Should we regenerate every catalogue image?
Only when the evidence and recovery plan justify that scope. First verify that source files exist and a limited regeneration succeeds.
Can an image problem affect SEO?
Missing or poorly described images can reduce the usefulness of a page. Fix the customer experience and accessible description; do not treat keyword-heavy filenames or alt text as a substitute for correct media delivery.