Why was my Meta Commerce image suppressed: Meta Commerce: image URLs must return 200 over public HTTPS?

Meta's catalogue ingestion fetches each product image URL and rejects assets that fail HTTPS, return non-200 responses, or load too slowly. Image CDNs that require authentication will fail validation. Fix: Publish your Meta export to a public CDN over HTTPS (CatalogPrep's marketplace pack honours this by default). If you self-host, confirm the asset URLs are not behind login or referrer gating.

Meta Commerce suppression

Why your Meta Commerce image was suppressed - and how to fix it

Meta Commerce flags 2 image rules that suppress or reject listings. Each is sourced, dated, and fixable. Run a free audit to find which apply to your photos.

Audit my Meta Commerce images See all rules

Meta Commerce: 500×500 minimum, 1080px+ short edge recommended

Meta's catalogue for Shops on Facebook and Instagram requires a 500×500 pixel minimum (1:1 works across placements). Meta scales images aggressively, so 1080 px or more on the short edge is recommended to keep product cards from looking blurry.

What we check: CatalogPrep reads the file dimensions and aspect ratio and warns when the short edge falls below 1080 px or aspect deviates from square by more than 2%.

How to fix: Use CatalogPrep's auto-crop with the Meta Commerce square preset. We never upscale beyond the source - re-export from your design tool if your source falls below 1024 px.

Meta Commerce: image URLs must return 200 over public HTTPS

Meta's catalogue ingestion fetches each product image URL and rejects assets that fail HTTPS, return non-200 responses, or load too slowly. Image CDNs that require authentication will fail validation.

What we check: CatalogPrep verifies that the export pack publishes images over public HTTPS and that the resulting URLs return 200 within the Meta ingestion timeout budget.

How to fix: Publish your Meta export to a public CDN over HTTPS (CatalogPrep's marketplace pack honours this by default). If you self-host, confirm the asset URLs are not behind login or referrer gating.