Documentation

Optimize every new upload

Once active, OmegaPix works at the point of upload — there's no separate step in your publishing flow.

1. Upload an image as you normally would (Gutenberg, Classic Editor, or the Media Library).
2. OmegaPix resizes it to your configured maximum dimension if it's oversized.
3. It generates next-gen versions, preferring AVIF and falling back to WebP.
4. The Media Library status column shows the optimization state and file-size savings.

Tip: Optimization is non-destructive by default. The optional Replace Original mode is off by default and flagged Beta — leave it off unless you've tested it on your site.

Optimize existing media

New uploads are handled automatically, but your existing library can be brought up to date in one pass.

1. Go to the OmegaPix bulk tool in your admin.
2. Click Bulk Optimize.
3. Watch live progress as images are processed in batches.

Why it's batched

Large libraries can exceed PHP execution limits if processed all at once. OmegaPix runs the bulk job as timeout-safe AJAX batches, so it keeps going steadily without hitting server timeouts — and you can leave the page and come back.

Reprocessing a single image

From the Media Library, you can re-optimize any single attachment with one click — useful after changing your quality or max-dimension settings.

Next-gen formats

OmegaPix produces next-gen image formats locally, with no cloud, no third-party servers, and no credits.

Format preference

1. AVIF is preferred — it typically yields the smallest files.
2. WebP is the fallback when AVIF isn't supported.
3. If neither is available, OmegaPix skips next-gen conversion gracefully and still serves your optimized original.

What your server needs

OmegaPix is capability-aware: it inspects what your GD/Imagick build can actually do and reports it honestly in the admin, rather than failing silently.