After a CDN—a system that delivers files through separate servers—was connected, some photos stopped displaying. The file is still in the media library, and the old URL still opens. To find the cause, check the request made by the browser on the affected page: that URL, its response, and the transformation rules determine the result.
Suppose the images were moved from example.ru/uploads/ to media.example.ru/. Check the source file, the CDN URL, and the resized versions. An available original does not necessarily mean that the thumbnail in a product card will load too.
Find the URL the browser selected for the broken photo
In the Network tab, find the corresponding request and record the full URL, including its parameters. Note the size and format parameters, as well as whether the URL has a signature, if the CDN uses one. First, save the broken URL as it is. If you remove its parameters before checking it, you may lose the cause of the thumbnail error.
Check where the image is used. The main product-card photo, thumbnail, and background banner may be generated by different systems. If only the thumbnails are broken, changing the overall domain does not explain everything: compare the rules for that specific path rather than declaring the entire file delivery system unavailable.
Select the img element in Chrome DevTools:
Select the broken photo in the Elements tab, then read its URL in the browser console:
({ src: $0.src, srcset: $0.srcset, выбран: $0.currentSrc });In Network, open the request for выбран, then check the status and Content-Type. If the response is 200 with HTML, the photo was not retrieved. If it is 404, compare the path /uploads/ with the original: the prefix may have been added twice.
Check the response, not the .jpg extension
If redirects are involved, follow the chain to the end. The image may lead to a website page, an old domain, or unavailable storage. In your report, list the original URL and the final result separately: the developer needs to know at which redirect the destination changed.
Compare the response body with the expected file. Open the image directly and make sure it actually decodes and shows the right item. A small placeholder logo with a successful status is not a restored product photo. The check must include the content, not just the absence of a network error.
Compare the CDN path with the original
The responses from the original and the CDN indicate where to look for the cause:
| Observation | Next check |
|---|---|
| The original is available, but the CDN returns 404 | The path-building rule and the source address |
| Neither the original nor the CDN is available | Whether the file exists and the permissions on the source storage |
| The full-size image works, but the thumbnail does not | Transformation parameters and supported sizes |
| The CDN returns a login page | Access to the source and the settings for private storage |
Do not publish private tokens or service-access links in your report. If you send the URL to a developer, hide the token while keeping the names of the other parameters. Do not open access to the entire storage just to load one public photo.
Check the URL signature and guest access
If the response is 403, find out what access conditions apply: a URL signature, expiration time, hotlink protection, or an allowed request source. A link copied from an authenticated dashboard may work for an editor and fail for an ordinary visitor. Check the public-user scenario separately.
Do not disable all CDN restrictions for a single file. Find out whether the photo should be public or available through a temporary signed URL. For a public photo, fix its path or CDN permissions; for a private one, fix how the URL is generated and how long it remains valid.
Tell page caching apart from image caching
If the browser requests the same incorrect URL again after its cache is cleared, the problem may be with the product-card generator rather than a cached file response. Conversely, the HTML may already be correct while a separate delivery layer still returns the old image. Check the HTML containing the image URL separately from the CDN response at that URL.
After fixing the issue, open the page again without using saved local responses. Do not rely only on reloading the editor window: an image in the browser's memory can hide the defect. In Network, make sure a fresh request was made to the new CDN URL and that the response contains the right photo.
Repeat the check on two screens
Check the rules for crawling the delivery domain if images should be available to search engine crawlers. Google describes CDN considerations and image discovery in its image guidelines. Whether the product-card HTML is available and whether the photo is available are separate observations; one does not confirm the other.
For general guidance on image size and format, use the image optimization guide. If the lazy-loading mechanism also changed, compare it with the lazy loading guide: a loading-timing error is different from a URL or access error.
Open the thumbnail and the full-size photo
In a new guest session, the photo of the correct item loads from the new CDN URL. Check a phone screen, a wide catalog, and the gallery zoom: different sizes may have different URLs and errors.
Read also: Image optimization, Lazy loading images, Technical page audit.