There is a version of your website you have probably never seen.
It is the one loading for someone six thousand miles from your server, on the same page you tested this morning and called fast.
That version is slower. Not because your images are heavy, but because they are far away.
As of today, ThumbPress has an answer for it.
The Image CDN Is Live on Every Pro Plan
Starting September 1, 2026, the ThumbPress Image CDN is available on every Pro plan at no extra cost.
Turn it on from your ThumbPress dashboard and your images get cached across a global edge network. Each visitor loads them from the location closest to them, rather than making a trip to your origin server.
No DNS changes. No nameserver surgery. No separate CDN account to shop for, pay for, and configure.
CDN storage is included with your plan:
| Plan | Sites | CDN storage | Plan |
| Personal | 1 site | 10 GB | Personal |
| Professional | 5 sites | 50 GB | Professional |
| Agency | Unlimited | 100 GB | Agency |
Storage is the only thing that scales with your tier. The feature itself is the same on all three.
On the free plugin? The Image CDN is a Pro feature. See ThumbPress Pro plans and turn it on today.
Why Distance Is the One Thing Compression Cannot Fix
You can compress an image to a quarter of its size. You cannot make it travel any less far.
Your hosting server sits in one physical location. Every image request from every visitor has to reach it, and the further away they are, the longer that takes. It shows up worst on image-heavy pages, where a dozen files queue up before the page feels done.
It is also easy to miss because you are usually testing from near your own server.
The cost is measurable. Largest Contentful Paint, one of Google’s Core Web Vitals, is very often a hero image or a product photo. In a 2021 A/B test, Vodafone Italy improved LCP by 31% and saw an 8% lift in sales.
Compression shrinks the file. A CDN shortens the trip. You want both, which is why the CDN sits alongside the compression and format tools you already have in ThumbPress rather than replacing them.
What the CDN Actually Covers?
ThumbPress CDN goes beyond serving a few image files. It covers your existing media library, responsive image sizes, and WooCommerce product images, so your site’s images are consistently delivered from the edge.
(i) Your existing library, not just new uploads
ThumbPress pushes your current media library to the CDN in the background, with a progress bar you can cancel and resume without losing your place.
A site with ten years of uploads does not have to sit through one long migration window, and a shaky connection on your end will not force you to start over. Every new upload goes to the edge automatically from that point on.
(ii) Responsive images, all of them
ThumbPress rewrites srcset URLs, not just the main src. Every responsive size a browser might ask for comes from the edge, instead of some sizes quietly falling back to your origin.
This is the detail a lot of CDN plugins get wrong, and you only notice it when you open the network tab and find half your thumbnails still hitting your own server.
(iii) WooCommerce galleries and variations
Product photos, variation images, and gallery images are all served from the CDN. On a store page, that is most of the page weight. If you have already sorted out your WooCommerce product image sizes, this is the next thing that moves the needle.
- A fallback, so nothing breaks. If the CDN is ever unreachable, images fall back to your own server automatically. Your site does not go blank because an edge node had a bad moment.
- Exclusions you control. Keep specific file types local, like the SVGs your theme depends on, or exclude specific image sizes entirely. You can also lazy load CDN-served images the same way you would local ones.
- A storage dashboard, not a black box. See exactly how much of your included storage is in use and how many images are currently being served from the edge.
- An exit that is actually an exit. Disconnect and your local files are restored. You choose whether to keep or delete the CDN copies. Nothing is held hostage.
How to Turn It On?
Before you start: the Image CDN ships with ThumbPress Pro. On the free plugin, you will need to upgrade first.
1. Connect: Open your ThumbPress dashboard and enable the Image CDN. Your delivery region is selected automatically, so there is nothing to configure first.
2. Set your exclusions: If there are file types or image sizes you would rather keep local, exclude them now, before the bulk offload runs. This is also where you turn on lazy loading for CDN-served images.
3. Run the bulk offload: Send your existing library to the CDN. It runs in the background, so you can close the tab. Cancel and resume any time without starting over.
4. Verify: Open your storage dashboard to check used storage and the number of images being served from the edge. Then load your live site, right-click an image, and confirm the URL points at the CDN rather than your own domain. Hard refresh with Ctrl + Shift + R so you are not looking at a cached copy.
5. Disconnect ThumbPress CDN: You can disconnect the CDN whenever needed. When disconnected, your image URLs return to the local files on your website. You can choose to keep the files stored on the CDN for future use or delete them to free up CDN storage. Deleting the CDN files removes only the stored copies, not the original images on your website.
Optionally, once you are confident images are serving correctly, you can drop the local copies and keep only the CDN version to free up server storage. This step is not required. If you would rather keep local backups of everything, leave your originals in place and let the CDN handle delivery.
Nothing here touches your theme files, and nothing needs a developer.
How It Compares to Other WordPress CDN Options
Scoped to image delivery specifically, here is where each option lands:
| Option | Setup | What gets accelerated | Best for |
| Origin-only hosting | None | Nothing, everything comes from your server | Sites with a mostly local audience and light image traffic |
| Cloudflare | Nameserver change for the common full setup | All site traffic, with caching and optimization depending on plan | Sites that need full-site performance plus a security layer |
| Jetpack Site Accelerator | Connect Jetpack, enable the feature | Images, with automatic resizing and WebP for supported browsers | Small sites wanting a free, hands-off option |
| ThumbPress Image CDN | One toggle in the WordPress dashboard | WordPress images including srcset sizes and WooCommerce galleries | Sites that want dedicated image delivery without touching DNS |
Two things worth saying plainly.
ThumbPress is not a firewall. If you need DDoS protection and WAF rules, Cloudflare does a job the Image CDN is not trying to do, and the two can sit alongside each other.
And the table above is scoped to delivery only, so it understates the plugin. Compression, WebP and AVIF conversion, lazy loading, and hotlink protection are all already in ThumbPress. The CDN is the piece that handles distance.
4 Habits That Make the CDN Worth More
Turning on the CDN is only the first step. These four simple habits can help you get more out of it and make sure your images keep working the way they should as your site grows.
1. Pair it with compression and modern formats. A CDN moves images closer. It does not make them smaller. Converting to WebP or AVIF before they hit the edge is where the big file size savings come from. Do both and the gains stack.
2. Never lazy load your hero image. Lazy loading is genuinely useful below the fold. On your largest above-the-fold image, it is a mistake, because that image is usually your LCP element, and telling the browser to deprioritize the one thing your score depends on works against you. Keep the hero eager; lazy-load the rest.
3. Let the browser pick the size, not just the format. Serving multiple sizes through srcset lets the browser take the smallest file that still looks right, instead of shipping a 2,400px image to a 360px phone. That is exactly why ThumbPress rewrites srcset URLs for the CDN and not only the main image tag.
4. Test from somewhere that is not your desk. A single PageSpeed run is a snapshot from one location, usually close to your server. It cannot show you what a visitor two continents away is experiencing, which is the precise gap edge delivery exists to close. Check on a throttled connection now and then, and treat a good lab score as a floor rather than proof.
For the wider picture, our guide to WordPress image management covers the workflow around all of this.
And if you run a store, speeding up your ecommerce store goes past images into the rest of the stack.
One Toggle Away
Better hosting solves a lot of problems. Distance is not one of them.
If your images are still being served from a single server to visitors everywhere, the ThumbPress Image CDN closes that gap without a migration, a DNS change, or a second bill.
It is live today on every Pro plan. See the plans, or read the full Image CDN feature breakdown first.
Frequently Asked Questions
Yes. It is live on every Pro plan as of September 1, 2026. Storage is included based on your plan tier.
No. CDN storage is included in your plan at no additional charge.
No. You turn it on from your ThumbPress dashboard and it is live.
No. The CDN sits in front of the media library you already have. Your existing images stay where they are.
The CDN handles delivery. Compression, WebP and AVIF conversion, and resizing are handled by ThumbPress itself, and they work together. Optimize first, then serve from the edge.
Yes. Product images, variation images, and gallery images are all served from the CDN.
It can. Faster image delivery helps Largest Contentful Paint in particular, and LCP is an image on most WordPress pages.
No. The Image CDN is a Pro feature. Upgrade to any Pro plan to turn it on.
Disconnecting restores your local files, and you decide whether to keep or delete the CDN copies.
