In short: EWWW Image Optimizer is one of the most capable free compression tools available — it processes images locally on your server with no monthly quota, supports lossless and lossy modes, WebP and AVIF, and includes a CDN option. Mediapapa Pro includes compression via its own API at a flat annual cost, alongside usage tracking, health scoring, duplicate detection and deletion protection. If local processing and zero external dependency matter, EWWW is hard to beat. If you need compression as part of ongoing library governance, Mediapapa covers both.
What EWWW Image Optimizer does
EWWW Image Optimizer (45M+ downloads) compresses images locally on the server without sending files to an external API. It supports lossless and lossy compression, bulk optimisation, WebP and AVIF conversion, lazy loading, and an optional cloud compression mode for faster processing. The free tier is genuinely comprehensive — local lossless compression with no monthly limit, WebP conversion and bulk processing are all included at no cost. Paid cloud compression and the EWWW CDN are available as optional upgrades.
EWWW does not track where files are used, has no library health scoring, no duplicate detection and no protection against deleting a file still in use. Its scope is image optimisation.
What Mediapapa covers on the same ground
Mediapapa Pro processes compression via the Mediapapa API — files are sent to Mediapapa’s servers, optimised and returned. There is no monthly quota. WebP and AVIF conversion are included. Auto-compression on upload and bulk compression are both available in Pro. Unlike EWWW, Mediapapa has no local processing option — it requires an API connection and an active Pro plan for compression.
The governance features EWWW does not cover are the main reason to choose Mediapapa: the usage index maps every file to every reference across the site, Library Health gives a library-wide score, Media Score evaluates each file individually, Deletion Warnings block removal of referenced files, Safe Replace updates every reference sitewide, and duplicate detection surfaces copies. Compression in Mediapapa is one capability inside that system.
Feature comparison
| Feature | EWWW paid/cloud | Mediapapa (free) | Mediapapa Pro |
|---|---|---|---|
| Image compression | ✓ cloud, lossy | — | ✓ lossless, unlimited |
| WebP conversion | ✓ | — | ✓ |
| AVIF conversion | ✓ | — | ✓ |
| WP-CLI | ✓ | — | ✓ |
| Usage index (per-file reference map) | — | ✓ | ✓ |
| Deletion Warnings | — | ✓ | ✓ |
| Library Health + Media Score | — | ✓ | ✓ |
| Duplicate detection | — | ✓ | ✓ |
| Safe Replace (sitewide) | — | ✓ | ✓ |
| AI-assisted metadata | — | ✓ (credits) | ✓ (credits) |
| Pricing | from $80/yr | Free | from $49/yr |
Key differences
EWWW’s primary advantage is local processing. No file leaves your server on the free tier. For hosting environments where external API calls are restricted, or for site owners who are uncomfortable routing images through third-party servers, EWWW is the right choice. The free tier is also genuinely capable — lossless compression, WebP and bulk processing with no monthly limit or account required.
Mediapapa’s compression is API-based and requires a paid plan. The tradeoff is the governance layer that comes with it. If you need to know where every file is used, prevent accidental deletion, replace files safely across a complex site, and monitor library health over time — that context is not available in EWWW at any tier.
Both support WP-CLI. For agencies running compression across multiple client sites from the command line, either plugin is viable. EWWW has the advantage of local processing; Mediapapa has the advantage of combining compression with full governance in one plan.
Who should choose what
Choose EWWW if
Local processing with no external API dependency is a priority — privacy, hosting restrictions or preference.
You want a free compression tier with no monthly limit, WebP support and no account required.
You need backup and restore of original files after compression, which Mediapapa does not currently offer.
Compression is your only need and you want the lightest governance footprint.
Choose Mediapapa if
You need compression alongside usage tracking, health scoring, duplicate detection and deletion protection in a single plan.
Local processing is not a constraint and API-based compression at a flat annual cost is acceptable.
You manage client sites where library governance — not just compression — is part of your service.
Frequently asked questions
Yes. EWWW handles compression locally; Mediapapa handles usage tracking, health scoring and governance via its API. They do not conflict. If you run both, disable Mediapapa’s compression feature to avoid processing the same files twice.
No. EWWW’s scope is compression. It has no awareness of whether a file is referenced in site content. Mediapapa’s Deletion Warnings trigger automatically when you attempt to delete a file still in use.
For local lossless compression, yes. There is no monthly image limit, no account required and no quota. Cloud compression (lossy, AVIF, CDN) requires a paid plan. Mediapapa’s free version includes no compression — that requires Pro.
No. Mediapapa sends images to the Mediapapa API for processing. Files leave your server. EWWW’s free tier processes images entirely on your server with no external API call.
Related comparisons
Curious what is hiding in your library?
Scan it for free. Governance is included — compression via API in Pro.