Compress Images with EWWW Image Optimizer, Deliver Them Optimized from the Infinite Uploads Cloud
EWWW Image Optimizer compresses, resizes, and converts images the moment you upload them, using local tools or its Compress API. Infinite Uploads optimizes the same library again at delivery: right-sized, converted to AVIF or WebP, and served from a global CDN, without touching the file EWWW already processed.
150k+
Sites use our WordPress plugins
14 Days
Money-back Guarantee
EWWW Image Optimizer and Infinite Uploads: Two Optimizers, One Media Library, No Overlap
EWWW Image Optimizer earned its million-plus installs compressing images the moment they land in the Media Library. It bundles jpegtran, optipng, pngquant, and cwebp, or hands the job to its Compress API, and can convert files to WebP for sites without a CDN of their own. None of that stops working once Infinite Uploads is connected.
Image Optimization, on the Business plan, works from the other end. It never touches the original file EWWW compressed. At delivery it right-sizes each image, converts it to AVIF or WebP with a fallback for older browsers, strips metadata, and caches the result on the CDN so the next visitor gets it instantly.
Run both at full strength and you compress and convert the same image twice. Once Infinite Uploads is connected, every file EWWW rewrites inside the uploads folder gets written back to the cloud too, which works but is slow for a bulk run. Turn off the settings that overlap, keep the rest, and each plugin does what it's good at.
Four Ways to Split the Work With EWWW Image Optimizer
EWWW does its best work at upload. Infinite Uploads does its best work at delivery. Here's where the line goes.
Stop Compressing the Same Image Twice
EWWW's local compression, Compress API, and WebP Conversion all do their job on upload, and Infinite Uploads' Image Optimization does its job again at delivery. Running both means paying twice for identical work, and re-compressing an already-lossy JPEG can soften it without shrinking the file any further.
Free Up the Disk Space .webp Copies Were Using
WebP Conversion writes a second .webp file next to every original, doubling image storage on disk. Infinite Uploads serves AVIF and WebP straight from the CDN with automatic browser fallback, so once it's connected those extra copies have nothing left to do.
Skip the Slow Bulk Optimize Run on an Offloaded Library
EWWW's Bulk Optimize writes a compressed copy of every image back into the uploads folder. Once that folder is cloud-backed, each rewrite syncs back up to storage too, which works but turns a bulk run into a multi-day job. Run it before you connect, not after.
Everything Else EWWW Does Keeps Working
PDF compression, Lazy Load, and local or cloud backups of originals don't overlap with anything Infinite Uploads does, so none of it needs to change. Media Folders adds sorting and search on top, and the two plugins stay out of each other's way.
Why Sites Run EWWW Image Optimizer and Infinite Uploads Together
Fewer Credits and Subscriptions to Track
Skip Easy IO and stop burning Compress API credits on images Infinite Uploads is about to re-optimize anyway. Cloud storage, CDN bandwidth, and Image Optimization all come on one Business plan invoice.
Each Plugin Does the Job It's Actually Good At
EWWW handles what happens at upload: local compression, PDFs, backups. Infinite Uploads handles what happens at delivery: resizing, AVIF and WebP, the CDN. Turn off the overlap once, and neither plugin fights the other again.
One Stack an Agency Can Standardize On
Agencies running EWWW across client sites connect every one to the same Infinite Uploads account. Unlimited sites, one invoice, and the same image-delivery stack whether a client has ten photos or ten thousand.
What Works, Feature by Feature
Feature
What you get
Lazy Load
Defers offscreen images until they scroll into view. Runs independently of where the image is stored, so it keeps working once you connect.
Works
Resize images on upload
Scales oversized originals down to a sane maximum width before they reach the Media Library, so less gets stored and less gets synced.
Works
Local compression (jpegtran, optipng, pngquant, gifsicle, cwebp)
Still compresses the original on upload. Optional once Infinite Uploads optimizes the same image again at delivery; double compression adds nothing and can soften images.
Optional, turn off
WebP Conversion and its rewrite rules
Infinite Uploads already serves AVIF and WebP from the CDN with per-browser fallback, and Apache rewrite rules can't reach files the CDN is serving anyway.
Turn off
Easy IO
A second CDN and URL rewriter competing with Infinite Uploads' own for the same image tags. Pick one; there's no reason to run both.
Not needed
Bulk Optimize on an already-offloaded library
Rewrites every file back through cloud-backed storage as it compresses, which is slow. Run it before you connect if you want compressed originals.
Run before sync
Optimize other folders
Only reaches images still on the local filesystem. Anything already offloaded and served from the CDN is outside its reach.
Local files only
PDF compression
Shrinks PDF file size on upload. Infinite Uploads doesn't touch PDFs at all, so this keeps doing useful work with no overlap.
Works
WordPress Multisite
Every site in the network can run EWWW and offload to the same Infinite Uploads account.
Works
Turn Off the Overlap in Three Steps
1. Connect Infinite Uploads
Install the plugin, connect your account, and sync. Your existing Media Library, EWWW-compressed images included, moves to cloud storage and starts serving from the CDN.
2. Turn Off WebP Conversion and Easy IO
In EWWW's settings, turn off WebP Conversion and skip Easy IO. Infinite Uploads is now the one converting to AVIF and WebP and delivering from the CDN.
3. Free Up Local Storage
Once the sync finishes, remove local copies from Infinite Uploads settings. The compressed originals and any leftover .webp files go with them, and your hosting plan gets its space back.
Good to Know Before You Switch
Local compression and delivery-time optimization aren't the same job done twice, but running both is. EWWW's compression happens once, on upload, to the file that stays on your server before it's offloaded. Infinite Uploads' Image Optimization happens on every request, to the copy it serves from the CDN. Keep one, or keep both and accept the redundancy.
Bulk Optimize on an already-offloaded library is slow, not broken. A filesystem scan shows EWWW writing compressed copies and .webp files straight into the uploads folder as it runs. Once that folder is cloud-backed, each write syncs back to storage too, so a run that took an hour on shared hosting can stretch into days.
EWWW still does jobs Infinite Uploads leaves alone. PDF compression, local or cloud backups of originals, and compressing images before you ever connect all keep working with zero overlap. If the site also hosts lesson or product video, Video Cloud streams it from the same account, no separate plugin or hosting bill required.
How We Tested
- Installed EWWW and compressed a batch of JPEGs and PNGs with its local tools.
- Connected Infinite Uploads and synced the library, EWWW-compressed originals included.
- Turned off WebP Conversion and Easy IO, left Lazy Load and PDF compression on.
- Ran Bulk Optimize once before connecting, then again after, to compare speed.
- Confirmed images served as AVIF or WebP from the CDN domain, original untouched.
Result: no conflicts once the overlapping settings were turned off.
Frequently Asked Questions
Do I still need EWWW Image Optimizer if I connect Infinite Uploads?
Yes, for PDF compression, backups, and compressing images before they're ever offloaded. Turn off the settings that duplicate what Infinite Uploads does at delivery, and keep the rest running.
Should I turn off EWWW's local compression on upload?
It's optional. Infinite Uploads optimizes the same image again at delivery, so local compression adds little benefit, and re-compressing an already-lossy file can soften it slightly.
What happens to EWWW's WebP Conversion and the .webp files it created?
Turn it off. Infinite Uploads serves AVIF and WebP straight from the CDN with automatic fallback, and Apache rewrite rules can't reach files the CDN is already serving.
Do I still need Easy IO?
No. It's a paid CDN and URL rewriter doing the same job Infinite Uploads already does. Running both means two rewriters fighting over the same image tags.
Can I still run EWWW's Bulk Optimize on my whole library?
Yes, but run it before you connect Infinite Uploads. On an already-offloaded library, each rewrite syncs back to the cloud too, which works but turns a bulk run into days.
What about EWWW's Optimize other folders feature?
It only reaches images still on your local filesystem. Anything already offloaded and served from the CDN is outside what a local-path scan can see.
Does PDF compression still work?
Yes. Infinite Uploads doesn't compress PDFs, so EWWW's PDF compression keeps doing useful work on every upload with nothing to turn off or reconfigure on your end.
What if an original image or scan is bigger than my upload limit?
Add our free Big File Uploads plugin. It lifts the WordPress upload limit without server changes, so high-resolution scans reach the Media Library before EWWW compresses them.
More Performance and Media Plugins That Work With Infinite Uploads
- Infinite Uploads and Smush
- Infinite Uploads and WP Rocket
- Infinite Uploads and FooGallery
- See all integrations
Try Infinite Uploads Free for 7 Days
No credit card. No cloud accounts. No access keys. Install the plugin, connect your site, and your images start moving to the cloud, optimized for AVIF and WebP at delivery, automatically.
Plans from $16/mo. Unlimited WordPress sites included.