Adaptive Image Servlet

Learn how the Core Components uses the Adaptive Image Servlet for image delivery and how you can optimize its use.

Adaptive Image Servelt or Web-Optimized Image Delivery?

The Image Core Component can use two methods to delivery images.

  • The Adaptive Image Servlet is the default.
  • Web-optimized image delivery is available to AEMaaCS and reduces download size by 25% on average.

This document describes the default Adaptive Image Servlet.


By default, the Image Component uses the Core Component’s Adaptive Image Servlet to deliver images. The Adaptive Image Servlet is responsible for image processing and streaming and can be leveraged by developers in their customizations of the Core Components.

Optimizing Rendition Selection

The Adaptive Image Servlet will try to pick the best rendition for the requested image size and type. It’s recommended that DAM renditions and Image component allowed widths are defined in sync so that the Adaptive Image Servlet does as little processing as possible.

This will improve performance and avoid some images not being correctly processed by the underlying image processing library.

Using Last-Mofified Headers

Conditional requests via the Last-Modified header are supported by the Adaptive Image Servlet, but the caching of the Last-Modified header needs to be enabled in the Dispatcher.

The AEM Project Archetype’s sample Dispatcher configuration already contains this configuration.

On this page