StaticQ Media

StaticQ Media is a complete image processing pipeline for WordPress. Upload once. StaticQ handles resizing, WebP conversion, cloud offloading, and front-end delivery in the background via WordPress cron.

No required external API (the optional Cloudflare Image Resizing integration is the only external service, used only if you enable it). No per-image fees. Processing runs on your server, files live in your own cloud bucket.

Actively maintained in 2026. 1.

What makes StaticQ different

Most image optimization plugins compress and deliver. StaticQ Media also audits and cleans up. Three scanners catch what other plugins miss:

• Media Library Scanner: finds missing thumbnails, broken metadata, missing WebP variants, and cloud sync gaps; regenerates thumbnails after a theme change in one pass.

• Post Content Scanner: finds stale image URLs baked into your posts after a CDN migration, domain change, or filename rename, and fixes broken images automatically.

• Orphan Detection: finds files in your uploads folder and cloud bucket that no attachment references, so you can reclaim disk space safely.

All three are free in StaticQ Media. No competing image optimization plugin offers this combination.

Common use cases

• Switched themes and your images look wrong → Media Library Scanner detects deprecated sizes and regenerates current ones.

• Migrated from another CDN or domain → Post Content Scanner finds stale URLs baked into your posts and fixes them.

• Cleaning up an old site → Orphan Detection surfaces files no attachment references and lets you quarantine them safely.

• First-time WordPress site on Cloudflare → R2 offload, WebP delivery, and Cloudflare Worker fallback wired up from one plugin.

How It Works

• Upload: image enters the processing queue

• WordPress cron generates all registered sizes + WebP variants

• Processed files are uploaded to your Cloudflare R2 bucket

• Front-end delivery rewrites <img> tags to <picture> elements with CDN URLs and WebP sources

Media Library Scanner

Change your image sizes, switch themes, enable WebP: your media library drifts out of sync. The Media Library Scanner realigns everything in one pass across local disk and cloud bucket. Acts as a free regenerate thumbnails alternative when your theme’s image sizes change.

• Metadata check: detects corrupted metadata, missing thumbnails, wrong dimensions, deprecated sizes, and missing WebP entries

• File check: verifies every file exists in the correct storage location and flags sync gaps between local and cloud

• One-click repair per attachment: fixes metadata first, then generates missing files, uploads, or downloads as needed

• Batch Fix All: resolve every issue across your entire library at once

• Retroactive registration: index your existing media library for processing after install

• Regenerate mode: force re-process all sizes from the original file

Post Content Scanner

Switched CDN providers, migrated domains, cloned a site for staging, changed image sizes: your post content may still reference old URLs or outdated filenames, leaving broken images scattered across your site. The Post Content Scanner inspects every post for stale image references baked into your database and fixes broken images automatically. Handles post-migration URL rewriting that other offload plugins leave behind.

• Scans all posts, pages, and custom post types regardless of status

• Wrong domain detection: finds CDN or foreign domain URLs that should point to your local site

• Stale size references: detects image filenames that no longer match current attachment metadata

• Deleted attachment references: flags images linked to attachments that no longer exist (info only)

• Broken URL detection: identifies image URLs that cannot be resolved to any attachment (info only)

• One-click fix per post: rewrites wrong domain URLs and updates stale size references in post content

• Batch Fix All: resolve every fixable issue across all posts at once

• Table backup: back up wp_posts before applying fixes as an extra safety measure

Orphan Detection

Deleted posts, removed theme sizes, failed uploads: files pile up with no attachment record. The Orphan Detection tool finds them across local disk and cloud bucket. No false-positive deletion: every candidate is reviewed and quarantined before anything is permanently removed.

• Scans local uploads directory and cloud bucket for files with no WordPress attachment

• Folder exclusions: skip known third-party directories to avoid false positives

• Quarantine: move orphans to an isolated folder for review before permanent deletion

• Restore from quarantine: bring files back if needed

• Export orphan list as CSV for external review

• Built for libraries other scanners can’t finish: cron-batched, retryable, no stuck-at-X% timeouts

Run the Media Library Scanner first to fix metadata issues, then the Post Content Scanner to clean up stale references in your posts, then Orphan Detection to catch leftover files. Nothing is deleted without your review.

Processing

• Queue-based via WordPress cron: your upload completes instantly, processing runs in the background

• Configurable batch size and time budget per cron tick

• Automatic retry on failure

• Works on shared hosting: no memory spikes, no timeouts

• Cloudflare Image Resizing support (optional)

• WebP conversion with quality control

• EXIF metadata stripping for privacy

• Big image scaling control

• Non-image media support (PDFs, documents, etc.)

Storage

• Cloudflare R2: included free at every feature level. No Pro tier required, no per-site fees.

• Three modes: Local only / Local + Cloud / Cloud only

• Chunked uploads for large files

• Credentials via wp-config.php constants or settings page

Front-End Delivery

• HTML5 <picture> elements with WebP <source> fallbacks

• Automatic srcset generation from registered image sizes

• Lazy loading with eager-first-image option

• Works with Elementor, Divi, Gutenberg, Bricks, and any caching plugin (output buffer-based)

• Per-class and per-size exclusions

Cloudflare Worker Deployment

Deploy a Cloudflare Worker to serve media directly from your R2 bucket with automatic fallback to your origin server. The built-in wizard handles deployment, testing, and configuration.

Developer Configuration

php constants for fine-tuning:

• SQMEDIA_CRON_BATCH_SIZE: attachments per cron tick (default: 1)

• SQMEDIA_CRON_MAX_SECONDS: time budget per cron tick (default: 25)

• SQMEDIA_SCAN_BATCH_SIZE: attachments per scanner batch (default: 50)

• SQMEDIA_R2_ACCESS_KEY_ID: R2 API credentials

• SQMEDIA_R2_SECRET_ACCESS_KEY: R2 API credentials

• SQMEDIA_R2_BUCKET: R2 bucket name

• SQMEDIA_R2_ACCOUNT_ID: Cloudflare account ID

External services

This plugin connects to the following third-party services when configured by the user. No data is sent to any external service unless the user explicitly enables and configures the corresponding feature.

Cloudflare R2 (Object Storage)

When the user configures Cloudflare R2 as their storage provider, the plugin uploads processed media files (resized images and WebP variants) to the user’s own Cloudflare R2 bucket. Files are uploaded, downloaded, and deleted via the S3-compatible API.

• Data sent: media files (images), bucket credentials (API token, account ID)

• When: during cron-based queue processing, scanner repair operations, and orphan quarantine/restore

• Service provider: Cloudflare, Inc.

• Terms of Service

• Privacy Policy

Cloudflare Image Resizing (optional)

When enabled, the plugin sends original images to Cloudflare’s Image Resizing API to generate resized and WebP variants. This requires the user’s domain to be proxied through Cloudflare. The resized images are stored locally or in the user’s bucket.

They are not hosted by Cloudflare.

• Data sent: image files via Cloudflare-proxied URL

• When: during cron-based queue processing, when Cloudflare Image Resizing is enabled in settings

• Service provider: Cloudflare, Inc.

• Terms of Service

• Privacy Policy

Cloudflare Workers API (optional)

When the user deploys a Cloudflare Worker fallback via the plugin’s setup wizard, the plugin communicates with the Cloudflare API to create and configure the Worker script on the user’s own Cloudflare account.

• Data sent: Worker script source code, Cloudflare API token, account ID, zone ID

• When: only during the one-time Worker deployment wizard

• Service provider: Cloudflare, Inc.

• Terms of Service

• Privacy Policy