CDN for images
One source image. Every layout, at the edge.
Product, editorial and social imagery is often the heaviest part of a page. Generating every derivative at origin, then shipping the original JPEG worldwide, wastes bandwidth and origin CPU.
Cache images at Cloud CDN and convert, resize and crop at delivery time. Keep a single source file. Serve WebP or AVIF where the client supports them.
Why teams use Aptranet
What CDN for images looks like on this network.
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
WebP and AVIF without a second pipeline
Convert at the edge for up to 85% file-size savings at a given quality, without storing every format.
Images from 210+ locations
Repeat views are served from cache with 30 ms average worldwide latency.
Query-string variants
Resize and crop through query strings instead of baking every breakpoint into storage.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud CDN configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Point the media hostname at Cloud CDN
Pull the existing image origin — CMS uploads, a files host or an app disk.
- 2Enable transformation
Convert to WebP or AVIF and resize from URL parameters.
- 3Cache aggressively
Immutable image URLs can use long TTLs. Purge when a source file is replaced.
- 4Cut over the media domain
Map TLS and DNS once variants look correct on a test hostname.
Outcomes
What changes once the hostname is on Aptranet.
- Images are cached on 210+ PoPs
- Source files stay untransformed at origin
- WebP and AVIF can be negotiated at the edge
- Replaced files can be purged by URL
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
No. Keep a high-quality source and convert at delivery time. You can still store more than one format if you already do.
Yes. Use query-string resize and crop per layout instead of separate originals.
Purge the URL or directory. Versioned filenames avoid purge entirely.
Yes. See CDN for WordPress, WooCommerce and Magento for CMS-specific notes.