OptiForge Image Optimizer

FAQ

Does the optimization stop if I close my browser?

No! Version 1.4 features a true browser-independent background queue engine. When you start an optimization, it dispatches an asynchronous loopback worker monitored by a WP-Cron watchdog. You can safely close your browser or navigate to other admin screens.

How does OptiForge differ from cloud-based plugins like ShortPixel, Smush, or TinyPNG?

Most image plugins offload images to third-party external servers, which incurs recurring monthly costs, credit exhaustion, and privacy concerns. OptiForge executes 100% of optimizations locally on your web host using native PHP extensions. You retain complete ownership, zero recurring fees, and unlimited image processing.

What happens if my server has strict PHP memory or timeout limits?

OptiForge 1.4 is built with enterprise resource monitoring. Before processing each image, the queue worker checks memory_get_usage() and elapsed execution time. If limits approach the threshold, the worker cleanly yields execution and schedules the next batch via an asynchronous request, preventing 500 errors or server crashes.

What happens if my server does not support AVIF?

OptiForge includes an automated compatibility engine. If your PHP environment lacks native AVIF support, the AVIF toggle is automatically disabled and marked with an inline status badge to eliminate server crashes. Universal WebP compression remains fully active.

What Batch Processing Limit should I select?

• 1 – 3 Images: Best for entry-level shared hosting where PHP memory is constrained to 128 MB and script execution limits are strictly enforced.
• 4 – 6 Images: Ideal for standard VPS setups with 256 MB+ PHP memory.
• 10 – 20 Images: Tailored for high-performance VPS stacks delivering ultra-fast batch runs across tens of thousands of media uploads.

Does optimization alter or delete my original media files?

No. OptiForge employs a strict non-destructive architecture. When backup mode is enabled, your untouched original assets are preserved in a secure, isolated folder (/wp-content/uploads/ofio-backups/). You can restore any image individually or run a complete restore at any time.

How does the One-Click Bulk Restore feature work?

When you click One-Click Bulk Restore All, the background engine reverts each image in your media library to its original state, unlinks all generated .webp and .avif sidecar files from server storage, deletes backup duplicates to reclaim disk space, and automatically resets the dashboard counters to zero.

How does OptiForge deliver AVIF and WebP to frontend visitors?

OptiForge supports dynamic server-level rewrite rules (for Nginx and Apache/LiteSpeed) as well as automated frontend rewrites. When a visitor’s browser sends an Accept: image/avif or Accept: image/webp request header, your server transparently delivers the lightweight next-gen file without altering your HTML URLs.

Is OptiForge compatible with CDN and Page Caching plugins?

Yes. OptiForge features built-in cache-purging hooks compatible with FlyingPress, LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache, and Autoptimize. Whenever an image is optimized or restored, stale page caches are automatically invalidated.

Does OptiForge support WP-CLI?

Yes. Advanced administrators and DevOps engineers can execute optimizations headlessly using standard WP-CLI commands (wp ofio queue status, wp ofio queue start, wp ofio optimize).

Can I preserve photographer EXIF metadata?

Yes. You can toggle Preserve EXIF metadata in the Settings panel to retain camera settings, copyrights, and shutter details, or keep it disabled for maximum payload reduction.