WordPress-Native Image Processing
Uses wp_get_image_editor() and the active GD/Imagick editor instead of a remote conversion service.
OMEGA IMAGE ENGINE FEATURES · WordPress Plugin 2.0.0
Complete audited feature and capability reference for Omega Image Engine WordPress Plugin 2.0.0, covering all meaningful customer-facing functions.
COMPLETE CAPABILITY REFERENCE
This reference describes the product capabilities exposed to customers and administrators. Internal helper methods are represented through the capability they implement rather than published as meaningless source-code function names.
Uses wp_get_image_editor() and the active GD/Imagick editor instead of a remote conversion service.
Creates WebP files when the active WordPress image editor supports WebP output.
Creates AVIF files when the active editor/host provides AVIF support and reports capability status in the dashboard.
Generates Omega 320px, 768px and 1536px variants when those widths are smaller than the source image.
Creates modern-format siblings for existing WordPress-generated attachment sizes, extending optimization across normal Media Library derivatives.
Builds modern-format picture sources with the original WordPress image retained as the final fallback.
Builds responsive source sets from available Omega and WordPress image variants for browser-native image selection.
Integrates responsive output with WordPress attachment-image rendering without replacing core attachment records.
Can enhance eligible image markup in post/page content while preserving original fallback delivery.
Optional setting processes newly created image attachments as they enter WordPress.
Dashboard controls allow the operator to choose conversion quality settings for supported modern formats.
Scans processable WordPress image attachments to build the optimization queue and current status.
Runs existing-library processing in bounded AJAX chunks protected by manage-capability checks and nonces.
Supports resumable processing rather than requiring the full Media Library to finish in one request.
Adds Omega optimization status information so individual attachments can be reviewed from WordPress media administration.
Stores Omega-generated variant data separately in _omega_image_engine_variants.
Leaves _wp_attachment_metadata intact rather than replacing WordPress core image-size records.
Never requires replacing/deleting the original attachment; originals remain the compatibility fallback.
Confirms exact duplicate content with SHA-256 after candidate grouping.
Protects attachment originals, WordPress-generated sizes and Omega variants from duplicate deletion.
Deletion is limited to unregistered orphan duplicate files inside uploads after preview/confirmation.
Provides an administrator preview of duplicate groups before deletion.
Stores local diagnostic/processing state with atomic writes to reduce partial-state corruption.
Removes Omega metadata/state associated with an attachment when WordPress deletes that attachment.
Removes plugin settings and Omega attachment metadata while intentionally preserving generated files so cached/external references are not unexpectedly broken.
Plugin administration assets are limited to Omega screens rather than globally loading throughout wp-admin.
No required cloud optimization API, telemetry or remote processing dependency.
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.
Review the complete public-facing capability specification, pricing and licence information for Omega Image Engine.