Image CDN Explained
Resizing and Converting Images at the Edge
An image CDN is a content delivery network service that processes images on the fly. Instead of storing one fixed file for each picture, it accepts a request with instructions, such as a width, a quality level or a format, and returns a matching version. Modern formats such as WebP and AVIF are often much smaller than JPEG or PNG at similar quality, so an image CDN can offer them automatically to browsers that support them.
After the first request, the resized image is cached at the edge like any other file. Later visitors who ask for the same version receive the stored copy, and the processing cost is paid only once for each variant.
How It Differs From a Standard CDN
A standard CDN delivers files in the form they are stored at the origin. If a site needs a phone-sized image and a desktop-sized image, it must create and store both files. An image CDN generates variants from one original. The site keeps a single copy of each picture and requests the size it needs.
One original can therefore serve many URLs. The same product photo might be delivered at a small width to a phone and a larger width to a large monitor, with the page markup choosing which address to load. This removes much of the work of producing and storing every size by hand. Once generated, these variants behave like static files, which is why the ideas in static vs dynamic content caching apply to them.
Example: A Photo-Heavy News Site
A news site publishes hundreds of photos a day. Editors upload one original per image. When a page first requests a thumbnail, a mobile size or a WebP version, the image CDN generates it and caches it at the edge. Popular sizes are generated once and then served from cache, while rarely used sizes are created only when someone asks for them.
The team no longer needs a build step that creates every variant in advance. Storage stays smaller, and a new layout can request a new size without re-uploading any images.
Frequently asked questions
Do I still need to optimise images myself if I use an image CDN?
Usually yes, in part. An image CDN can resize and convert images, but it cannot fix a poor original or decide how images should load on a page. Choosing sensible dimensions, avoiding oversized originals and lazy loading, which means fetching images only as they approach the screen, still matter. The CDN handles delivery while your content choices control the result.
Are image CDNs only useful for large sites?
No. A small site with many product photos or a responsive layout can benefit too. The value grows with the number of images and the range of devices they reach. Processing and delivery are often billed in different ways, which is explained in how CDN pricing works.