OMEGA IMAGE ENGINE DOCUMENTATION · WordPress Plugin 2.0.0

Omega Image Engine documentation

Complete Omega Image Engine WordPress Plugin 2.0.0 documentation covering all audited customer-facing capabilities, installation, setup, safety, troubleshooting and support.

PRODUCT OVERVIEW

What Omega Image Engine does

A WordPress-native image engine built around the active WordPress image editor and attachment APIs. Version 2.0.0 preserves core attachment metadata, keeps originals as fallbacks and stores Omega variant metadata separately.

27 documented capabilities

The Features reference below maps every meaningful customer-facing capability identified in the audited 2.0.0 product codebase.

Local-first operation

The core functions described on this page are designed to operate locally on the customer website/server rather than requiring an OmegaWebApps cloud processing subscription. This reduces dependency on remote processing services and keeps operational state under the website owner’s control, subject to the hosting/platform environment.

Platform-specific architecture

WordPress-native hooks, capabilities, nonces, media/admin APIs and bounded administrator workflows.

Documentation map

Use the section that matches the job you are performing.

Features

Complete audited capability reference with descriptions.

Open Features

Installation

Requirements, preflight checks and installation procedure.

Open Installation

Setup

Recommended configuration order and safe production workflow.

Open Setup

FAQ

Commercial and product-specific technical answers.

Open FAQ

Troubleshooting

Common failure modes and corrective actions based on the engine boundaries.

Open Troubleshooting

Support

What to check, what information to collect and where to get help.

Open Support

Core operating workflow

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

Requirements

WordPress 6.0+.
PHP 7.4+.
GD or Imagick through the WordPress image editor.
WebP/AVIF generation requires corresponding codec support in the active editor.

Safety architecture

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.

Technical boundaries

AVIF/WebP output depends on the host and active WordPress image editor. Themes, page builders, custom markup and caching/CDN layers can affect final frontend picture/srcset delivery. Image optimization cannot by itself guarantee a specific page-speed or Core Web Vitals score.

Product page and commercial specification

Review the complete public-facing capability specification, pricing and licence information for Omega Image Engine.

View Omega Image Engine