Optimizing Image Delivery with Cloudflare Image Resizing and R2
Optimizing image delivery for websites is crucial for enhancing user experience. Since images often represent the largest portion of a website’s data, they significantly affect page load times, search engine rankings, delivery costs, and overall performance. This reference architecture diagram will guide you through a straightforward, scalable, and high-performance solution. By simply adjusting the URL string to specify image size and quality, you can cache and deliver the optimized image to any user requesting that format. Below are the Cloudflare components involved in this solution:
- Cloudflare CDN ↗ - Leverage Cloudflare’s Global Network ↗ to cache your transformed images for fast and reliable delivery to your end users.
- Cloudflare Images ↗ - Leverage Cloudflare Images to resize, optimize and transform your images that are stored in an object storage solution such as Cloudflare R2. Transformations are performed based on a specifically-formatted URL which requires minimal refactoring to your application to support.
- Cloudflare R2 Object Storage ↗ - R2 allows users to store a large amount of unstructured data, and in this use case will be used for storing our original images (best quality) for transformation.
- Cloudflare Transform Rules - If you’re migrating from another solution to Cloudflare, Transform Rules allows you to Rewrite the URL from another solutions syntax to a Cloudflare specific syntax, which reduces the complexity of migration.
- User Request: The user sends an HTTP request for an image (image.jpg), specifying transformations like width and quality directly in the URL as a comma-separated list of options.
- Cache Hit: Cloudflare processes the request at the point of presence closest to the user. It first checks if the requested image transformation is already in Cloudflare’s Cache. If so, the image is immediately returned to the user, eliminating the need for further processing. If not, the request moves to the next step.
- Transform Rules (optional): If you’re migrating from another images solution it may be necessary to rewrite the URL path and query string with a rewrite so that you can avoid any complex refactoring at the application level to assist with the migration. Both Dynamic and Static rewrites are supported, with dynamic rewrites supporting complex expressions to support a multitude of URL rewrites.
- Cache Miss - R2: If the requested image is not available in Cloudflare’s Cache, then the request is sent to the origin, which in this scenario is Cloudflare’s R2 Object Storage platform. Only the original images are stored in R2, no resized variants are stored in the R2 bucket, which makes operating R2 without object lifecycle rules less onerous.
- Transform Image: Based on the URL syntax sent in step 1 or transformed in step 3, Cloudflare Images transforms the image and sends it to the Cache before serving back to the end user with the requested image.
You can easily convert and resize images by requesting them through a specifically-formatted URL. This section explains the URL structure for image transformation, referring back to the diagram and detailing each URL component:
- Part 1 - Your specific domain name on Cloudflare, this is the Zone you onboarded to Cloudflare and where your website or images are served from. e.g. https://www.mywebsite.com/ ↗
- Part 2 - A fixed prefix that identifies this is a special path handled by Cloudflare’s built-in Worker.
- Part 3 - A comma-separated list of options for the image, such as width=80,quality=75
- Part 4 - Absolute path on the origin server. For example: /uploads/image.jpg
The final URL used in the request would look like this:
https://www.mywebsite.com/cdn-cgi/image/width=80,quality=75/uploads/image.jpg