What is an Image Derivative?
An image derivative is a generated version of a source image with changed dimensions, format, crop, quality, effects, or other properties. It remains associated with the source while serving a distinct delivery or presentation need.
How Image Derivatives work
A derivative is best treated as a reproducible asset whose identity includes its master, transformation recipe, processor version, and output settings. It may be materialized in storage or generated on demand and cached near viewers. Digital asset systems use this relationship to deliver crops, previews, print renditions, and device-specific variants without modifying the master. Lifecycle rules must connect replacement or deletion of the source to every dependent rendition.
Key facts
- 1A cache key that omits crop coordinates, orientation handling, color profile, or encoder version can serve a technically valid but incorrect prior rendition.
- 2Derivatives should normally be generated from the highest-quality master, because chaining one resized or lossy rendition into another accumulates avoidable damage.
- 3A focal point or safe-area instruction is source metadata, while the resulting crop is a derivative; keeping them separate permits new sizes without manual recropping.
When Image Derivatives matter
Generate named derivatives for stable requirements such as thumbnails, previews, and responsive breakpoints instead of transforming each request arbitrarily. When the source changes, invalidate or regenerate its derivatives to prevent stale output.
Common use cases for image
These examples cover image broadly, not specifically Image Derivatives.
- Generating responsive website images, thumbnails, avatars, social cards, and product imagery.
- Standardizing user uploads to safe dimensions, formats, and metadata policies.
- Applying crops, overlays, watermarks, background operations, or visual analysis at scale.
Working with image
This guidance covers image broadly, not just Image Derivatives.
Image software decodes the source into pixels, applies spatial or color operations, and encodes the result. Resize filters, crop coordinates, operation order, and output settings determine both appearance and file size.
Image operations interact with resolution, aspect ratio, alpha, color profiles, orientation, and compression. Test the complete sequence because changing the order of resize, crop, sharpen, and encode operations can change the result.
What you gain
- One source can produce consistent variants for different layouts and devices.
- Automated optimization reduces bytes without requiring editors to prepare every derivative.
- Explicit transformation rules make crops, dimensions, and formats reproducible.
What it costs
- Smaller dimensions and stronger compression reduce transfer size but can remove useful detail.
- Automatic crops scale well but can cut off important subjects when detection or focal information is wrong.
- Wide-gamut, HDR, and transparent assets need an end-to-end path that preserves those properties.
Before production
- 1Test representative dimensions, transparency, color profiles, orientation, and animated inputs.
- 2Compare visual quality at the actual display size, not only at 100% zoom.
- 3Set explicit crop, fit, and upscaling rules so edge cases remain predictable.