Nexora Media – Image Optimization

Nexora Media is the intelligent image optimization plugin for WordPress. It generates WebP variants of every image you upload, swaps them in automatically for public visitors, and keeps your editors and page builders untouched.

Safe by default. Logged-in editors, Elementor previews, Divi builder, Bricks, Oxygen, customizer, and any builder preview frame always see the original image. Nothing breaks while you build.

Background optimization queue. Heavy variant generation runs in safe batches so uploads stay snappy and WordPress stays responsive. Manual mode is the default — automatic processing is an explicit opt-in.

Adaptive frontend delivery. When enabled, eligible WordPress image URLs are seamlessly replaced with the optimized WebP for logged-out visitors. The original file stays in place and is served as a fallback whenever needed.

Queue health that talks back. When something goes wrong — a stale lock, a permission error, a memory issue — Nexora Media surfaces a clear alert with a recovery action. No more silent failures, no more “the queue stopped and I don’t know why”.

Why “safe” matters

Most image optimizers break something. A bad src rewrite turns a working lightbox into a blank popup. An aggressive cache strategy serves stale images on cached pages. A naive lazy-load tag kills above-the-fold paint.

Nexora Media is conservative on purpose. It:

• Detects every major page builder and bypasses delivery rewriting during editing
• Skips lightboxes, galleries, carousels, logos, menus, and any image marked data-no-lazy, data-no-webp, or fetchpriority=high
• Only swaps URLs when the WebP variant is actually smaller than the original
• Never deletes your originals
• Provides a one-click “Recover stuck queue” action if anything ever stalls

Features

• WebP generation — Imagick preferred, GD fallback
• Background optimization queue with safe batching and worker locking
• Adaptive frontend delivery that swaps WordPress image URLs to WebP for public visitors
• Responsive image variants (320, 640, 960, 1600 by default, configurable)
• Lazy loading + decoding=async with intelligent hero-image guards
• EXIF stripping for privacy and smaller files
• Per-image controls to force original delivery on a single image when needed
• Queue health dashboard with structured error logs, stale-lock detection, and one-click recovery
• WP-CLI compatible cron for automated processing
• Modern React-based admin with live queue progress and per-image cards

Pro extensions

There aren’t any. Nexora Media is fully free, GPL, and complete. New features ship to everyone.

On the Roadmap

• One-click CDN cache purge for Cloudflare, BunnyCDN, and other pull-zone CDNs after a variant is regenerated
• Optional WebP/AVIF for theme and plugin CSS background images
• Bulk re-optimization with a configurable quality target

Roadmap items are shown in the app’s Roadmap page marked “Coming Soon” and are not yet active.

Plays well with

• Elementor (free + Pro)
• Divi
• Bricks
• Oxygen
• WPBakery
• Beaver Builder
• Yoast SEO, Rank Math, AIO SEO
• WP Rocket, W3 Total Cache, LiteSpeed Cache, Cloudflare
• WooCommerce
• Nexora Engine (sibling plugin) — when active, Engine handles inline-CSS image rewriting during static site generation so Media stands down on the_content rewriting to avoid double-processing

Source code & development

Nexora Media is fully open. The admin interface is a React + TypeScript application; the human-readable source lives in the frontend/ directory that ships inside the plugin, and it is compiled with Vite to assets/dist/nexora-media.js. Nothing is obfuscated or minified beyond a standard production build.

The complete, unminified source — including the React/TypeScript admin UI and build instructions — is publicly available at:

https://github.com/auralogicslabs/nexora-media

To reproduce the compiled bundle from source (see BUILD.md in the repository for full details):

This runs Vite (vite.config.ts) over the frontend/ sources and writes the bundle to assets/dist/. Node.js 18+ and npm 9+ are required. The plugin runs entirely from the built output at runtime; node_modules/ is a development dependency only and is not shipped.