Squeeze – Image Optimization & Compression, WEBP Conversion

Squeeze compresses images in your browser using Web Workers and open-source codecs (MozJPEG for JPEG, Browser Image Compression for PNG, WebP and AVIF encoders). You can squeeze from the Media Library, bulk tools, custom folders, or during upload in supported editors.

No. Squeeze does not require ShortPixel, Imagify, or any third-party API. There are no per-month image caps imposed by the plugin.

• Unlimited squeezes (no SaaS quota).
• Privacy: files stay on your server; compression runs in the admin browser.
• Direct WebP can replace originals instead of keeping parallel JPG + WebP copies.
• No recurring API cost for compression itself.
• Niche integrations: Voxel pre-upload, Gutenberg/GenerateBlocks on upload; Elementor in Premium.

Speed depends on your computer and image size. Large PNGs can take longer; increase Squeeze timeout under Settings → Squeeze → Basic Settings if needed.

No. Processing is client-side in wp-admin (and in supported front-end upload flows). Your image bytes are not sent to Squeeze’s servers for compression.

Yes. Enable Direct WebP conversion under Basic Settings to convert new uploads to WebP and replace the original file. You can also use legacy modes that keep JPG/PNG and store WebP in wp-content/squeeze-webp/ with URL rewrite or .htaccess delivery.

Yes for new uploads when you understand URL changes. For existing sites, test on a staging copy first. Replace Image URLs rewrites src in page HTML at render time (database URLs unchanged). If you deactivate the plugin while Direct WebP is on, some hard-coded .jpg links may break — reselect images from the Media Library or restore from .bak backups.

If Direct WebP replaced originals, some content may still reference old .jpg/.png URLs. Reselect images in the editor or restore backups. HTML-only URL rewrite modes stop rewriting when the plugin is off, but original files remain on disk.

Choose one of three modes in WebP delivery:

1. Direct WebP (recommended) — file on disk becomes .webp; lowest storage.
2. Rewrite <img> src — keeps originals; serves WebP URLs in HTML output.
3. Server delivery — keeps URLs; .htaccess serves WebP bytes to supporting browsers.

Yes, with one important caveat about the WebP delivery mode you choose. Supported — Rewrite <img> src to WebP URLs in HTML: Squeeze pushes WebP sidecar files to your external storage provider (S3, GCS, DigitalOcean Spaces, etc.) alongside the compressed originals. The PHP-based URL rewriting rewrites image src and srcset attributes in the page HTML to the WebP path, and this works correctly whether files are served from your origin or a CDN — even when WP Offload Media's "Remove Local Files" option is on. Not compatible — Keep JPEG/PNG URLs — server serves WebP (.htaccess): This mode adds Apache mod_rewrite rules to .htaccess that intercept requests for .jpg/.png files and serve the WebP equivalent. When WP Offload Media is active, image URLs point to a CDN domain (e.g. storage.googleapis.com). Those requests never reach your origin server and therefore never pass through .htaccess — WebP files will not be served. If you use WP Offload Media, always choose the Rewrite <img> src to WebP URLs in HTML mode instead.

Your browser blocked canvas access (common with Firefox privacy.resistFingerprinting). Set privacy.resistFingerprinting to false in about:config, use Chrome/Edge, or a profile without strict fingerprinting resistance.

Yes (free). Pre-upload compression runs on Voxel create-post and file/gallery AJAX uploads so images are smaller before they reach the server.

On-upload squeeze in Elementor is a Premium feature. Free version supports Gutenberg, GenerateBlocks, and Voxel.

Yes. GenerateBlocks media blocks support the same on-upload squeeze as the core Image block when Squeeze on upload is enabled under Basic Settings.

Squeeze can skip replacing an upload when the compressed file would be larger (common with already-optimized PNGs). Lower JPEG/WebP quality in the format tabs, exclude the asset under Excluded images, or squeeze a smaller registered thumbnail size.

Enable Create backup in Basic Settings before squeezing. Squeeze saves a .bak copy next to the file so you can Restore Original Image from the Media Library list or attachment screen. Remove unneeded backups with Delete Backup Image.

The separate folder + server-side delivery mode writes .htaccess rules and needs mod_rewrite on Apache. If mod_rewrite is unavailable, use Direct WebP or Rewrite <img> src instead. On Nginx or other stacks without Apache rules, prefer Direct WebP or HTML rewrite unless you add equivalent server rewrites yourself.

Yes on standard multisite installs—each site has its own Squeeze settings and Media Library. Test Direct WebP on a staging subsite before bulk conversion across a large network.

MozJPEG (JPEG), Browser Image Compression (PNG), plus WebP and AVIF encoders—the same technology family as Squoosh.app by the Chrome team.

Smaller images improve LCP and overall speed, reduce bandwidth bills, and free disk space—especially when combined with WebP.

JPEG, PNG, WebP, and AVIF.

Yes. Use Bulk Squeeze (Media Library attachments) or Directory Squeeze for any folder under your site root. Directory mode does not create automatic backups—back up first.

Yes. List URL or filename patterns (one per line) under Excluded images in Basic Settings.

Yes. Settings → Squeeze has tabs for JPEG, PNG, WebP, and AVIF quality and advanced options.

Wait for completion or a timeout message. Increase Squeeze timeout (default 60 seconds). Very large PNGs may exceed browser memory on low-end devices.

Go to Settings → Squeeze → Basic Settings and raise Squeeze timeout. If it still fails, resize the source image or squeeze a smaller derivative.

Yes, if you want unlimited local compression without API keys or per-month image quotas. Cloud optimizers upload files to their servers; Squeeze processes images in your browser and stores results on your WordPress site. You trade SaaS convenience for privacy, predictable cost, and no upload caps.

Both can optimize on your server. Squeeze focuses on client-side codecs in the browser (Squoosh-family encoders), Direct WebP replacement on disk, and pre-upload squeeze in Gutenberg, GenerateBlocks, and Voxel. EWWW often relies on server-side tools or paid cloud tiers. Choose Squeeze when you want no external compression queue and strong WebP storage savings.

Activate the plugin, open Media Library → any image → Squeeze on the attachment screen. For many images at once, go to Settings → Squeeze → Bulk Squeeze and run Bulk Media Library Squeeze. Enable Squeeze on upload under Basic Settings for automatic optimization on new uploads.

Yes. Squeeze is compatible with the FileBird media folder plugin; bulk and attachment squeeze work with FileBird-organized libraries.

Recommended—especially before Direct WebP conversion on an existing site. Test themes, page builders, and any hard-coded .jpg/.png URLs on staging, then enable on production.

Yes, when images are normal Media Library attachments (product galleries, thumbnails registered in WordPress). Select the thumbnail sizes you want under Squeeze thumbnails in Basic Settings, including WooCommerce sizes when listed.

Yes. Image bytes are not sent to Squeeze’s servers for compression—processing runs locally in the administrator’s browser (and supported front-end upload flows). This helps sites that must avoid third-party image processing services.

https://pluginarium.com/squeeze/squeeze-documentation/