Skip to main content

Resizing Algorithm

Use the resizing_algorithm transformation to choose the resize kernel used for a delivered image variant.

Overview​

Most image delivery workflows can use the default resize behavior. Choose a specific algorithm when you need predictable resizing characteristics for screenshots, generated graphics, pixel-art style images, or image comparison workflows.

Syntax​

FieldValue
Canonical parameterresizing_algorithm
Aliasra
Accepted valuesnearest, cubic, mitchell, lanczos2, lanczos3

Example​

https://cdn.imgwire.dev/{organization_id}/{environment_id}/{image_id}?width=320&resizing_algorithm=lanczos3
image.url({
  width: 320,
  resizing_algorithm: 'lanczos3',
  format: 'auto',
  quality: 'auto',
});
imgwire images url img_123 --width 320 --resizing-algorithm lanczos3

Live examples​

NearestMitchellLanczos3
Demo image resized with nearest neighbor kernelDemo image resized with Mitchell kernelDemo image resized with Lanczos3 kernel

Best practices​

  • Use the default unless you have a visual reason to choose a kernel.
  • Use nearest for pixel-art style assets where hard edges are intentional.
  • Compare kernels at the final rendered size because differences may be subtle.

Common mistakes​

  • Changing the resize kernel to fix a low-quality source image.
  • Using nearest for photos and expecting natural-looking results.
  • Tuning the algorithm before setting the correct dimensions and quality.

Last updated at: May 9, 2026