INSTALL OMEGA IMAGE ENGINE PRO · Pure HTML 2.0.1
Install Omega Image Engine Pro
Installation and preflight requirements for Omega Image Engine Pro Pure HTML 2.0.1, including safe first-run checks.
Pre-installation requirements
Verify the environment before installation so unsupported server/platform conditions are discovered before production changes.
- Create a current backup appropriate to the site before installing or making production changes.
- PHP 8.1+ recommended.
- Write access to /omega-image-engine/data/, /omega-image-engine/logs/ and /omega-media-library/.
- Imagick/ImageMagick recommended for broadest codec support; GD supported when required codecs are compiled in.
- ZipArchive is required only for ZIP output.
- Apache/LiteSpeed can use the supplied .htaccess protection; Nginx requires equivalent server rules for private engine directories.
Installation procedure
- Extract the engine at the website root so /omega-image-engine/ and /omega-media-library/ are created.
- Open the private Omega administration URL and create the first administrator account.
- Confirm protected data/log paths are writable and private from public execution where applicable.
- Open the engine Status/Settings area and verify the server capabilities required by this product.
- Complete the product-specific setup workflow before applying high-impact changes.
Immediately after installation
- Confirm the production Base URL before importing or rewriting so public URLs are constructed correctly.
- Verify writable engine data/log directories and /omega-media-library/ before processing.
- Check Imagick/ImageMagick or GD codec capability in Status before requesting AVIF/WebP output.
- Use image discovery first, then import only the source images you want Omega to manage.
Do not treat installation as proof of compatibility
AVIF/WebP availability depends on the server image editor and installed codecs. Responsive variants improve delivery options but do not guarantee a particular Lighthouse/Core Web Vitals score. HTML rewrite support is for eligible local markup; unusual templating/runtime-generated markup may require manual integration. Nginx does not process .htaccess and therefore requires equivalent server configuration for web-deny protections.
Product page and commercial specification
Review the complete public-facing capability specification, pricing and licence information for Omega Image Engine Pro.
