OmniPixy Browser Image Compressor

By omnipixy

★ 5.0/5 (1 ratings)0+ active installationsVersion 0.5.1

Compress images without sending them to any third-party server. Compression runs in your own browser, so your photos never leave your site.

Description

Most image compression plugins work by uploading your images to the developer’s cloud, compressing them there and sending them back. That is fine for a personal blog. It is a problem if you handle client photos, medical or legal documents, or anything covered by a confidentiality agreement, because your files leave your server and reach a third party you do not control.

This plugin does the opposite. Compression runs inside your own browser, on the computer where you are uploading from. Your original image is never sent anywhere except your own WordPress. Only the already-optimised file reaches your server, and no external service ever sees it.

Who this is for

  • Agencies and freelancers who signed a confidentiality clause and cannot send client images to a third-party CDN.
  • Sites in the EU that would rather not add another data processor to their GDPR records.
  • Anyone who wants smaller images without depending on an outside service that can change its terms, price or availability.
  • Intranets, staging sites and offline installs where an external API call is not possible or not wanted.

If what you need is to compress thousands of images already in your library in one click, a cloud plugin will do that faster. This one is for the case where the images must not leave your site.

Features

  • Automatic compression, no extra steps: works when uploading images in the Media Library, the editor’s media modal and WooCommerce.
  • 100% local processing in the browser: your original image is not sent to any external service.
  • Lightest format by default: each upload is tried in its original format and in WebP, and the smaller result is kept. In the settings you can force WebP or keep the original format instead.
  • Never makes it heavier: if recompression doesn’t reduce size, the original file is kept.
  • Quality control (1-100) and minimum size to recompress.
  • Optional WebP conversion with automatic fallback to the original format.
  • Max width/height resizing before compressing.
  • Automatic EXIF orientation fix and optional forced EXIF/GPS strip.
  • Savings notice after each upload.
  • Toggle to enable/disable compression.
  • Reprocess library: recompress the images you already uploaded with the saved settings, one by one, with an optional zip of the originals.
  • Optimize or convert selected images: pick images from the Media Library and recompress them or change their format, updating the old URLs in your posts.

Privacy

This plugin does not collect data, create accounts or call any external server. All processing happens in the administrator’s browser.

Guide and more tools

Step-by-step usage guide: Free WordPress plugin to compress images without third-party services. More free tools that run in your browser (compress, convert, resize, remove EXIF) at omnipixy.com.

Installation

  1. Upload the omnipixy-browser-image-compressor folder to /wp-content/plugins/.
  2. Activate the plugin from the “Plugins” menu.
  3. Adjust settings in “Media” → “OmniPixy”.

FAQ

Where exactly do my images go?

Nowhere. The compression runs in JavaScript inside your browser, on the machine you are uploading from. The file is read locally, compressed locally and the result is what gets sent to your WordPress. No request is made to omnipixy.com or to any other external server during the process. You can verify it: open your browser’s Network tab while uploading and you will see only the request to your own site.

Is this a GDPR thing?

It can help. If your current plugin sends images to a third-party cloud, that provider is a data processor you have to list in your records and cover in your privacy policy. With this plugin there is no such transfer, so there is no new processor to declare for image handling. It does not make your site GDPR-compliant on its own, and it is not legal advice, but it removes one data flow you would otherwise have to document.

Does it work offline or on an intranet?

Yes. Because nothing leaves the browser, the plugin works on a local install, a staging site behind a firewall or an intranet with no outbound internet access. Cloud compressors cannot do that.

Can I compress the images I already uploaded?

Yes, from Media > OmniPixy you can reprocess the existing library with your saved settings, one by one, with an optional zip of the originals. It is not a bulk one-click job like a cloud plugin: it runs in your browser, so it works through the images while the tab is open. For a very large library, a cloud plugin will be faster.

Which formats does it support?

JPEG, PNG and WebP are compressed. By default every upload is tried in its own format and in WebP, and the lightest one is kept (a PNG only gets lighter as WebP). You can also pick images in Media > OmniPixy and optimize or convert them; if the format changes, the URLs in your posts are updated. Animated GIFs and SVGs are never touched. HEIC and AVIF are not supported yet.

Is quality lost?

