StaticQ Media

Images are not processed on upload. They enter a queue and are processed in batches by WordPress cron. Batch size and time budget are configurable. This avoids CPU spikes and timeouts, especially on shared hosting.

StaticQ Media overlaps with all three but isn't a drop-in replacement for any of them. The pipeline (resize, WebP, offload, deliver) covers what Smush and Imagify do for image optimization, plus what WP Offload Media does for cloud storage, but only for Cloudflare R2. Where StaticQ Media adds something none of those offer is the three media library scanners (Media Library Scanner, Post Content Scanner, Orphan Detection). If you're on Cloudflare and want the full pipeline in one plugin with no monthly fees, StaticQ Media is a fit. If you're locked into AWS or use a different optimization workflow, those plugins may serve you better.

No, Cloudflare is optional. The plugin is optimized for Cloudflare workflows (R2 offload, Cloudflare Image Resizing, and the optional Worker fallback), but it runs fully on your own server without any cloud account. In local-only mode, StaticQ uses WordPress's native image editor (GD or Imagick) for resizing and WebP generation, files stay in your uploads directory, and the Media Library Scanner, Post Content Scanner, and Orphan Detection all work as a pure audit-and-cleanup toolkit. Cloudflare comes in when you want offsite storage, edge-based image resizing, or CDN fallback. R2's free tier (10 GB storage, 10 million reads/month) is generous for most WordPress sites if you decide to enable it.

No, your upload completes instantly. Processing happens in the background via WordPress cron, fully decoupled from the upload request.

Yes. The Media Manager registration tool indexes your entire existing library. Then run the Media Library Scanner to detect issues and repair them: missing sizes, WebP variants, and cloud sync gaps are all handled.

Your original files remain untouched. Cloud copies stay in your bucket. Front-end delivery stops. WordPress falls back to local URLs. No data is deleted on deactivation.

Yes. Front-end delivery uses output buffering, so it works with Elementor, Divi, Gutenberg, Bricks, and any caching plugin that outputs standard HTML.

The Media Manager page shows queue status, processed counts, and per-attachment state. Scanner results show issue breakdowns by category.

It checks every attachment against your current settings in one pass. Metadata is validated for missing sizes, wrong dimensions, deprecated entries, and missing WebP variants. Files are verified across local disk and cloud bucket to ensure they exist in the correct storage location. Issues are categorized by type and severity. You can repair individual attachments with one click, or use Batch Fix All to resolve everything at once. After a theme change with new image sizes, it acts as a free regenerate thumbnails replacement.

It inspects every post, page, and custom post type for image references baked into the content. It detects URLs pointing to wrong domains (e.g. old CDN or migration leftovers), stale size references that no longer match current attachment metadata, deleted attachments still referenced in content, and broken URLs that cannot be resolved. Wrong domain and stale size issues can be fixed automatically: the scanner rewrites the URLs directly in the database. Deleted attachment and broken URL issues are reported for manual review.

Orphan Detection lists all files in your local uploads directory and cloud bucket, then compares them against the WordPress database. Any file with no matching attachment record is flagged as an orphan. You can exclude specific folders to avoid false positives. Orphans can be quarantined for safe review before permanent deletion. Run the Media Library Scanner first to fix metadata issues, then Orphan Detection to catch leftover files.

Yes. EXIF metadata (GPS coordinates, camera info, timestamps) is stripped during processing. This reduces file size and removes potentially sensitive location data.

Absolutely. Cloud offloading is just one part of the pipeline. The Media Library Scanner audits your entire library and lets you repair everything in one pass. Orphan Detection cleans up leftover files. The Post Content Scanner fixes stale image references in your posts. And the queue-based processing prevents CPU spikes on upload, all without moving a single file off your server.