Omega Image Engine – Documentation

Version 1.0.0 Alpha & Omega Limited omegawebapps.com

Omega Image Engine is a high‑stability, fully local WordPress image optimization engine. It generates WebP variants, adds safe custom sizes, rewrites HTML <img> tags, and provides batch processing and Media Library status — all without cloud dependencies.

1. Features Overview

• Local WebP generation for JPG/PNG uploads.
• Omega custom sizes: omega_small, omega_medium, omega_large.
• Safe sizing — extends WordPress sizes, does not disable core sizes.
• Batch processor to process the entire Media Library in controlled chunks.
• Recursive scan of /wp-content/uploads/ to build a processing queue.
• HTML rewriter that swaps JPG/PNG URLs for WebP only when the file exists.
• Media Library status column showing whether an image is optimized.
• Fully local — no cloud APIs, no external services, no telemetry.

2. Installation

1. Upload the plugin folder to /wp-content/plugins/omega-image-engine/.
2. Activate Omega Image Engine from the WordPress “Plugins” screen.
3. Open Omega Image in the WordPress admin sidebar.
4. Run a scan and batch process (see below).

3. Admin Dashboard

The plugin provides a unified Omega UI with four tabs:

• Overview — feature summary
• Image Engine — scanning tools
• Batch Processor — AJAX batch runner
• Status — diagnostics

3.1 Scan Uploads

Located under the Image Engine tab.

• Runs a recursive scan of /wp-content/uploads/.
• Finds JPG, JPEG, PNG, and WebP files.
• Builds the processing queue (omega_batch_queue).
• Displays the number of discovered images.

3.2 Batch Processor

Located under the Batch Processor tab.

• Processes 20 images per batch.
• 2‑second delay between batches.
• Generates WebP variants.
• Updates attachment metadata.
• Live log output in the admin UI.

4. Image Processing

4.1 Custom Omega Sizes

Registered by Image_Registry:

• omega_small — 320px
• omega_medium — 768px
• omega_large — 1536px

These sizes are additive and safe for all themes, builders, and WooCommerce.

4.2 WebP Variant Generation

Handled by Image_Processor:

• Uses wp_get_image_editor().
• Resizes to Omega widths.
• Saves as .webp.
• Filenames follow WordPress conventions: basename-WIDTHx0.webp.
• Metadata is merged into the attachment.

5. HTML Rewriting

The HTML_Rewriter class filters the_content:

• Targets only JPG/PNG images.
• Ignores external URLs.
• Builds a WebP URL and converts it to a filesystem path.
• Safety check: only rewrites if the WebP file exists.
• Replaces only the src attribute.

6. Media Library Integration

The Library_UI class adds an “Omega Status” column:

• Optimized — Omega metadata exists.
• No Omega Data — image not yet processed.

7. Troubleshooting

• No Omega Data — run Scan + Batch Processor.
• WebP not appearing — ensure server supports GD or Imagick.
• HTML not rewriting — verify WebP file exists in uploads.
• Batch stops early — refresh and run again; queue persists.

8. Support

For support, visit:

omegawebapps.com/support