Imagify plugin review and common issues

Monthly data limits reset at the start of each billing cycle. If you have hit the limit before your reset date, you can upgrade to a higher plan in Imagify → Account, or wait for the monthly reset. For bulk optimization of a large library, consider timing the bulk process near your reset date to maximize the monthly allowance. If you regularly exceed your limit, upgrade to a plan that covers your average monthly data usage — check Imagify’s dashboard for your historical usage pattern.

Imagify creates WebP versions of images but requires server configuration to serve them. For Apache: Imagify adds rules to .htaccess automatically — check Imagify → Settings → WebP to verify .htaccess rules are present. For Nginx: automatic .htaccess rules do not apply — you need to add server-level rules to check for WebP file existence and serve them. Alternatively, if using WP Rocket, enable WebP caching in WP Rocket — it handles WebP delivery automatically in coordination with Imagify.

Imagify backs up original images if backup is enabled in settings. To restore a specific image, go to the media library, click the image, and click Restore Original in the Imagify section. To switch compression levels, restore the original first, then re-optimize with a less aggressive mode (Aggressive instead of Ultra, or Normal instead of Aggressive). If backup was not enabled before optimization, originals cannot be recovered from Imagify — use a site backup from UpdraftPlus or another backup plugin.

AVIF conversion is available in Imagify’s settings alongside WebP. Go to Imagify → Settings → Files Optimization and enable AVIF Creation. Imagify will generate AVIF versions of images in addition to WebP. For browser detection and format serving, configure server rules or rely on WP Rocket’s handling if active. AVIF provides better compression than WebP but requires browser support — enabling both WebP and AVIF fallback ensures optimized delivery across all browsers.

Imagify processes all images uploaded to the media library by default. To exclude specific images, you can restore them to the original after bulk optimization. For preventing optimization of future uploads for specific cases, there is no built-in exclusion filter — Imagify optimizes all new uploads automatically. For theme or plugin images outside the media library, Imagify does not process these by default (only media library images), so external assets are not affected unless manually added.

Both are top-tier choices. Imagify excels at JPEG compression quality, particularly at the Aggressive level, and is the natural choice for WP Rocket users. ShortPixel offers credit-based pricing (more predictable than Imagify’s data-based system for variable image sizes), custom folder optimization outside the media library, and strong AVIF support. For most WordPress sites, the difference in compression quality is minimal — the decision often comes down to pricing model and ecosystem (WP Rocket users → Imagify; everyone else → ShortPixel or Imagify).

Yes — Imagify functions independently of WP Rocket. The integration advantage applies to WebP delivery (WP Rocket handles it automatically when both are active), but Imagify’s core optimization features work on any WordPress site regardless of which caching plugin is used. The WP Rocket integration simply removes one configuration step.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.