Getting Started
CDN Guidelines

CDN Guidelines

imgix combines sophisticated image manipulation, our proprietary caching infrastructure, and the performance improvements of an industry-leading CDN (content delivery network) into a powerful end-to-end service. Our integrated solution gives us full visibility and flexibility over the entire image pipeline, making the service robust and easy to integrate.

With our global delivery network (opens in a new tab), your images will get to your users quickly no matter where they are. No additional CDN is required to cache them and provide a great experience to your end users.

Our CDN POP locations are listed in the table below:

OceaniaEuropeNorth AmericaAsiaSouth AmericaAfrica
Adelaide, AUAmsterdam, NLAshburn, USBangkok, THBogota, COCape Town, ZA
Auckland, NZBrussels, BEAshburn (Metro), USChennai, INBuenos Aires, ARGhana, GH
Brisbane, AUCopenhagen, DKAtlanta, USDelhi, INCuritiba, BRJohannesburg, ZA
Christchurch, NZDublin, IEAtlanta (Metro), USDubai, AEFortaleza, BR
Honolulu, USFrankfurt (Metro), DEBoston, USFujairah Al Mahta, AELima, PE
Melbourne, AUFrankfurt - Interxion, DECalgary, CAHong Kong, CNRio de Janeiro, BR
Perth, AUHelsinki, FIChicago (Metro), USHyderabad, INSantiago, CL
Sydney, AULisbon, PTColumbus, USKolkata, INSao Paulo (Metro), BR
Wellington, NZLondon, GBDallas (Metro), USKuala Lumpur, MY
Madrid, ESDenver, USManila, PH
Manchester, GBDetroit, USMumbai, IN
Marseille, FRGainesville, USOsaka, JP
Milan, ITHouston, USSeoul, KR
Munich, DEKansas City, USSingapore, SG
Oslo, NOLos Angeles (Metro), USTokyo, JP
Palermo, ITMiami, USTokyo (Metro), JP
Paris (Metro), FRMinneapolis, US
Rome, ITMontreal, CA
Sofia, BGNew York City, US
Stockholm, SENew York City (Metro), US
Vienna, ATNewark, US
Palo Alto (Metro), US
Phoenix, US
Portland, US
San Jose, US
Seattle (Metro), US
St.Louis, US
Toronto, CA
Vancouver, CA

If at all possible, we recommend that you not use a third-party CDN on top of the one we provide. Due to the close integration of all components of the imgix service, performance with a third-party CDN may be reduced and some features will not be available.

Having two CDNs participate in each image request will cause initial image renders to take longer, and will have adverse effects on cache hit ratio. Cache hit ratio is the percentage of requests served by the CDN cache versus requests that have to go back to the origin. Adding a third-party CDN increases the chances of an initial miss, because it will not be tuned to match up to our backend systems in the way our CDN is.

Diagram describing impact to hit ratios of adding a third-party CDN

Serving Non-Image Assets

We understand that maintaining one CDN for your images and one CDN for all of your other static assets can be complex, time-consuming, and expensive. However, with imgix, you can also serve all of your non-image assets from the same account you use for your images, or even from the same Source. Any asset not supported as an input file type will be automatically served without any transformation. Assets served in this manner are also cached at the imgix CDN edge nodes for faster delivery to your end users and can be purged in the same way you purge image assets.

Non-image assets are served with gzip compression by default for a smaller payload. Customers can also request to have Brotli compression enabled for even more file size savings.

We also offer the option to disable passthroughs for non-image assets, which will prevent them from being served through our CDN and return an error instead. Contact support to enable this feature.

imgix-Specific Feature Impacts

In addition to the speed hit and greater chance of cache misses with a third-party CDN, the advanced imgix features listed below rely on our integration of optimization logic at the edge caches, and are therefore not available when using a third-party CDN in conjunction with imgix.

Automatic Content Negotiation

The imgix Automatic Content Negotiation technology is a convenient way to serve more modern image formats to end users based on their device and browser with no additional programming required. We do all of the heavy lifting of evaluating whether the client supports advanced image formats (WebP, JPEG XR, etc.) up front at our CDN, to convert as necessary to the best-optimized format for that client on the fly.

Client Hints Support

Please Note: Starting with version 67, Chrome no longer supports sending Client Hints to third-parties origins to prevent them from accessing information that might be unavailable to them otherwise. This feature may return at a later date.

Similarly, our support for Client Hints requires our caching logic so it can direct the server to send the best-sized image to a client or browser based on extra information included in the HTTP request headers. Other CDNs don’t provide the logic required to make these features performant, so we are only able to offer them to customers that use the imgix CDN.


With imgix, you only need a single click or API call to purge an Origin Image and all of its derivatives, and purges typically complete within minutes. Adding a third-party CDN can delay purge times as well as necessitate purging all of your image derivatives separately.

SSL with Custom Domains

imgix offers SSL/TLS by default on all of our standard hostnames (*, and when using our CDN. If you do choose to use a third-party CDN in addition to imgix, you will need to work with that CDN provider to get a certificate for the custom domain you desire, and then point that CDN origin to your source’s hostname.