The current header changed, but the real question did not
Current Shopify product CSVs use `Product image URL`. Older files may still contain the legacy `Image Src` header, so this checker accepts both instead of treating an older export as automatically broken.
It then checks what can be determined locally: whether the value parses as an http/https URL, whether whitespace has slipped into it, and whether the same URL appears repeatedly in a suspicious way.
A share page that opens in your browser is not necessarily an image URL
A Google Drive or Dropbox share page can look fine to a person while still being unsuitable for Shopify to fetch as an image. Share-page-like URLs are therefore warnings, not proof that the image will fail.
Current Shopify guidance also says to avoid image filenames ending in suffixes such as `_thumb`, `_small`, or `_medium`, so the checker surfaces those names before import.
A syntactically valid URL can still be unreachable
This tool deliberately does not fetch remote images. Access permissions, redirects, TLS, anti-bot rules and the actual Content-Type returned by the host cannot be established reliably from a local CSV check.
Zero errors means the CSV-side URL format looks reasonable. It does not replace a small real import test for a new image host.
Check the product row as well as the image row
Additional image rows still depend on the product identifier structure in the Shopify CSV. A perfect image URL can land in the wrong place if the product rows are malformed.
For a broader check, run the Shopify CSV Validator — Product Import Preflight after this image-specific pass.