Who is StaticQ Media

Phil and I kept inheriting WordPress sites with the same three problems: thumbnails broken after theme changes, image URLs pointing at old domains after migrations, and gigabytes of orphan files nobody could explain. The existing tools either solved one of those problems or had support issues we weren't comfortable handing to clients.

So we set out to build a plugin that solves all three, with the workflow we actually want to use ourselves: scan and report first, fix selectively second, delete last. Backups before any database change. Quarantine before any file deletion. No bulk-delete buttons without a review step. No silent failures.

That audit-first philosophy (the part that makes the plugin feel different from the alternatives) came out of long conversations between us early on, mapping out everything that could go wrong in a media cleanup and what the safety-by-default version of each operation should look like. The code is mine; the shape of the product is ours.

The Cloudflare R2 + WebP + Worker delivery side came later. I needed cheap, reliable media offload for my own sites, the existing offload plugins gated R2 behind paid tiers, and Cloudflare's free tier is genuinely generous (10 GB storage, 10 million reads/month, zero egress fees). It made sense to wire that into the same plugin as the audit tools.

Benoit Aubert (goonydev on WordPress.org and GitHub): code, releases, support. I'm a working developer using the plugin on production sites, which is part of why the release cadence stays steady. When something breaks, it breaks on my sites too.

Philippe (philooo): concept, product direction, design partner. Phil's the reason the plugin behaves the way it does. The audit-first workflow, the quarantine-before-delete principle, the backup buttons at every database-touching step, the way the scanners categorize findings instead of just reporting counts: those are conceptual decisions he shaped through long discussions early on, and his input still drives what gets built and what doesn't. We talk through every significant feature before it lands.

[Optional: add a sentence about location, years of WordPress experience, prior projects (whatever feels honest). Leave it out if you'd rather keep it minimal.]

StaticQ Media is free at every feature level. No Pro tier gating Cloudflare R2 or bulk migration. No per-image limits. No monthly subscription. Three reasons it stays that way:

• Your infrastructure costs are yours, not mine. The plugin doesn't run servers I have to pay for. Cloudflare R2 storage and Cloudflare Workers run in your own account, on your own free tier. I don't see your media files; I don't host them; I don't pay for the bandwidth.
• I built it for my own work. Maintaining a tool I already use is incremental effort, not a profit center.
• I'd rather have 50 agencies install it across their client portfolios than charge 5 of them. Distribution beats monetization for a tool like this.

If the project ever needs a paid layer to survive (agency support contracts with SLA, white-label customization, dedicated migration consulting), those would be additions on top of a free plugin that stays free. The current scanners, R2 offload, WebP conversion, and Worker deployment will not move behind a paywall.

Active maintenance through 2026 and beyond. Releases ship when there's something worth shipping. Bug fixes get prioritized, features land in scoped increments. No silent abandonment.

Recent release history:

• v3.3.4 June 4, 2026 post_content corruption fix in Worker mode (critical).
• v3.3.3 May 2026 Security hardening for WP.org review + cron pipeline silent-failure guard.
• v3.3.2 April 2026 Original-file handling fix + scanner badge accuracy.
• v3.3.1 April 2026 wp-config constant naming refactor (SQMEDIA_* prefix).
• v3.3.0 April 2026 Initial WP.org-approved release after a 4-round review.

Support questions on the WP.org plugin forum get answered from my personal account (goonydev), typically within 24 hours. Bug reports get triaged and either fixed in the next patch release or scheduled with a clear plan.

Roadmap notes, without firm commitments on timing:

• AVIF support. Currently we generate WebP via WordPress's native image editor (GD or Imagick). AVIF is on the list once GD/Imagick AVIF support is more reliable across hosts.
• Auto-tuned cron batch sizing. Detect the server's max_execution_time and memory_limit and pick safe defaults without requiring wp-config.php overrides.
• WP-CLI commands. For agencies running scans across many client sites at once.
• Potential paid agency support tier. 24-hour SLA, direct Slack, custom migration help. Separate from the free plugin.