What is the difference between Cloudflare Images and Cloudflare Image Resizing?

Cloudflare Images is storage plus delivery plus transforms, aimed at assets you upload into Cloudflare. Remote transformations (optimizing files that still live on your origin) use the Images Transformed meter. PicPerf’s default path is closer to remote fetch: keep files where they are, prefix the URL.

Which is cheaper, Cloudflare Images or PicPerf?

It depends on variants and traffic. Cloudflare’s free tier covers 5,000 unique transformations per month; paid is about $0.50 per 1,000 unique transforms, $5 per 100,000 stored, $1 per 100,000 delivered. PicPerf is $5/month for 500 unique images, then $0.01–$0.02 per extra unique file, no delivery cap. Many variants of one file can run up Cloudflare transform counts; PicPerf still counts that file once.

Do I need a Cloudflare account to use PicPerf?

No. PicPerf is a separate image CDN. You can keep Cloudflare as your DNS and CDN and send only image URLs through PicPerf. For whole-page HTML optimization, use PicPerf Turbulence. See PicPerf vs. Turbulence.

When should I stay on Cloudflare Images?

Stay if you already upload into Cloudflare’s image store, you build variants from Workers, or you want one vendor for DNS, WAF, and media. Switch to PicPerf if you do not want to migrate originals, you dislike three billing meters, or you want built-in image sitemaps and broken-image alerts without extra Cloudflare products.

Cloudflare Images vs. PicPerf

Cloudflare Images meters storage, delivery, and unique transformations. PicPerf is a drop-in image CDN with prefix setup, unique-image pricing, and no bandwidth cap.

By Alex MacArthur, builder of PicPerf · Published August 31, 2026

Bottom line: Cloudflare Images stores and transforms files inside Cloudflare and bills unique transformations, stored images, and deliveries separately. PicPerf is a standalone image CDN: prefix existing URLs (or upload), convert to AVIF/WebP when smaller, and pay per unique file with no bandwidth cap. Choose Cloudflare Images if files already live there; choose PicPerf for drop-in optimization without a three-meter bill.

	PicPerf	Cloudflare Images
Setup	URL prefix, upload, or WordPress plugin	Upload to Cloudflare and/or enable remote transforms
Keep files on your origin	Yes. Prefix is first-class	Possible via remote transforms; hosted path wants uploads
Formats	AVIF/WebP when smaller than the original	WebP, AVIF, and other output formats via transforms
Pricing unit	Unique source file ($5 for 500, then $0.01–$0.02)	Transforms + stored + delivered (separate meters)
Bandwidth / delivery cap	None	Delivered images billed at $1 / 100,000 (hosted path)
Requires Cloudflare	No	Yes
Image sitemap / broken-image alerts	Built in	Not the same product; roll your own
Auto resize to rendered size	Yes. PicPerf measures displayed dimensions	You define variants or transform params

Cloudflare Images and Cloudflare the CDN

Cloudflare the CDN is still the right default network. Cloudflare Images is an optional media product with its own meters. Mixing them up is how people compare PicPerf to “Cloudflare” and conclude they already have an image CDN when they only have Polish or a free zone. For the network-versus-HTML rewrite question, see Turbulence vs. Cloudflare.

Why Teams Look at PicPerf Instead

Unique transformations count every distinct source-plus-params combo. A hero with six widths and two formats is twelve transforms, every month they stay unique in the window. PicPerf still sees one unique image. That is the same predictability argument as Cloudinary vs. PicPerf and Imgix vs. PicPerf. Those pages are the evaluator (“vs.”) versions. If you are already leaving Cloudflare Images, the alternatives hub collects the leaver intent pages.

For a ranked list across vendors, use best image CDN.

Frequently Asked Questions

Yes, if you want image optimization without Cloudflare storage or a Workers-paid transform meter. Cloudflare Images bills unique transformations, stored images, and deliveries as separate counters. PicPerf prefixes existing URLs (or hosts uploads) and charges by unique image, with no bandwidth cap.
Cloudflare Images is storage plus delivery plus transforms, aimed at assets you upload into Cloudflare. Remote transformations (optimizing files that still live on your origin) use the Images Transformed meter. PicPerf’s default path is closer to remote fetch: keep files where they are, prefix the URL.
It depends on variants and traffic. Cloudflare’s free tier covers 5,000 unique transformations per month; paid is about $0.50 per 1,000 unique transforms, $5 per 100,000 stored, $1 per 100,000 delivered. PicPerf is $5/month for 500 unique images, then $0.01–$0.02 per extra unique file, no delivery cap. Many variants of one file can run up Cloudflare transform counts; PicPerf still counts that file once.
No. PicPerf is a separate image CDN. You can keep Cloudflare as your DNS and CDN and send only image URLs through PicPerf. For whole-page HTML optimization, use PicPerf Turbulence. See PicPerf vs. Turbulence.
Stay if you already upload into Cloudflare’s image store, you build variants from Workers, or you want one vendor for DNS, WAF, and media. Switch to PicPerf if you do not want to migrate originals, you dislike three billing meters, or you want built-in image sitemaps and broken-image alerts without extra Cloudflare products.

Related Guides

PicPerf images vs. PicPerf Turbulence When to optimize individual image URLs, when to put the whole site behind the edge, and when to use both.
PicPerf Turbulence vs. NitroPack Two full-site optimizers compared on setup, platform coverage, and scope.
PicPerf Turbulence vs. Cloudflare How an HTML-rewriting edge layer differs from Cloudflare’s CDN and Speed products.
PicPerf Turbulence vs. WP Rocket A platform-agnostic DNS proxy versus a WordPress caching plugin.

Prefix image URLs or upload originals. AVIF/WebP when smaller, resizing, and a 1-year CDN cache.

Start a 14-day Image Trial