JPEG compression uses a configurable quality factor (80% by default) and only applies if the result is lighter than the original (or if forced EXIF strip is enabled). Lower quality means a smaller file and less detail.

Which PHP version should I use?

PHP 8.3 or newer. PHP 8.2 reaches end of life on 31 December 2026. On 21 October 2026 the PHP project released fixes for two critical remote code execution vulnerabilities (CVE-2026-109618 and CVE-2026-109619, “php2shell”) in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. PHP 8.1 and older receive no official releases; the PHP team published source backports for 7.4, 8.0 and 8.1, and some Linux distributions ship patched packages. If your site runs an unpatched version, update PHP or ask your host. This plugin cannot protect you from a vulnerability in PHP itself, because those flaws are reached before any plugin code runs.

Does it work with WooCommerce?

Yes. WooCommerce uses the same WordPress media uploader, so it inherits this compression.

Does “Reprocess library” overwrite my images?

Yes. Originals are replaced and thumbnails regenerated; there is no undo. Make a backup first. Only the main image file is rewritten: when WordPress keeps an unscaled original (large images), that extra file is left untouched, except when the format changes (PNG to WebP), where the unscaled original is removed as well. The optional originals zip is built in browser memory (may fail on multi-GB libraries), is lost if you close the tab mid-way, and does not restore anything by itself. Images served from another domain (CDN) may fail to download. Processing is one image at a time.

Screenshots

Changelog

0.5.1

  • Fixed the tags line: wordpress.org only keeps the first 5 tags and drops the rest silently, so the privacy tags were being lost. The 5 that remain are now the ones that matter: image compression, compress images, gdpr, privacy, webp.
  • No code changes.

0.5.0

  • Readme rewritten around the privacy use case: who this is for, where the images actually go, GDPR and offline/intranet use.
  • Added the “Can I compress the images I already uploaded?” answer, with the honest limit about bulk reprocessing.
  • Expanded the tags so the plugin can be found by people searching for a compressor that does not use a third-party cloud.
  • No code changes. Same behaviour as 0.4.9.

0.4.9

  • Fixed: if regenerating the thumbnails failed after converting an image to WebP, the attachment was left pointing at a file with the wrong extension and without thumbnails. The original is now backed up before anything is written and fully restored on failure.
  • Fixed: the upload queue could stay paused forever if handling the compressed file threw an error, leaving the rest of the batch unuploaded.
  • Fixed: a failed compression in the block editor aborted the upload instead of sending the original file.
  • Fixed: “Reprocess library” reported “Nothing to process” when the server had actually failed, and a expired session was counted as “couldn’t download an image”. Both now say what happened.
  • Fixed: changing “Always convert to WebP” or “lightest format” did not mark already processed images as pending again, so the reprocess skipped them.
  • Improved: the old thumbnails are only deleted once the new ones exist, and only the ones that are no longer used.
  • Improved: the settings stylesheet is no longer loaded on every admin screen; only the savings notice has its own small stylesheet.
  • Improved: the originals zip reads the files one at a time instead of holding them all in memory at once, and canvases are released as soon as they are encoded.
  • Improved: the savings notice no longer swallows clicks on the page underneath it.
  • Improved: the smoke test now covers 40 assertions, including all of the above.

0.4.8

  • Fixed: the confirmation dialog of “Reprocess library” did not show correctly. With a single pending image it displayed “undefined”, and with several it failed to open. It now uses the proper singular/plural message.
  • Improved: clarified the format description in this listing (the plugin keeps the lightest of the original format and WebP by default; you can force WebP or keep the original in the settings).

0.4.7

  • Improved: the savings notice now shows the quality used (“OmniPixy saved 2.629 KB · quality 45%”). If a setting stops working, you see it on the first upload.
  • Improved: settings are passed to the browser with their real types (number, boolean) instead of text, so this kind of bug can’t come back.
  • Improved: PHP 8.3+ is now recommended, and the FAQ explains the php2shell fixes (CVE-2026-109618 / CVE-2026-109619) and which PHP versions are patched.
  • Improved: translatable strings use standard gettext placeholders, and the HTML in the footer goes through wp_kses.
  • Added: a smoke test (25 assertions) and a version check that runs on every commit, so a release can’t ship with mismatched versions again.

