Imagify (from WP Media, the WP Rocket team) is the compression plugin for site owners who want the decision tree made for them: three compression levels – Normal (lossless), Aggressive (recommended), Ultra – applied on upload or in bulk across the media library, with WebP or AVIF next-gen versions generated alongside. The trade is control for predictability; where EWWW Image Optimizer offers server-binaries and granular per-format settings, Imagify’s API-driven pipeline is tuned, maintained, and paired naturally with WP Rocket’s caching. The 2.3.x line modernized the operational side: a Missing Next-Gen filter in the Media Library, a manual stop button for bulk jobs, chunked database queries for restrictive hosts, and MCP abilities with OAuth 2.1 + PKCE authentication for AI-agent interaction – optimization credits require confirmation before an agent consumes them.
WordPress 7.1 client-side upload handling is where 2.3.3 and 2.3.4 invested: thumbnails from client-side uploads now optimize instead of being skipped, resize opt-outs are respected to prevent double scaling, and next-gen generation no longer stalls when the API reports an image as already compressed. That is the unglamorous compatibility work that keeps a media plugin dependable on current WordPress.
Competitive Features
- Three compression levels – lossless Normal through Ultra, applied globally or per-image
- WebP and AVIF generation – next-gen formats served alongside originals
- Bulk optimization with control – manual stop button and prioritized queue ordering (2.3.2)
- Missing Next-Gen filter – Media Library view isolating images lacking next-gen versions
- WP 7.1 client-side compatibility – thumbnails optimized, double-scaling prevented (2.3.3)
- MCP abilities with OAuth 2.1 – AI-agent access with credit-consumption confirmation
- WP Rocket integration – same vendor, coordinated WebP and caching delivery
Key Features
- Automatic on-upload optimization – every new image compressed as it lands
- Resize larger images – optional max-dimension scaling on upload
- Backup and restore – originals preserved; one-click revert per image or in bulk
- Chunked bulk processing – large libraries survive restrictive hosting timeouts (2.3.2)
- GIF and PDF optimization – beyond standard raster formats
- Comparison view – before/after quality inspection per image
- Network activation – multisite-compatible configuration
Comparison with Competitors
Imagify vs ShortPixel
| Aspect | Imagify | ShortPixel |
|---|---|---|
| Billing model | Monthly by traffic tier | Credit-based (monthly or one-time) |
| Compression levels | Three presets | SmartCompress + lossy/lossless/glossy |
| Next-gen formats | WebP + AVIF | WebP + AVIF |
| Media Library tooling | Missing Next-Gen filter, stop button | Advisor and bulk tools |
| Ecosystem | WP Rocket / WP Media | Independent |
| Bulk on restrictive hosts | Chunked queries (2.3.2) | Configurable batches |
Bottom line: Both are excellent API-based optimizers with credit/tier billing. ShortPixel’s credit model suits spiky usage; Imagify’s tiers and WP Rocket integration suit WP Media ecosystem sites. Compression quality is comparable – the decision is pricing shape and stack fit.
Imagify vs Soliloquy Slider Pro
| Aspect | Imagify | Soliloquy Slider Pro |
|---|---|---|
| Job | Compress all site images | Slideshow presentation |
| Performance role | Upstream file size reduction | Layout and display layer |
| Next-gen formats | WebP + AVIF | Depends on images fed |
| Complementary | With sliders and galleries | With optimizers |
| Overlap | None | None |
Bottom line: Different layers of the media pipeline. Soliloquy Slider Pro presents images in responsive slideshows; Imagify makes whatever it presents load faster. Slider-heavy sites run both – the optimizer works before the slider ever renders.
Recommended Stack – optimized images deserve optimized delivery. Pair Imagify with FlyingPress or WP Rocket: WebP files from Imagify, lazy loading and critical CSS from the caching layer, and Core Web Vitals coverage end-to-end.
Official Changelog
Version 2.3.4
Release Date: September 2, 2026
- Fix: Optimization no longer stops when a next-gen destination path is unavailable.
- Fix: The “Settings saved” notice is back on multisite when Imagify is network-activated.
- Fix: Failing to reach the MCP OAuth discovery documents is no longer reported as a critical issue in Site Health.
- Enhancement: Updated the WP Rocket banner copy on the bulk optimization page.
Version 2.3.3
Release Date: August 20, 2026
- New: MCP media abilities now accept a filename or media URL, not just an attachment ID.
- Enhancement: WordPress 7.1’s resize opt-out on client-side uploads is respected to avoid double scaling.
- Fix: Thumbnails from WordPress 7.1 client-side uploads are now optimized instead of skipped.
- Fix: Companion files recorded by WordPress 7.1 are kept when regenerating or restoring media.
- Fix: Media Library behavior corrected for 7.1 client-side uploads.
Version 2.3.2
Release Date: July 22, 2026
- New: Missing Next-Gen filter added to the Media Library.
- New: Manual stop button for bulk optimization.
- Enhancement: Newly uploaded and manually optimized images prioritized in bulk jobs.
- Enhancement: Large database queries chunked to avoid timeouts on restrictive hosts.
- Fix: The Next-Gen generation progress bar is visible again and no longer shows a negative count.
- Fix: Next-Gen files are generated when the API reports an image as already compressed.
- Fix: Scaled uploads are no longer skipped by the bulk backup check.
- Fix: Improved WP Rocket CDN detection for CDN-hosted images.
- Fix: Correct capability handling restored for the Imagify network admin menu.
Frequently Asked Questions
Which compression level should I choose?
Aggressive is Imagify’s recommendation for most sites – visually lossless at practical viewing sizes with substantial savings. Normal preserves bytes exactly for portfolios and print assets; Ultra maximizes savings where quality latitude exists (thumbnails, backgrounds).
Does Imagify create WebP and AVIF?
Yes. Next-gen versions generate alongside originals, with delivery configurable through rewrite rules or the paired caching plugin (WP Rocket). The Missing Next-Gen filter in 2.3.2 makes gaps visible in the Media Library.
Can I restore my original images?
Yes – originals are backed up before optimization, restorable per image or in bulk. Scaled uploads and WordPress 7.1 companion files are handled correctly as of 2.3.3.
How does bulk optimization behave on large libraries?
Jobs run in the background with prioritization – new uploads and manually optimized images first – and chunked database queries prevent timeouts on restrictive hosts. A manual stop button (2.3.2) halts a job without losing progress.
What are the MCP abilities?
Machine-readable operations (with OAuth 2.1 + PKCE authentication as of 2.3.1) that let AI agents and external clients interact with Imagify – listing media, requesting optimization. Credit-consuming actions require explicit confirmation, so automation cannot silently drain your quota.
Leave a Reply