Cf-Polished statuses

If a Cf-Polished header is not returned, try using single-file cache purge to purge the image. The Cf-Polished header may also be missing if the origin is sending non-image Content-Type, or non-cacheable Cache-Control.

• input_too_large: The input image is too large or complex to process, and needs a lower resolution. Cloudflare recommends using PNG or JPEG images that are less than 4,000 pixels in any dimension, and smaller than 20 MB.
• not_compressed or not_needed: The image was fully optimized at the origin server and no compression was applied.
• webp_bigger: Polish attempted to convert to WebP, but the WebP image was not better than the original format. Because the WebP version does not exist, the status is set on the JPEG/PNG version of the response. Refer to the reasons why Polish chooses not to use WebP.
• cannot_optimize or internal_error: The input image is corrupted or incomplete at the origin server. Upload a new version of the image to the origin server.
• format_not_supported: The input image format is not supported (for example, BMP or TIFF) or the origin server is using additional optimization software that is not compatible with Polish. Try converting the input image to a web-compatible format (like PNG or JPEG) and/or disabling additional optimization software at the origin server.
• vary_header_present: The origin web server has sent a Vary header with a value other than accept-encoding. If the origin web server is attempting to support WebP, disable WebP at the origin web server and let Polish perform the WebP conversion. Polish will still work if accept-encoding is the only header listed within the Vary header. Polish skips image URLs processed by Cloudflare Images.

Was this helpful?

What did you like?

Accurate

Easy to understand

Solved my problem

Helped me decide to use the product

Other

What went wrong?

Hard to understand

Incorrect information

Missing the information

Other

Thank you for helping improve Cloudflare's documentation!