MiniPx for Chrome

The same image tools, one click from wherever you already are. Compress a screenshot before you paste it into a ticket. Convert a PNG someone sent you. Resize a photo down to the size a form will accept. None of it leaves your machine.

Get MiniPx on the Chrome Web Store

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.

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 quality presets, a target file size in KB, and the platform presets from the site.
• Convert — between JPEG, PNG, WebP, AVIF, BMP and JFIF.
• Resize and crop — by pixels, by percentage, or to one of the social and document presets.
• Rotate, flip and circle crop — the geometry tools, exact and lossless where the format allows it.
• Greyscale, invert, blur and pixelate — the filters, including pixelating a region to redact it before you share a screenshot.
• EXIF strip and JPEG DPI — the two byte-level tools: remove location and camera metadata, or set the DPI a print shop asked for.

Which tools open the website 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, 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.

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.

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.