How to fix image URL errors in a Shopify product CSV
Content and sources reviewed:
Shopify product CSV image fields need public image URLs. CatalogHandoff accepts absolute HTTP or HTTPS values from the WooCommerce Images field, preserves their order, and assigns one-based positions. A media-library filename blocks output because the browser cannot derive its public address safely. The converter does not download, rehost, or test images; malformed values are skipped with a warning, and reachability remains unverified.
Which image values are accepted?
An accepted value includes the complete scheme and host, such as https://cdn.example.test/products/tote.jpg. Multiple WooCommerce image values retain their source order. The first product image receives position 1, and later images receive increasing positions.
Official source: Using CSV files to import and export products (reviewed )
Why does a filename block conversion?
WooCommerce can resolve a filename that already exists in its media library. Shopify's product CSV expects an image URL. CatalogHandoff has no store address, media index, or permission to query a merchant system, so turning tote.jpg into a URL would be a guess.
Official source: Product CSV Importer and Exporter (reviewed )
How should you correct image rows?
- Find the reported source row and
Imagesvalue. - Replace filename-only entries with their actual public HTTPS URLs.
- Remove accidental text, local file paths, and unsupported URL schemes.
- Convert the corrected export again and review image positions.
Does the converter check that an image loads?
No. Conversion makes no external request, so it cannot confirm DNS, redirects, authentication, content type, or future availability. It validates URL structure only. Open representative image URLs yourself before importing a large catalog.