Before you begin
Use a recent WordPress installation with suitable image-processing support. The plugin's published requirements are WordPress 6.0+ and PHP 7.4+. WebP/AVIF writing depends on GD, Imagick or available server encoders.
A practical WordPress image optimization tutorial for site owners, editors and developers. No previous image-conversion experience required.
Follow these steps in order for a first run. You can also jump straight to a section if the plugin is already installed. Menu names refer to the UWH Image Optimizer admin dashboard in version 3.0.1.
Use a recent WordPress installation with suitable image-processing support. The plugin's published requirements are WordPress 6.0+ and PHP 7.4+. WebP/AVIF writing depends on GD, Imagick or available server encoders.
uwh-image-optimizer-converter-v3.0.1.zip.Installing the plugin does not start a bulk conversion of existing Media Library files.
On a first installation, the three-step setup recommendation can help you choose an output format, image quality and automatic processing of future uploads. You remain in control:
Start at Image Optimizer → Settings. Select a supported output format and image quality, then optionally cap maximum width/height.
Use Beginner Mode for the main controls or open Advanced for source-format include/exclude and policy settings.
When automatic optimization is enabled, compatible images uploaded after installation may be processed using your configured settings. It is separate from the manual conversion of pre-existing library files. Check format support and test with one upload before enabling it for a production workflow.
Dry Run uses temporary output where applicable; it is designed not to replace Media Library attachments or create rollback/history entries.
You can re-optimize with a changed format, quality or max resolution. Repeating the exact same profile may be skipped to avoid needless recompression.
Existing library conversion is intentionally manual. The live admin worker helps when WP-Cron is delayed, and server-capacity safety checks can skip demanding files. Avoid running other heavy server tasks concurrently.
Open History & Rollback to see successful conversions that still have valid restore snapshots. Restore a previous state or inspect recorded bulk runs. Up to three prior states can be retained per attachment.
Bulk Restore reverts files in a specific run when valid snapshots still exist, but skips later-modified images to prevent overwriting new work. You can delete old backup snapshots from the dashboard; doing so removes related restore options.
Check Settings → System Status for writer availability. Your host may need compatible GD/Imagick/ImageMagick support. Choose WebP when AVIF is unsupported.
Read the skip reason. Common cases include an identical optimization profile, animated GIF protection, unsupported writer, small originals or memory/file-size safety limits.
Keep the dashboard open so its AJAX worker can advance processing. Check permissions, server timeouts and scheduled WordPress tasks. Avoid simultaneous heavy jobs.
Pause the operation and reduce resource contention. Server capacity varies, especially on shared hosting; consider off-peak processing and reviewing PHP error logs.
Snapshots can be removed, expire or fail if storage is unavailable. A restore requires a valid retained snapshot; use your independent full-site backup if one is no longer available.
Download the plugin, start with a few images and review the results before running bulk changes.
Download the WordPress plugin