Configure Omega Image Engine Pro

1. Confirm the production Base URL before importing or rewriting so public URLs are constructed correctly.
2. Verify writable engine data/log directories and /omega-media-library/ before processing.
3. Check Imagick/ImageMagick or GD codec capability in Status before requesting AVIF/WebP output.
4. Use image discovery first, then import only the source images you want Omega to manage.
5. Generate only the width/format variants appropriate to the site, then inspect library state and usage.
6. Use Back Up & Apply Responsive Delivery only after reviewing the responsive output plan.
7. Run duplicate scan/preview before deletion; only unprotected confirmed orphan duplicates should be removed.

1. Extract the engine at the website root so /omega-image-engine/ and /omega-media-library/ are created.
2. Create the first private Omega administrator.
3. Open Status and confirm writable directories plus available Imagick/GD WebP/AVIF capabilities.
4. Set the website Base URL.
5. Run Full Site Image Discovery and review discovered sources.
6. Import the images you want Omega to manage.
7. Select managed sources and generate the required modern-format/responsive variants.
8. Review library metadata, usage and conversion state.
9. Use Back Up & Apply Responsive Delivery when ready to update eligible HTML markup.
10. Run duplicate scanning, preview confirmed groups and delete only unprotected orphan duplicates when appropriate.

• No hosting/cPanel credentials are requested or stored.
• HTML rewriting is explicit and backup-first.
• Failed or unsupported conversions are not represented as valid generated output.
• Managed originals remain available and modern formats are additional delivery choices.
• SHA-256 duplicate confirmation reduces false duplicate decisions.
• Referenced site images and registered Omega originals/variants are protected from duplicate deletion.
• Administrative writes require authentication and CSRF validation.

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.