Your images are processed in your browser — Cloud HD (Pro, opt-in) is the only exception

Changelog

MiniPx has shipped 145 releases since 28 May 2026. Below is what the product does that it did not use to, followed by the full dated list. The notes are deliberately not tied to version numbers: what matters to you is that the behaviour exists, and attributing each one to a single release turned out to be a reliable way to get it wrong.

What changed

A RAW, PDF or video file is sent to the tool that can take it

Dropping a camera RAW on the compressor used to end in “not an image”. Now the notice names what the file is and links the converter for that camera format; a PDF gets a one-tap switch to PDF mode; a video or a Photoshop file gets an honest line about what to export first. The tool stays ready for the next file.

Wide images keep their size, or say why not

WebP cannot hold a side longer than 16,383 pixels. Rotate, flip, blur, pixelate, invert and grayscale used to cut such an image down without a word; they now say so and PNG or JPEG keeps the full size. Exam photos whose rules give a printed size (UPPSC, NEET-PG) come out at that size instead of at the original pixel count.

Firefox does not wait on a slow AVIF

Firefox encodes AVIF single-threaded, and the automatic format pick could spend most of a minute on a photo that other formats finish in seconds. The pick now times a small probe first and skips AVIF when the full frame would blow the budget, saying which format was used instead. AVIF stays one click away in the format menu.

An iPhone photo saved as .jpg still opens

A share sheet or a sync step often saves an iPhone HEIC photo with a .jpg name. The compressor and converters read what the bytes actually are, so that file goes to the HEIC decoder and comes out as an ordinary image instead of being refused as a variant we could not open.

A photo too big for your device can still be compressed

An image over the size this device can work on used to be turned away. Now the compressor names the largest size it can produce here and offers to compress it at that size. Nothing is resized unless you choose it, and the result says it was made smaller.

A slow start does not fail the file

On a slow connection the compressor’s background worker can take a long time to load before it says anything. If it stays silent before any compression work has begun, the file is finished in the page itself instead of being reported as taking too long.

Intact photos are not called corrupt

Samsung and Pixel phones write a complete JPEG with a video appended to the end, and a JPEG keeps its frame header wherever its EXIF or colour data leaves room. Both used to make a perfectly good photo read as damaged. We now scan for the end marker rather than demanding it be the last thing in the file, scan far enough to find it past a video that runs to megabytes, and ignore a marker that turns out to be inside an embedded thumbnail.

A file we cannot open is declined, not failed

Tools judge a file by its actual bytes rather than the label the browser puts on it. If something genuinely cannot be opened you are told it was declined and why. Where a truncated photo still has a usable part, we offer that part back, cropped, with the percentage stated before you commit — per file, and only if you ask. An honest limit: Chromium refuses a truncated JPEG at any cut level, so that last part helps Safari and Firefox rather than everyone.

Automatic format picks are verified at full size

Choosing a format from a small probe tile gets it wrong, because the formats do not scale the same way. The probe still shortlists, but the winner is confirmed against one full-size challenger before anything is shipped. On one photograph that turned a 99.6 KB AVIF into an 80.9 KB JPEG.

Lossless PNG really is lossless

Decoding a PNG through a canvas quietly loses precision in transparent areas — measured at 196,156 of 262,144 pixels changed on a test image. The lossless path never decodes or repaints; it repacks the compressed bytes, so every pixel comes back identical.

A way to say whether a result was any good

Every finished run ends with a thumbs up or down and a link to follow the project. One click, and it is the only direct signal we get about whether a tool did what you wanted.

Cloud HD for Pro, and what stays free

Seven AI tools have a server-side Cloud HD path for Pro subscribers. Four — restoration, colourising, enhancement and object removal — are Cloud HD only. Background removal, upscaling and passport photos keep their free in-browser versions and simply gain Cloud HD as an option. A Cloud HD image is deleted when the run finishes, and within 24 hours in every case; the free tools still never leave your browser.

A Chrome extension

The compressor runs as a browser extension using the same engine as the site. It bundles no AI and no Pro features — the AI tools link back here. Chromium-based desktop browsers show an "Add to Chrome" link in the site header; on other browsers the extension simply is not offered.

Scrollable boxes reachable by keyboard

Fifty-five scrollable code blocks across twenty pages could not be scrolled without a mouse, which fails WCAG 2.1.1. Every scrollable box now takes keyboard focus and announces itself to a screen reader, and a gate refuses any new one that does not.

A performance budget that fails the build

Page weight and load timings are measured against fixed ceilings, and a build that slips past them does not ship.

Every page has its own preview card

Share any page and the card is made for that page rather than being one generic image — including the right privacy line, since the free tools run in your browser and the Cloud HD ones do not.

Every release

All 145, newest first, from the repository's own tags. Most are fixes, tests and groundwork rather than anything visible.

All Image Tools

AI Tools

Compress for Platform

Solutions by use case