Configure Omega Image Engine

1. Review the active WordPress image editor and its WebP/AVIF capability before batch processing.
2. Choose AVIF/WebP quality settings appropriate to the site before optimizing existing media.
3. Decide whether automatic optimization should run for new uploads.
4. Scan the Media Library before starting an authenticated batch.
5. Use run/resume batch processing rather than trying to optimize the entire library in one unbounded request.
6. Review the Media Library status column for individual attachment results.
7. Use duplicate preview before deleting any orphan file; registered attachment originals/sizes and Omega variants are protected.

1. Back up the WordPress site/database and install/activate the plugin.
2. Open Omega Image and review Status for GD/Imagick, WebP and AVIF output capability.
3. Configure AVIF/WebP quality and whether new uploads should be optimized automatically.
4. Run Scan Media Library to identify processable attachments.
5. Run or resume the authenticated batch to optimize existing attachments.
6. Review Media Library status for individual attachment results.
7. Use duplicate scanning and preview to inspect exact duplicate orphan files.
8. Delete only confirmed unregistered orphan duplicates when appropriate.

• Native WordPress attachment metadata is preserved.
• Original attachment images remain fallback sources.
• All AJAX administration actions require capability checks and WordPress nonces.
• Duplicate cleaner protects registered attachment originals, WordPress sizes and Omega variants.
• Generated image files are preserved on uninstall to avoid breaking cached/external references.
• No cloud processing credentials or remote optimization account is required.

After configuration, test the pages, forms, checkout/payment flows, authentication, media, scripts/styles and integrations that matter to the site. Use staging where practical for higher-risk changes.