If some product images fail to process in Cropink, the issue is usually related to image accessibility rather than your design.
Below are the most common reasons and how to resolve them.
1. Cropink Is Blocked from Accessing Your Images
The most common cause is that your hosting provider, CDN, firewall, or security settings are blocking Cropink from downloading your product images.
When this happens, Cropink cannot access the image URLs from your product feed, so the images cannot be processed.
How to fix it
Ask your hosting provider or IT team to allow requests from the following Cropink IP addresses:
192.0.2.10 198.51.100.25 203.0.113.40
Once these IP addresses are whitelisted, Cropink will be able to download and process your product images normally.
đĄ Tip: If your website uses a firewall, CDN, or services like Cloudflare, make sure these IP addresses are excluded from any security rules or bot protection.
2. The Image URL Is Not Accessible
Cropink downloads images directly from the URLs provided in your product feed.
If an image URL is broken or unavailable, the image cannot be processed.
Common examples include:
The URL returns a 404 Not Found error.
The image has been removed from the server.
The URL redirects to an invalid location.
The server returns an error such as 403 Forbidden or 500 Internal Server Error.
How to fix it
Open the image URL from your product feed in a private browser window.
If the image does not load, the issue is with the source image and needs to be fixed on your server or in your product feed.
3. The Server Restricts External Requests
Some servers are configured to only allow images to be accessed from a web browser or from the store's own domain.
Since Cropink retrieves images automatically, these restrictions may prevent the download.
How to fix it
Make sure your image server allows external requests and does not require:
authentication,
cookies,
browser sessions,
or specific referrers.
Images should be publicly accessible via a direct URL.
4. Temporary Server or Network Issues
Occasionally, image processing may fail because the image server is temporarily unavailable or responding too slowly.
In many cases, the images will be processed successfully during the next project update.
How to fix it
If the issue is temporary:
Verify that the image URL is accessible.
Run Update Now in your Cropink project.
Check whether the image has been processed successfully.
Still Having Issues?
If your image URLs are accessible and Cropink IP addresses have already been whitelisted, but some images still fail to process, contact our support team.
To help us investigate faster, please include:
your project name,
a few example product IDs,
and the affected image URLs.
We'll be happy to help identify the cause.