HTTP Status Code Overview

If you receive an error code for an image request, you can find the meaning and possible causes below.

In case you encounter an error that is not listed on this page, please feel free to contact support.

You can also view our status page for any ongoing incidents.

Rendering API Errors

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.
There is a default parameter on your Source causing an issue.
- Having a mark or blend referencing an image in the same Source will cause a loop due to how the mark works. If you are using a mark or blend, make sure it’s referencing an image in a different Source.
Using a base64 parameter without base64 encoding will return a 400 response.
The base64 encoded string is not URL safe. Make sure to replace + with - and / with _ and remove any trailing =. Read more here.

The 402 status code indicates one of two problems:

payment_required: Your account has been disabled due to nonpayment. Please visit the dashboard to check your outstanding invoices to make a payment or update your credit card.
plan_limits_exceeded: Your account has exceeded the usage limits of your current plan. Please visit the dashboard to upgrade your plan.

The image is requested from a Source with the Secure URL option turned on, but the s signature is either missing or invalid.
- Either turn off secure URLs in your Source settings or sign the image using the dashboard tools
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.

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 S3 Access Key and Access Key ID credentials entered in imgix are valid and that the IAM user has sufficient permissions to access the object
- The image can be accessed by imgix and is not being blocklisted
- 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.

The URI is too long. The current limit is 8000 characters.
Due to certain browser limitations, we recommend using a maximum of 2048 characters.

The requested image has failed internal verification. This is usually caused by a corrupt image.

You are serving an non-renderable image (e.g., an HTML file). If you are on a paid plan, you can contact support to enable the serving of non-renderable assets.
A parameter in the query string contains an invalid value, e.g. w=0.
The image (or watermark/blend) is not able to be processed
- This can be due to the file type or file corruption. You can verify this by saving the image locally and by installing imagemagick’s command-line tool. Once installed, you can run the below command line to diagnose the issue:
```
magick identify -verbose image_name.png
```
You are using an SVG in the mark/blend URL in a Source where SVG rendering is not enabled
A color profile may be missing from the image (check the image metadata)
The GIF you’re processing is too large either in frame count or individual frame size

The asset is being processed and is not yet available. Please wait a few seconds and try again
- This can occur from chaining AI transformation requests

An error occurred attempting to fetch the image from the Origin. (E.g., 5xx response at Origin)

Temporary unavailability due to processing requirements, i.e., a requested GIF is too large.