Short answer: no. With Infinite Uploads Image Optimization enabled, you don't need a separate image-compression plugin, and in most cases you'll get a better, faster result by turning the other one off.
Why a second optimizer isn't needed
Infinite Uploads compresses your images and converts them to next-gen AVIF and WebP formats as they're delivered from the CDN, which is exactly the job other plugins do. Running both means your images can be compressed twice, which adds no benefit and can actually reduce quality.
What we recommend
- Turn off the other plugin's compression / resizing. Let Infinite Uploads handle it at delivery. Double-compression (one plugin's lossy output being re-compressed by ours) can soften images for no size gain.
- Turn off its "WebP" or "next-gen format" conversion. Infinite Uploads already serves WebP and AVIF automatically with per-browser fallback, so a second WebP layer is redundant and can conflict.
- Lazy loading is fine to keep. If you use another plugin only for lazy loading or other non-compression features, those don't conflict. Keep them if you like them.
You can leave the other plugin installed with its compression features disabled, or deactivate it entirely. Either is fine.
Note: Infinite Uploads Image Optimization is non-destructive: it never rewrites your original files. That's different from most compression plugins, which modify the files in your Media Library. If you've previously run one of those, your stored files may already be compressed; that's fine, we optimize whatever the current original is. See Does Image Optimization change my original files?.
A note on the media offload
Infinite Uploads stores and serves your media from the cloud. Some third-party optimizers try to process files on your local server, which can behave unexpectedly once your media is offloaded. Letting Infinite Uploads own optimization end-to-end keeps everything consistent and avoids those edge cases.