From c74e822435ace302ba5d0d969042b2eb75ca58f0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lu=C3=ADs=20Cardoso?= Date: Wed, 1 Jul 2026 16:09:31 +0100 Subject: [PATCH] [Images] Update overview.mdx Hello team, Per docs https://developers.cloudflare.com/cache/concepts/cache-responses/ --- .../docs/images/optimization/transformations/overview.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/images/optimization/transformations/overview.mdx b/src/content/docs/images/optimization/transformations/overview.mdx index d623c6694db..8979e19acf8 100644 --- a/src/content/docs/images/optimization/transformations/overview.mdx +++ b/src/content/docs/images/optimization/transformations/overview.mdx @@ -30,9 +30,9 @@ To serve transformations on your zone, you must first enable the feature: When the browser requests a transformed image, Cloudflare checks the edge cache for a previously optimized version with the same parameters: -**On a cache hit** — Cloudflare serves the optimized image directly from the edge without contacting the origin or re-applying the optimization parameters. +**On a cache [HIT](/cache/concepts/cache-responses/#hit)** — Cloudflare serves the optimized image directly from the edge without contacting the origin or re-applying the optimization parameters. -**On a cache miss** — Cloudflare fetches the original image from the source origin, applies the requested parameters (e.g. `format`, `width`, `quality`), caches the transformed result, and serves it to the browser. The original image is also cached to speed up future transformations of the same source. +**On a cache [MISS](/cache/concepts/cache-responses/#miss)** — Cloudflare fetches the original image from the source origin, applies the requested parameters (e.g. `format`, `width`, `quality`), caches the transformed result, and serves it to the browser. The original image is also cached to speed up future transformations of the same source. Each unique combination of source image and parameters is cached and billed separately. The first request for each unique version within a calendar month is billed as one [unique transformation](/images/optimization/features), regardless of cache status. Subsequent requests for this transformation do not incur billable usage within the same calendar month.