StaticQ Media Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
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 external API. No per-image fees. Processing runs on your server, files live in your own cloud bucket.
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
Processing
- Queue-based via WordPress cron — no upload slowdowns
- 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
- 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
- Output buffer-based — works with any theme or page builder
- Per-class and per-size exclusions
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.
- Metadata check — detects corrupted metadata, missing sizes, 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, changed image sizes — your post content may still reference old URLs or outdated filenames. The Post Content Scanner inspects every post for stale image references baked into your database.
- 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.
- 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
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.
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
Key wp-config.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 credentialsSQMEDIA_R2_SECRET_ACCESS_KEY— R2 API credentialsSQMEDIA_R2_BUCKET— R2 bucket nameSQMEDIA_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
Screenshots
No screenshots provided

