{"id":14501,"date":"2026-11-06T09:30:00","date_gmt":"2026-11-06T15:30:00","guid":{"rendered":"https:\/\/infiniteuploads.com\/?p=14501"},"modified":"2026-11-03T11:49:58","modified_gmt":"2026-11-03T17:49:58","slug":"image-cdn-for-wordpress","status":"publish","type":"post","link":"https:\/\/infiniteuploads.com\/blog\/image-cdn-for-wordpress\/","title":{"rendered":"Image CDN for WordPress, What It Is and When You Need One"},"content":{"rendered":"\n

An image CDN is a CDN that also edits the picture on the way out. It resizes the image, compresses it and converts it to a format like WebP or AVIF, on the fly, and it can do that differently for every visitor. If you've been searching for a CDN for images on WordPress, you probably know the symptom. The hero photo shows up last.<\/p>\n\n\n\n

The pattern barely changes from one WordPress site to the next. Somebody uploads a 6000 pixel wide photo straight off a camera, the theme shows it in a 1200 pixel column, and every visitor downloads the whole thing.<\/p>\n\n\n\n

Below I'll cover what an image CDN is, when a WordPress site needs one, the three practical ways to get one, and how to set up and test it. I work on Infinite Uploads, so one of those three ways is ours.<\/p>\n\n\n\n

What an image CDN is<\/h2>\n\n\n\n
The cleanest definition comes from web.dev. Image CDNs specialize in transforming, optimizing and delivering images (web.dev, Use image CDNs to optimize images<\/a>). The image URL says which image to load, and it can also carry parameters like size, format and quality. One original, many variations.<\/p>\n\n\n\n
web.dev says switching to an image CDN can cut image file size by 40 to 80%. That's their range, not mine, and it depends on your starting point.<\/p>\n\n\n\n

How an image CDN differs from a regular CDN<\/h2>\n\n\n\n
A regular CDN is a group of servers spread over many locations that store copies of your files, so a request gets answered by a server near the visitor (MDN glossary: CDN<\/a>). Nearer is faster, since distance affects latency. It serves the same file. A huge JPEG stays a huge JPEG, it just travels a shorter road.<\/p>\n\n\n\n
Think of a chain of warehouses stocking identical boxes. The nearest warehouse ships faster, but the box is the same box. An image CDN is that chain with a packing station in every warehouse. The order comes in, and the packing station sizes the image for that screen, shrinks it, and boxes it in the format that visitor's browser can open.<\/p>\n\n\n\n
web.dev says the changes that matter most are size, pixel density, format and compression, and many image CDNs have an automatic mode that picks them per visitor. Its example is AVIF to Chrome and JPEG to a very old browser.<\/p>\n\n\n\n
For a plain CDN comparison, see our roundup of WordPress CDN services<\/a> and what is the best CDN for WordPress<\/a>. If you offload media to cloud storage, why a CDN is essential with cloud storage<\/a> explains the pairing.<\/p>\n\n\n\n

How an image CDN works on delivery<\/h2>\n\n\n\n
Every time a browser asks for an image, it sends an Accept header listing the image types it can handle (MDN on content negotiation<\/a>). A CDN that reads that header can answer the same URL with AVIF for one browser, WebP for another and the original for an old one. The Vary response header tells caches to keep those versions apart (MDN on Vary<\/a>).<\/p>\n\n\n\n
On Infinite Uploads, our docs describe what happens the first time a visitor requests an image with optimization on (how Image Optimization works<\/a>):<\/p>\n\n\n\n
\n
We choose the best format their browser supports, AVIF first, then WebP, then the original.<\/li>\n\n
We right-size the image to your maximum width, so a large photo isn't sent at full resolution to a small screen.<\/li>\n\n
We compress it at your chosen optimization level and strip unnecessary metadata.<\/li>\n\n
We cache the result on the CDN for every visitor after that.<\/li>\n<\/ol>\n\n\n\n
Your original is never modified. Optimization happens only on the delivered copy, so you can change settings or turn the feature off and your source files stay intact (does Image Optimization change my original files<\/a>). It applies to JPEG and PNG. SVG and GIF are delivered as they are.<\/p>\n\n\n\n
The URL can still end in .jpg while the response is AVIF, because the content-type header, not the extension, tells the browser what it got. I saw that in my own testing, which I wrote up in AVIF vs WebP for WordPress<\/a>.<\/p>\n\n\n\n
When a WordPress site needs an image CDN<\/h2>\n\n\n\n
Here are the signs I'd look for.<\/p>\n\n\n\n
\n
A big, heavy media library.<\/strong> Optimization on delivery covers images you uploaded long ago too, with no re-processing and no re-uploads (Image Optimization features<\/a>).<\/li>\n\n
Visitors far from your host.<\/strong> Distance adds latency. If your server sits in one region and your audience in another, images from a nearby edge help. Your HTML still comes from your host, though.<\/li>\n\n
Slow Largest Contentful Paint.<\/strong> LCP measures how long until the largest image or text block is rendered, and web.dev says to aim for 2.5 seconds or less for at least 75% of page visits (Optimize LCP<\/a>). If your LCP element is an image, file size matters. If it's text, an image CDN won't fix it. Check the LCP breakdown first, since web.dev shows a case where a smaller image only shifts time into render delay.<\/li>\n\n
Oversized uploads.<\/strong> Editors, clients and cameras produce images far bigger than any screen shows. A maximum width fixes that on delivery.<\/li>\n\n
Mobile traffic.<\/strong> web.dev says serving desktop-sized images to mobile devices can use 2 to 4x more data than needed (Serve responsive images<\/a>). If most of your visitors are on phones, that waste adds up.<\/li>\n<\/ul>\n\n\n\n
When you don't need one<\/h2>\n\n\n\n
A brochure site with 20 images already exported at the right size is well served by a decent host. Same if your LCP element is text, or your Core Web Vitals already pass. WordPress has accepted WebP uploads since version 5.8<\/a> and AVIF since version 6.5<\/a>, so a few images in a modern format at sensible sizes leave little to win.<\/p>\n\n\n\n
An image CDN fixes image problems. If you don't have one, don't buy one.<\/p>\n\n\n\n
Three ways to get an image CDN on WordPress<\/h2>\n\n\n\n
What people call a WordPress image CDN usually comes down to one of three setups.<\/p>\n\n\n\n
1. A regular CDN plus a separate image plugin<\/h3>\n\n\n\n
A regular CDN for delivery, plus a plugin that compresses and converts. It works, and it's the cheapest start if you already run both. Our docs point out that most compression plugins modify the files in your Media Library, and two optimizers can compress an image twice, which adds no benefit and can reduce quality (do I still need other image optimization plugins<\/a>).<\/p>\n\n\n\n
2. An image optimization service priced by visits, like Optimole<\/h3>\n\n\n\n
Optimole is a hosted image optimization service and a fair option. On its pricing page<\/a>, checked October 27, 2026, plans are priced by monthly visits. Starter is $19.08 a month billed yearly for 48,000 visits, and Business is $39.08 a month billed yearly for 120,000 visits. It lists a CDN with 450+ locations. Its WordPress.org page<\/a> says it converts to WebP and AVIF where browsers support them without altering the original files on your server. If your traffic is modest and predictable, paying per visit can be cheap.<\/p>\n\n\n\n
3. Infinite Uploads, where offload, CDN and image optimization are one connection<\/h3>\n\n\n\n
With Infinite Uploads you connect your site, offload your media and turn on Image Optimization. Your media is already served from our CDN, which has 119+ points of presence (PoPs), so optimization is a setting on a system that's already wired. We charge by storage and bandwidth, not visits.<\/p>\n\n\n\n
Image Optimization is Business plan only. Business starts at $24\/mo billed yearly ($288\/yr) or $29\/mo billed monthly, for 100 GB of storage and 200 GB of bandwidth. Starter, the smallest paid plan, is 25 GB of storage and 50 GB of bandwidth from $8.25\/mo billed yearly ($99\/yr) or $11\/mo billed monthly, without Image Optimization. We also have a Free plan with 10 GB of storage and 20 GB of bandwidth a month, and paid plans have a 7-day free trial. All of it is on the pricing page<\/a>, which I checked on October 27, 2026.<\/p>\n\n\n\n
Worked example. Your library is 40 GB and your site moves about 90 GB of media a month. Starter lacks Image Optimization, so the cheapest plan that fits both numbers and includes it is Business with 100 GB of storage and 200 GB of bandwidth, $24\/mo billed yearly or $29\/mo billed monthly.<\/p>\n\n\n\n
How to set up an image CDN with Infinite Uploads<\/h2>\n\n\n\n
Nearly every option can stay at its default, so setup takes minutes.<\/p>\n\n\n\n
\n
Connect your site to Infinite Uploads and offload your media.<\/li>\n\n
Open the Infinite Uploads screen in your WordPress dashboard and scroll to the Image Optimization section.<\/li>\n\n
Turn Image Optimization On. The full set of options appears.<\/li>\n\n
Choose an optimization level.<\/li>\n\n
Set a maximum image width.<\/li>\n\n
Add exclusions if you need any.<\/li>\n\n
Click Save Settings.<\/li>\n\n
Click Purge CDN Cache in the Account & Usage section if you want the new settings applied to images that are already cached.<\/li>\n<\/ol>\n\n\n\n
That section holds the optimization level, the next-gen formats (AVIF and WebP, both on by default), the maximum image width, metadata stripping (on by default) and the exclusions box. The full steps are in enabling Image Optimization<\/a>.<\/p>\n\n\n\n
$\"Infinite$
The Image Optimization section of the Infinite Uploads screen in the WordPress dashboard.<\/figcaption><\/figure>\n\n\n\n
Optimization level.<\/strong> Maximum compression gives the smallest files, though very detailed images may soften slightly. Balanced is the default, with no visible quality difference on almost all images. Highest quality means larger files and suits photography portfolios. Start with Balanced (choosing an optimization level<\/a>).<\/p>\n\n\n\n
Maximum image width.<\/strong> Any value from 256 to 2560 pixels, with 2560 as the default and ceiling. Lower it (to 1600, say) if your theme never shows images very large, but keep it at least as wide as the widest spot an image appears (setting a maximum image width<\/a>).<\/p>\n\n\n\n
Exclusions.<\/strong> Most sites never need these. If a logo must be delivered exactly as uploaded, add one entry per line, by filename like logo.png or by path like \/2026\/01\/. Matching checks whether the entry appears anywhere in the image's path, so keep entries specific (excluding images from optimization<\/a>).<\/p>\n\n\n\n
Purge the cache after changing settings.<\/strong> Changes apply to each image the next time it's requested and re-cached. To apply them right away, use the Purge CDN Cache button at the top of the Account & Usage section. It's limited to once per hour (purging the CDN cache<\/a>).<\/p>\n\n\n\n
Your CDN URL shows in the Account & Usage section of the Infinite Uploads screen, and it looks like https:\/\/xxxxx.infiniteuploads.cloud\/ (setting up a custom CDN URL<\/a>).<\/p>\n\n\n\n
$\"The$
The CDN URL card in the Account & Usage section of the Infinite Uploads screen.<\/figcaption><\/figure>\n\n\n\n
On Business plans you can swap that for a subdomain on your own domain, like cdn.yoursitename.com. You create a CNAME record at your DNS provider, then paste the new domain into the Custom CDN Domain section for your site in your account on infiniteuploads.com. SSL is automatic. With Cloudflare, set the record to DNS only. web.dev adds a reason to do this: your own domain makes it easier to switch image CDNs later, since no URLs change.<\/p>\n\n\n\n
How to test that your image CDN works<\/h2>\n\n\n\n
\n
Check the file URL.<\/strong> In Media > Library, click an image. The File URL should use the Infinite Uploads URL assigned to your site.<\/li>\n\n
Check the format.<\/strong> In a modern browser, right-click an image, choose Inspect and open the Network panel. Reload and click the image request. The response Content-Type should be image\/avif or image\/webp instead of image\/jpeg or image\/png. An old browser getting the original is the fallback working as designed.<\/li>\n\n
Compare file size.<\/strong> Your Media Library shows the original's size, and the Network panel shows what the browser received. In our own test of a gaming site's library we measured 54% to 71% smaller, with one 584 KB JPEG coming out at 268 KB as WebP and 171 KB as AVIF (Image Optimization features<\/a>). That is one site, so your numbers will vary.<\/li>\n\n
Run a speed test.<\/strong> Test the same page in PageSpeed Insights<\/a> before and after, more than once, because the first request after a change rebuilds the cached copy. Watch LCP. If Lighthouse and real user data disagree, web.dev says the real user data is likely more accurate.<\/li>\n<\/ol>\n\n\n\n
Who this is not for<\/h2>\n\n\n\n
If you have a small site with a few images already sized and compressed, skip this. If your traffic is small, Optimole's Starter at $19.08 a month billed yearly may cost less than our Business plan at $24\/mo billed yearly, and if you're happy there, don't move. Our optimization works on media served from our CDN, so it isn't for you if you won't offload your media. It also won't touch SVG, GIF or video.<\/p>\n\n\n\n
Image CDN FAQ<\/h2>\n\n\n\n
What is an image CDN?<\/h3>\n\n\n\n
A content delivery network that also transforms images. It serves them from a location near the visitor like any CDN, and it resizes, compresses and converts them to formats like WebP and AVIF on the fly.<\/p>\n\n\n\n
Is a CDN the same as image optimization?<\/h3>\n\n\n\n
No. A CDN decides where a file is served from. Image optimization changes the file itself. An image CDN does both on delivery, but you can have a CDN with no optimization, and a plugin with no CDN.<\/p>\n\n\n\n
Does an image CDN help SEO and Core Web Vitals?<\/h3>\n\n\n\n
It can help Core Web Vitals when images are what's slowing your page, mainly LCP. Google recommends good Core Web Vitals for success with Search and says they align with what its core ranking systems seek to reward (Google Search Central<\/a>). It's not a ranking shortcut.<\/p>\n\n\n\n
Do I need an image CDN for a small site?<\/h3>\n\n\n\n
Usually not. With few images that are already sized and compressed, there's little to fix.<\/p>\n\n\n\n
Will an image CDN change my original files?<\/h3>\n\n\n\n
Not ours. Infinite Uploads Image Optimization never modifies your originals. It optimizes only the delivered copy, and turning it off goes back to serving your originals (details in the docs<\/a>).<\/p>\n\n\n\n
Want to see it on your own images? You can try any Infinite Uploads plan free for 7 days, a card is required, and the trial includes the features of the plan you pick, so choose Business to test this.<\/p>\n\n\n\n
\n
Start your 7-day free trial<\/a><\/div>\n<\/div>\n<\/body><\/html>\n","protected":false},"excerpt":{"rendered":"
An image CDN resizes, compresses and converts your images on delivery. Here is how it differs from a regular CDN, when a WordPress site needs one, and how to set it up and test it.<\/p>\n","protected":false},"author":3787,"featured_media":14500,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"wds_primary_category":0,"footnotes":""},"categories":[26],"tags":[174,49,119,28,23,173],"class_list":["post-14501","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-performance","tag-avif","tag-cdn","tag-images","tag-optimization","tag-performance","tag-webp"],"acf":[],"_links":{"self":[{"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/posts\/14501","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/users\/3787"}],"replies":[{"embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/comments?post=14501"}],"version-history":[{"count":2,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/posts\/14501\/revisions"}],"predecessor-version":[{"id":14931,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/posts\/14501\/revisions\/14931"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/media\/14500"}],"wp:attachment":[{"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/media?parent=14501"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/categories?post=14501"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/infiniteuploads.com\/api\/wp\/v2\/tags?post=14501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Image CDN FAQ<\/h2>\n\n\n\n

What is an image CDN?<\/h3>\n\n\n\nA content delivery network that also transforms images. It serves them from a location near the visitor like any CDN, and it resizes, compresses and converts them to formats like WebP and AVIF on the fly.<\/p>\n\n\n\n

Is a CDN the same as image optimization?<\/h3>\n\n\n\nNo. A CDN decides where a file is served from. Image optimization changes the file itself. An image CDN does both on delivery, but you can have a CDN with no optimization, and a plugin with no CDN.<\/p>\n\n\n\n

What is an image CDN?<\/h3>\n\n\n\n
A content delivery network that also transforms images. It serves them from a location near the visitor like any CDN, and it resizes, compresses and converts them to formats like WebP and AVIF on the fly.<\/p>\n\n\n\n

Is a CDN the same as image optimization?<\/h3>\n\n\n\n
No. A CDN decides where a file is served from. Image optimization changes the file itself. An image CDN does both on delivery, but you can have a CDN with no optimization, and a plugin with no CDN.<\/p>\n\n\n\n