About Pixora

Almost every free image tool works the same way: you upload your file, a server processes it, and you download the result. That design has three problems, and only one of them is about privacy.

The privacy problem is obvious. Your passport scan, your client’s unreleased product render, the medical form you needed to shrink for an upload limit — all of it lands on someone else’s hard drive. The promise to delete it in 24 hours is a promise, not a mechanism.

The second problem is speed. Uploading a 40 MB folder of photos over a typical home connection takes longer than compressing them would. Your laptop has eight cores sitting idle while it waits for a queue on a shared server.

The third is money. A server that decodes images costs real money per image, so a free tool built that way must either sell your data, throttle you, or nag you toward a subscription. Move the work to the browser and the marginal cost of a user is essentially zero — which is exactly why we can afford to keep every tool free, unlimited and unwatermarked.

Browsers have been able to read local files without uploading them for over a decade. What changed recently is that they can now run real, production image codecs at close to native speed, thanks to WebAssembly.

Pixora uses the same encoders that desktop software and image CDNs use: MozJPEG for JPEG, oxipng for PNG, libwebp for WebP, libavif for AVIF, and libheif to decode the HEIC photos your iPhone takes. They are compiled to WebAssembly and run in Web Workers, so several images encode in parallel across your CPU cores while the interface stays responsive.

Nothing about this is exotic any more. It is simply the architecture nobody bothers to use, because a server is easier to build and easier to monetise.

Advertising, and nothing else. Because there is no image-processing server, hosting a million compressions costs about as much as hosting a blog. Ads cover it comfortably.

Ad code runs in a sandboxed cross-origin iframe. It cannot read the files you open, the canvas we draw them on, or the results you download. Read the privacy policy for the specifics.

A privacy promise you cannot check is marketing. Here are two ways to check this one, in under a minute each.

1. 1Open your browser developer tools, go to the Network tab, then compress an image. Watch for a request carrying your file. There will not be one.
2. 2Load any tool page, then switch off your Wi-Fi or unplug the network. Compress, convert and resize as much as you like. Everything keeps working, because none of it needed the network in the first place.