0.4.6

  • Fixed: the Quality setting had no effect, everything was compressed at 80%. WordPress turns every value passed to the browser into text, so the quality never arrived as a number.
  • Fixed: the reprocess now generates the thumbnails before deleting the original file, so a failure can no longer leave an attachment without a file.
  • Fixed: removing EXIF from an image could report negative savings.
  • Fixed: plural forms in the reprocess and selection messages (“1 image” instead of “1 images”).
  • Improved: the upload error is reported as such instead of “not a valid image”.
  • Improved: the nonce is renewed during long reprocess runs, and the server upload size limit is enforced.
  • Improved: the excerpt of posts is updated too when image URLs are rewritten.
  • Fixed: numbers in the notices use the separator of your language.
  • Improved: clearer wording in the settings panel.

0.4.5

  • Fixed: “Always convert to WebP” had no effect while “lightest format” (on by default) was enabled; it now takes priority.
  • Fixed: leaving Quality empty saved 1%; it now falls back to 80.
  • Fixed: “Reprocess library” ignored the minimum size setting.
  • Hardened: the reprocess endpoint now refuses attachments that are not images.

0.4.4

  • Fixed: animated PNG and animated WebP files are no longer recompressed (the canvas kept only one frame).
  • Fixed: the “lightest format” option is now removed when the plugin is deleted.

0.4.3

  • Improved: “Reprocess library” now loads the image list in pages, so large libraries no longer build one huge query.
  • Fixed: singular wording in the reprocess confirmation (“1 image”).

0.4.2

  • New: link to the usage guide on the Plugins screen and in the settings page footer.

0.4.1

  • New: automatic lightest format on upload (original vs WebP, the smaller one is kept); WebP files are recompressed too.
  • New: optimize or convert selected images from Media > OmniPixy; when the format changes, old URLs in posts and pages are rewritten.
  • Renamed to OmniPixy Browser Image Compressor; translations now come from translate.wordpress.org.

0.4.0

  • New: “Reprocess library” button recompresses images already in the Media Library (browser-side, keeps format, regenerates thumbnails).
  • Fixed: panel CSS missing when compression was disabled; duplicate “uploading…” placeholder; negative savings notice.
  • Fixed: images larger than the server upload limit are now compressed instead of rejected before the plugin could run (Media Library, Add Media File page and block editor).
  • Fixed: classic “Add Media File” page and Gutenberg direct uploads (REST) are now covered.
  • Redesigned settings page to match omnipixy.com (light/dark switch, progress bar).
  • Reprocess uses WP_Filesystem and only removes old thumbnails after the new file is written; plugin slug is now omnipixy-browser-image-compressor.
  • Fixed: reprocess no longer marks an image as done when it can’t be downloaded (HTTP errors now count as errors); the upload queue can’t stay paused if compressing fails.
  • Reprocess remembers which settings it used: changing quality or max size makes images pending again. Download timeout (30 s) and clearer error reasons.
  • Max width/height capped at 20000 px; the file types filter is sanitized; the upload size limit is lifted on each uploader instance too.
  • Accessibility: theme switch and progress bar announce their state.

0.3.1

  • i18n: English as source language; Spanish translation (es_ES) bundled. Plugin now follows the WordPress site language (English by default; Spanish when locale is es_ES).

0.3.0

  • Max width/height resizing before upload.
  • Automatic EXIF orientation fix (portrait photos).
  • Forced EXIF/GPS strip even without compression.

0.2.3

  • Fixed: unchecked checkboxes weren’t saved; README limitations updated.

0.2.2

  • Covered the second WordPress upload path: Gutenberg Image block that uploads directly to the REST API (without going through plupload).

0.2.1

  • Fixed infinite loop when file doesn’t improve (e.g. PNGs or already compressed images).
  • Complete cleanup of all registered options on uninstall in uninstall.php.
  • Numeric array normalization for filtered MIME types.
  • Visual identity fixes: SVG brand icon, <h1> heading and cards aligned with the official site.

0.2.0

  • Quality and minimum size controls from the panel.
  • Optional WebP conversion with fallback to original.
  • Cumulative savings notice after upload.

0.1.0

  • Initial version: intercepts upload with plupload and compresses JPEG/PNG in the browser before sending to the server.