If you receive an error code for an image request, you can find the meaning and possible causes below.
List of errors
400 Bad Request
- The image is requested from a Web Proxy Source, and the URL that is proxied is not an absolute URL.
- The image is requested from a Web Proxy Source with an invalid hostname.
- The image is requested from a Source with the Secure URL option turned on, but the
ssignature is either missing or invalid.
- The Source is configured to know the presence of the object, but the object is missing.
- Any permissions that the Source needs to access images from the origin are incorrect.
404 Not Found
- The image cannot be accessed from the origin. Please check that:
- The file path to the image is correct in your imgix source settings
- If you're using an S3 source, check that the the S3 Access Key and Access Key ID credentials entered in imgix are valid, and that IAM user has sufficient permissions to access the object
- The image can be accessed by imgix and is not being blacklisted
- The HTTPS certificates on the origin are valid and working
- The image is requested from a Source that is not deployed.
- Check to see that the Source is actually deployed
- The image is requested from a Source that does not contain the hostname of the URL under Domains.
413 Request Entity Too Large
- The requested image is too large. Our current input limit is 500MB.
421 Misdirected Request
- The requested image has failed internal verification. This is usually caused by a corrupt image.
422 Precondition failed
- A parameter in the query string contains an invalid value, e.g.
500 Internal Server Error
- An error occurred while processing the image.
503 Service Unavailable
- Temporary unavailability due to processing requirements, i.e. a requested GIF is too large.
504 Gateway Timeout
- A timeout occurred while attempting to fetch the object from the origin.
More troubleshooting info
Improper base64url encoding
If the URL contains a base64 encoded value, check to see that it's using proper base64 URL and filename safe variant (
Base64url encoding replaces certain "unsafe" or reserved characters in a URL with a URL safe equivalent. The substitutions that should take place after the URL is base64 encoded:
/is replaced by
+is replaced by
=characters are removed
If you're seeing URL non-safe characters in the URL, making the substitions above will correct the issue.
Source is not yet deployed
Most of the time, this issue means that your Source is not yet deployed.
You can either wait until the Source is fully deployed (10-15 minutes) or check to ensure that you're using the right Source URL.
SSL related issue
503 error most commonly indicates an SSL error.
To check if this is the issue, use this tool to diagnose your SSL certificate:
It should be showing all green and should not have any warnings. If you find any warnings, fixing them will resolve the
If you're using Incapsula as a CDN and you're experiencing a
503 error when serving your images, this is most likely due to an invalid cookie header being sent to our servers.
Incapsula deliberately does this as a way to determine if the requester is a bot or a human, but unfortunately our software requires that all headers contain only valid characters.
To fix this, you can ask them to disable this feature for your account or you can change your set up so that imgix bypasses your CDN directly.