Mediapapa vs Smush

In short: Smush and Mediapapa both touch image compression, but they are built for different problems. Smush is a dedicated image optimisation service with CDN, lazy loading and a large install base. Mediapapa includes compression inside a governance layer that tracks usage, detects duplicates, prevents accidental deletion and monitors library health. If compression and CDN delivery are your only needs, Smush is a strong dedicated tool. If you need compression as part of ongoing library management, Mediapapa covers both at a comparable annual cost — without CDN.

What Smush does

Smush (WPMU Dev) is an image optimisation plugin with over 1 million active installs. The free version provides lossless compression with no monthly limit, automatic compression on upload, bulk processing, lazy loading for images and videos, and WebP and AVIF conversion. The free plan is already more capable than most dedicated compression plugins.

Smush Pro adds 5x lossy Super Smush compression, a 119-point CDN for image delivery, backup and restore of original files, and additional performance tools. Pro plans start at $36 per year for one site. Smush does not track where files are used across the site, has no library health scoring, no duplicate detection and no protection against deleting a file still in use.


What Mediapapa covers on the same ground

Mediapapa Pro includes image compression via the Mediapapa API, processed on Mediapapa’s own servers with no monthly quota. Auto-compression on upload and bulk compression are both included. WebP and AVIF conversion are part of the Pro plan. There is no CDN — Mediapapa compresses and converts files in place on your server rather than serving them from an external delivery network. If CDN delivery is a requirement, Smush Pro or a dedicated CDN plugin fills that gap independently.

The governance features Smush does not cover are where the scope difference is most concrete. The usage index maps every file to every location where it appears across posts, pages, blocks, custom fields and widget areas. From that map, Library Health gives a library-wide score with prioritised recommended actions, and Media Score gives a per-file health indicator covering size, format, alt text and accessibility. Safe Replace updates every ID and URL reference sitewide when a file is swapped. Deletion Warnings block removal of any file still in use. Additional features include AI-assisted metadata writing, media tagging with tag-based search, pre-publish health checks, WP-CLI support and Multisite.


Feature comparison

FeatureSmush ProMediapapa (free)Mediapapa Pro
Image compression✓ 5x lossy✓ unlimited
WebP conversion
AVIF conversion
Auto-compression on upload
Bulk compression
Usage index (per-file usage map sitewide)
Unused media detection
Duplicate detection
Library Health (library-wide score)
Media Score (per-file health)
Deletion Warnings
Safe Replace (sitewide ID and URL swap)
AI-assisted alt text, title and caption✓ (credits)✓ (credits)
Pre-publish health checks
WP-CLI support
Multisite support
Pricingfrom $60/yrFreefrom $49/yr

Key differences

Smush’s primary value is compression performance and delivery. Super Smush achieves higher compression ratios than lossless tools, and the CDN in Pro shifts image delivery off the origin server entirely. For a site owner whose priority is page weight and Core Web Vitals, Smush delivers measurable results with minimal configuration. The free tier is genuinely capable — lossless compression with no monthly limit is more than most sites need from a compression-only tool.

The structural difference is scope. Smush optimises images at upload or during a bulk pass, but has no awareness of what happens to those images in the library afterwards: whether a file is in use, duplicated, missing alt text or at risk of accidental deletion. Mediapapa’s Library Health, Deletion Warnings and pre-publish checks are active during normal content work. The library is not a storage area that gets periodically cleaned — it is a governed layer that stays in a known state.

Pricing is roughly equivalent at entry level. Smush Pro starts at $36 per year for one site. Mediapapa Pro starts at $49 per year for one site and includes all governance features alongside compression. The difference becomes more significant at scale: Mediapapa’s Agency plan covers 100 sites at $199 per year.


Can you use both?

Yes. Smush handles compression and CDN delivery; Mediapapa handles usage tracking, health scoring and governance. They do not conflict. If you run both, disable Mediapapa’s compression feature to avoid sending files through two separate API passes.


Who should choose what

Choose Smush if

You need a CDN for image delivery — Smush Pro includes one, Mediapapa does not.

Lazy loading is important for your performance strategy and you want it handled in the same plugin as compression.

You need backup and restore of original files after compression, which Mediapapa does not currently offer.

Compression is your only current need and the free lossless tier covers your upload volume.

Choose Mediapapa if

You need compression as part of a broader governance layer — usage tracking, health scoring, duplicate detection and deletion protection in a single plugin.

You manage client sites on care plans and need ongoing library health monitoring, not a periodic compression run.

You want compression at a flat annual cost with no per-image pricing, and CDN is handled separately or is not a requirement.

You need Safe Replace, Deletion Warnings or WP-CLI support alongside image optimisation.


Frequently asked questions

Yes. They do not conflict. If you run both, disable Mediapapa’s compression feature to avoid sending images through two separate API passes. Smush continues to handle compression and CDN delivery; Mediapapa continues to handle usage tracking, health scoring, duplicate detection and governance independently.

Smush Free covers lossless compression, WebP and AVIF conversion, and lazy loading with no monthly limit. Mediapapa’s governance layer — usage index, Deletion Warnings, Library Health, Media Score, Safe Replace, duplicate detection — is not available in Smush at any tier. These features address a different problem: not how files are delivered, but whether they are safe to modify, where they appear, and whether the library is degrading over time.

No. Smush’s scope is compression and delivery. It has no awareness of whether a file is in use anywhere on the site. Mediapapa’s Deletion Warnings trigger automatically when you attempt to delete a file that is still referenced in content, preventing accidental breakage without any manual audit required.

These are different things. Smush Pro’s CDN serves compressed images from edge locations close to the visitor, reducing load time regardless of server location. Mediapapa compresses and converts files in place on your server — there is no delivery network. A CDN and Mediapapa are complementary rather than competing.

Not currently. Smush Pro keeps a copy of the original file and allows restoration at any point. Mediapapa does not offer a dedicated restore function at this stage. The roadmap includes moving the original to the WordPress media trash on conversion rather than discarding it, which will make recovery possible through the native WordPress interface.

No. Smush’s scope is compression and format conversion. It has no visibility into how files are referenced across posts, pages, blocks or custom fields. Mediapapa’s usage index maps every file to every location where it appears sitewide, which is the basis for Deletion Warnings, unused media detection and Safe Replace.

Related comparisons

Browse all comparisons →