Stop Paying Monthly for Media Optimization

When you upload an image, WordPress normally generates all registered thumbnail sizes immediately — blocking your upload and spiking CPU. StaticQ intercepts this process and places each required size into a processing queue instead. A WordPress cron job then works through the queue in controlled batches, preventing server overload.

No — Cloudflare is optional. StaticQ runs fully on your own server using WordPress's native image editor (GD or Imagick) for resizing and WebP generation, with files staying in your local uploads folder. The Media Library Scanner, Post Content Scanner, and Orphan Detection all work without any cloud account. Cloudflare comes in only if you want to offload to R2 (free up to 10 GB), use Cloudflare Image Resizing instead of local encoding, or deploy the optional Worker fallback. Plenty of users run StaticQ purely as a local audit-and-cleanup tool with no Cloudflare account at all.

Cloudflare R2 includes 10 GB of free storage and 10 million Class B (read) operations per month — more than enough for most WordPress sites. Beyond that, it's $0.015/GB/month with zero egress fees. You'll never pay for bandwidth when visitors load your images.

Absolutely. The Media Library Scanner audits your entire media library — both the WordPress database and actual files on disk. It identifies missing sizes, extra sizes, and files that need to be offloaded. You can then process everything through the queue at your own pace.

Yes — that's actually one of its main advantages. Because images are processed in batches via cron rather than all at once on upload, StaticQ puts minimal load on your server. It's designed to work within the resource constraints of shared hosting environments.

In local mode, optimized images stay on your hosting server. In cloud mode, they're offloaded to Cloudflare R2 after processing, and the local copies are removed. You can mix and match — some images local, others offloaded — based on your needs.

Everything. StaticQ Media includes queue-based processing, Cloudflare R2 offloading, Cloudflare Image Resizing, Media Library Scanner, Post Content Scanner, orphan detection with quarantine, Batch Fix All, regenerate mode, WebP generation, lazy loading, Cloudflare Worker deployment, and smart front-end delivery. No feature limits. No per-image caps.

ShortPixel and Optimole charge monthly per-image fees and route your images through their servers. StaticQ processes everything on your own infrastructure (with optional Cloudflare Image Resizing for users who already have a paid Cloudflare plan), stores on your own cloud bucket, and the plugin itself is completely free. You own your entire pipeline.

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.

Absolutely. Cloud offloading is just one part of the pipeline. The Media Library Scanner audits your entire library — detecting missing sizes, wrong dimensions, deprecated entries, and corrupted metadata — then lets you repair everything in one pass. The Post Content Scanner fixes stale image references in your posts. Orphan Detection cleans up leftover files. And if you have a Cloudflare account, you can use Cloudflare Image Resizing for higher-quality thumbnails — all without moving a single file off your server.

Cloudflare Image Resizing is typically used for on-the-fly transforms, but that means ongoing costs — each unique request is billed, and the same sizes get regenerated on every cache miss. StaticQ takes a different approach: it uses Cloudflare to resize each image once during cron processing, then stores the result on disk or in your bucket. You get Cloudflare's superior compression and quality without recurring per-request fees. It also keeps your server out of the resizing work entirely — no GD or Imagick bottleneck. Another key advantage: Cloudflare guarantees WebP output regardless of your server configuration, while local WebP generation depends on your hosting environment having the right libraries (libwebp for GD or Imagick). And because the output files are yours, you can stop using Cloudflare anytime without losing your thumbnails.