A variable product with 6 colors and 4 sizes can have up to 24 image slots in WooCommerce, though in practice many variations share the same image (color changes the photo, size usually doesn't). Multiply that by five presets, product_card, product_page, category_banner, mobile_thumbnail, and manufacturer_logo, and a naive pre-generation strategy would need to render dozens of variants before a single visitor ever sees the product.
ImagePipe doesn't work that way. Variants are computed on demand: the first time a specific combination of source file, size, resize mode and format is requested, it's generated once and written to the permanent disk cache. Every request after that, for that exact combination, is served straight from the cache. If a shopper never selects the "green, size L" variation, ImagePipe never spends CPU time or disk space generating the images tied to it.
This matters directly when you add a new color to an existing product. There's no batch job to run and no waiting period, the new variation's images simply get cached the first time a customer, or you, browsing the product page, triggers them, typically in a few hundred milliseconds for the first request and instantly afterward.
Because formats are also negotiated per request via the browser's Accept header, the same variation can exist in the cache as WebP for one visitor and AVIF for another, again only for the formats actually requested, not every possible combination up front.