Image Compressor Chrome Extension
Compress, convert and resize images from the toolbar — or right-click any image on any page. Thirteen tools run inside the extension on your own machine, using the same WebAssembly codecs as minipx.com. Nothing is uploaded, because there is nowhere to upload it to.
Short version
- Thirteen tools run inside the extension — compress, convert, resize, crop, rotate, flip, greyscale, invert, blur, pixelate, circle crop, EXIF strip and JPEG DPI.
- Everything else opens on minipx.com, marked with an external-link arrow so you always know which is which.
- No account, no upload, no analytics. The extension makes zero network requests of its own.
- Free, and it stays free. It is the free tier of MiniPx, in a toolbar.
What it looks like
Four screenshots from the shipping build — the popup, a finished batch, the tool list and the settings.
What it does without asking anyone
Click the MiniPx icon and you get a file picker and a list of tools. Pick files, pick a tool, and the work happens in a worker thread on your own machine using the same WebAssembly codecs the website uses: MozJPEG, libwebp, OxiPNG and AVIF. The output lands in a results list with the before and after byte counts, and you download what you want — one at a time, or the whole batch as a zip.
You can also drag images straight onto the popup, or right-click an image anywhere on the web and choose to compress or convert it. That last one is the only time the extension ever reads something outside itself, and it asks first — see below.
Which tools run locally
Thirteen, and they cover the work most people open MiniPx for:
- Compress — JPEG, PNG, WebP and AVIF, with a balanced, maximum-quality or smallest-file preset, an optional target size in KB and an optional maximum dimension. The website version of this is the JPEG compressor.
- Convert — output as JPEG, PNG, WebP or AVIF. It reads JPEG, PNG, WebP, AVIF, GIF and BMP; HEIC and camera RAW need the image converter on the site.
- Resize and crop — by width, height or percentage, and cropping to a region. See resize image for the presets.
- Rotate, flip and circle crop — the geometry tools, exact and lossless where the format allows it. Also on the site as rotate and circle crop.
- Greyscale, invert, blur and pixelate — the filters, including pixelating a region to redact a face, a name or an account number before you share a screenshot.
- EXIF strip and JPEG DPI — the two byte-level tools: remove location, camera and timestamp metadata, or stamp the print density a print shop asked for.
Why an extension when the website already does this
Because the website costs you a tab and a drag. The extension costs you a click.
- Right-click any image on any page. You do not have to save it first. Right-click, compress or convert, and the result is in the popup.
- It is in the toolbar, not in a tab. Compress a screenshot before you paste it into a ticket, without losing the ticket.
- It works with no connection. The codecs ship inside the extension, so a flight, a train or a locked-down network changes nothing.
- Your defaults persist. Output format, quality preset and theme are remembered in Chrome, so the second file takes one click instead of four.
The website is still the better place for a big batch, for the tools listed below, and for anything you want to do on a phone. See the full feature list for what lives where.
Which tools open minipx.com instead, and why
The background remover, the upscaler, the passport photo maker, OCR, the PDF tools, HEIC and camera RAW input, vectorising, favicon generation and GIF work all stay on minipx.com. This is not a paywall. Those tools need neural network weights measured in tens of megabytes, or WebAssembly runtimes of several megabytes each, or decoders that need a real page rather than a worker. Shipping them inside an extension would mean a download the size of a small application before you compressed your first file, updated through a store review queue every time a model changed.
So the extension shows them in the same list, marked with an external-link arrow, and opens the tool on the website in a new tab. Same tools, same privacy model, same free tier. The website has always run those in your browser too — the heavy ones are the reason MiniPx Pro exists on the site, and none of that gating is inside the extension.
Permissions, in plain English
The extension asks for two permissions at install time and one more only if you use the right-click menu.
- Context menus — to add the two MiniPx entries when you right-click an image.
- Storage — to remember your default output format, quality preset and theme. Three settings, stored in Chrome, never sent anywhere.
- Access to the site you are on — optional, and requested only at the moment you right-click an image and choose a MiniPx action. Decline it and everything else still works; you can drag the image onto the popup instead. The extension never asks for this at install time and never keeps it for sites you have not used it on.
What it does not ask for, deliberately: no tab access, no download permission, no history, no cookies, no identity. The full statement is in the extension privacy policy.
Privacy
The extension makes no network requests of its own. There is no analytics, no telemetry, no remote configuration and no update ping beyond the one Chrome itself performs against the Web Store. Your images are read from disk, processed in memory, and written back to disk when you download them.
The one network request that can happen is the one you ask for: when you right-click an image on a page and choose a MiniPx action, the extension fetches those image bytes from the site that is already serving them to you. If that fetch is blocked, or you decline the permission, it says so and asks you to drag the file in instead.
This is the same promise the website makes, and you can check it the same way: open the DevTools Network panel, use the extension, and watch nothing leave. The site's own privacy policy covers minipx.com itself, including the one page that does talk to our server.
It stays in step with the site
The extension reads the same tool list this website renders, from the same file, and the same capability map decides which tools it runs locally. Adding a tool to MiniPx without deciding what the extension does with it fails the build. That is deliberate: the alternative is an extension that quietly falls a version behind and nobody notices for a month.
Questions people ask before installing
Does it install on Edge, Brave or Opera?
Yes. It is a Chrome Web Store extension, so it installs in Chrome and in any Chromium browser that accepts Web Store extensions — Edge, Brave, Vivaldi and Opera among them. Edge and Opera will each warn you once that you are installing from another store; that warning is about the store, not about this extension.
Does it work offline?
Yes, for everything it runs locally. The codecs ship inside the extension, so compressing, converting, resizing, cropping, rotating, flipping, greyscaling, inverting, blurring, pixelating, circle-cropping, stripping EXIF and setting JPEG DPI all work with no connection at all. The two things that need the network are the tools that open minipx.com in a tab, and fetching an image you right-clicked from the page that is serving it.
Does it phone home?
No. The extension makes no network requests of its own: no analytics, no telemetry, no remote configuration, no account and no update ping beyond the one Chrome itself performs against the Web Store. The only request it can make is the one you ask for, when you right-click an image and it fetches those bytes from the site already showing them to you. You can check this yourself in the DevTools Network panel.
Is it free, or do I need Pro?
It is free, and it stays free. The extension is the free tier of MiniPx in a toolbar — there is no account, no sign-in and no licence check anywhere in it. MiniPx Pro is a separate thing that lives on the website and unlocks the heavier tools there.
Why is there no Firefox version?
There is not one yet. Firefox uses a different extension store with its own review process and its own manifest differences, and shipping a build nobody maintains is worse than shipping none. Until then, every tool the extension runs also runs on minipx.com in Firefox, in your browser, with the same no-upload guarantee.
How does it stay in sync with the website?
It reads the same tool list this website renders, out of the same file, and the same capability map decides which tools it runs locally and which it opens on minipx.com. Adding a tool to MiniPx without deciding what the extension does with it fails the build, so the extension cannot quietly fall a version behind.
Installing
Get it from the Chrome Web Store. It works in Chrome and in any Chromium browser that accepts Web Store extensions, which includes Edge, Brave, Vivaldi and Opera. There is no Firefox build yet.
Questions, bugs or a tool you want moved into the local set: contact@minipx.com.