Why PixBulk exists: 88 batch image tools that never upload your files. Meet the local-first philosophy behind every tool.
When you compress a photo on a typical online tool, the file travels to their server, gets processed, and travels back. Along the way it can be logged, retained, analyzed or breached. For memes that's fine. For passport scans, family photos, medical images or client work, it's a risk you were never asked to take.
PixBulk flips the model: your browser IS the server. Compression, conversion, cropping, GIF editing — all of it runs on your device through Canvas, Web Workers and pure-JavaScript engines. Load the page, and you can even go offline. Nothing you process is ever transmitted, because there is no transmission.
Because there are no processing servers, there are no processing bills. PixBulk costs the price of static hosting — one of the cheapest things on the internet. If the project grows, a lightweight premium tier may fund development; the core tools you use today will stay free, without watermarks, always.
Zero files uploaded since day one — by architecture, not by policy.
PixBulk is built and maintained by a small, fully remote team of front-end engineers and imaging enthusiasts. We have spent years working on browser-side graphics: canvas pipelines, WebAssembly codecs and the unglamorous plumbing that makes large image batches feel instant. There are no investors steering the roadmap and no ad network monetizing your attention — development is funded by the project itself, and every feature starts from a real workflow that we or our users actually struggle with.
We publish working principles instead of marketing promises: every tool must work without an account, must never transmit your files, must state plainly what it cannot do, and must stay fast on mid-range hardware. When a tool fails any of those tests in our own review, it is labeled beta on its page until it passes — you will find the full criteria on the methodology page below.
Each tool ships only after a documented review pass — the same checklist published on our methodology page. We verify output fidelity against reference images with known color profiles and metadata, judge compression quality with structural-similarity comparisons rather than eyeballing, and audit the browser's network panel to confirm that zero requests leave your device while a tool runs. The criteria, the test fixtures and the pass thresholds are all described there in plain language, so you can hold us to them.
PixBulk stands on well-regarded open-source work, and we say so on every tool page that uses it: WebAssembly codec builds from the jSquash project power the AVIF and JPEG engines, the gifenc and gifuct-js libraries handle GIF encoding and decoding, and JSZip packages your batch downloads. We contribute fixes upstream rather than forking silently, and we pick libraries the same way we build tools — audit the code, check the license, keep everything running on your device.