CDN image optimization

Convert images to WebP or AVIF, resize and crop at the edge with Aptranet Cloud CDN, and cache the result on 210+ points of presence.

210+Points of presence worldwide
200+ TbpsNetwork capacity
30 msAverage latency worldwide
85%Average cache hit ratio

CDN image optimization

Transform images at delivery time, not in a batch job.

Most teams still generate derivative images at upload. That pipeline lags new layouts and still ships overweight originals to the browser.

Keep a single source image. Cloud CDN converts to WebP or AVIF, resizes and crops from query strings, then caches each variant at the edge.

Why teams use Aptranet

What CDN image optimization 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.

Up to 85% smaller at a given quality

WebP and AVIF conversion happens at the edge from one source file.

Layout-specific sizes from a URL

Resize and crop through query strings instead of storing every breakpoint.

Variants cached globally

Each derived image is stored on 210+ PoPs after the first request.

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.

  1. 1
    Point the media origin at Cloud CDN

    CMS uploads, a files host or an application disk over HTTPS.

  2. 2
    Enable conversion and resize

    Turn on WebP/AVIF and query-string geometry for the media hostname.

  3. 3
    Update templates to request sizes

    Product cards, heroes and OG images can each ask for the width they need.

  4. 4
    Cache and purge by source URL

    When the original changes, purge it so variants rebuild.

Outcomes

What changes once the hostname is on Aptranet.

  • One source image supports every layout
  • WebP and AVIF are created at the edge
  • Derived files are cached worldwide
  • Replaced originals can be purged

Frequently Asked Questions

Serve a compatible format for the client. Conversion is a delivery-time choice, not a stored-only format.

Yes. Many teams keep the CMS as the source and let Cloud CDN handle output formats and sizes.

Yes. Balance visual fidelity against page weight per template rather than one global derivative.

No. A DAM still stores rights and originals. Cloud CDN is the delivery and transformation layer.

Put CDN image optimization on the Aptranet edge.

Get started in the Management Console, or talk through origin, DNS and cutover with Aptranet.