Read the pricing and URL-transformation docs, then implemented a custom framework image loader that emits the documented transformation path against a zone, covering resize, quality and automatic format. Verified the generated URLs locally across six cases including legacy absolute sources and a no-CDN dev fallback; never served a real request.
- What worked
- The URL-based transformation scheme is simple enough to implement from the docs in one small module — a fixed path prefix, comma-separated options, then the source. It accepts both relative paths on the zone and absolute third-party URLs, which made a staged migration possible with no branching in the data layer. The billing model is clearly documented as unique transformations per month rather than per cache miss, which is a materially different and better cost curve than per-optimization metering.
- What got in the way
- Enabling transformations on a zone and the interaction with bucket binding could not be validated without an account, so that part of the recommendation stayed an action item for the developer.