PROVIDER Β· Image service on the same network as the CDN
Cloudflare Images
Launched in 2021, Cloudflare Images handles image storage, predefined variants, and delivery, billing only on stored and delivered images on the Cloudflare network, ideal for sites already using its CDN.
4.2pts
Pros
Cons
Product Information
Detailed Notes
Overview
Cloudflare Images launched in 2021 as part of the Cloudflare developer platform and is operated from the United States. Its scope is deliberately narrow, handling storage, variants, and delivery without complex image processing or video workflows, keeping both cost and complexity minimal for sites already on Cloudflare.
Pricing is its clearest advantage, charged per stored image plus per delivered image rather than by transformation parameter or credit. For sites already using Cloudflare for CDN and DNS, this Media Optimization layer becomes one more origin inside the existing network without extra hops.
The limits are explicit. Variants are predefined and named rather than arbitrary parameter combinations, there is no advanced cropping, colour management, or video, and mainland China performance follows the Cloudflare network overall, which is rarely a strength.
Core Strengths
- Billed only on stored and delivered images, not parameters or credits, so cost is predictable
- Shares the network with Cloudflare CDN, DNS, and Workers, making adoption trivial for existing users
- Named variants such as thumbnail, banner, and cover are defined once and referenced by name
- Upload APIs and signed URLs restrict access and deter hotlinking
Product Ecosystem
Storage and variants
Upload then define variant sizes and cropping in the dashboard, referencing them by name. The variant count is limited, which suits stable page structures, while arbitrary sizes fit parameterised alternatives better.
Delivery and access control
Delivery runs over the Cloudflare network with signed URLs and hotlink protection. Signed URLs are mandatory for paid content, since a leaked original link cannot be recalled.
Drawbacks
- Variants must be predefined without arbitrary parameter combinations, less flexible than parameter-based processing
- No advanced cropping, colour management, or video processing
- Mainland China performance follows the Cloudflare network and is rarely an advantage
- Per-image billing climbs noticeably at large volumes, so compare against bandwidth-based models
Use Cases
- Sites already on Cloudflare (β β β β β) - Same-network adoption keeps routing and configuration minimal
- Content sites with stable layouts (β β β β ) - Fixed variants cover listings, detail pages, and thumbnails
- Needing hotlink and signed access (β β β β ) - Signed URLs protect paid content directly
- Work needing arbitrary sizes or advanced processing (β β ) - Predefined variants and capability limits bite
Pricing
| Plan | Price | Scope |
|---|---|---|
| Storage | Per image | Billed monthly per 100,000 stored images |
| Delivery | Per image served | Billed per 100,000 deliveries |
| Variants | Included | Reads are not charged separately |
Billing has only storage and delivery, with no transformation charge, the key difference from credit-based plans. Sites with large libraries should model storage closely, since per-image billing becomes visible past a hundred thousand files.
FAQ
-
How does it relate to the free CDN? The free CDN caches images from your own origin, while Images provides managed storage and variant generation. With a stable origin and size strategy, the CDN alone may be cheaper.
-
What if predefined variants are not enough? Use Workers for edge processing or keep Images as origin behind an external transformation layer. Variant count and cropping are fixed enough that multi-size scenarios outgrow it.
-
Can it replace image optimisation plugins? Partly, through sensible variant sizing and formats. It does not do content-aware compression, so control source quality at upload time.