Skip to main content
All posts
EngineeringUpdated:

Inside PixSip: Running MozJPEG and Friends in Your Browser

A look under the hood of a browser-side image compressor: WebAssembly codecs, a worker pipeline, local HEIC decoding and browser ZIP export.

PixSip looks simple — drop images, get smaller files — but there is a real compression pipeline behind it, running entirely in your tab. The free plan accepts 20 images per batch, 5 MB each, with no daily image quota; paid plans accept up to 500 per batch. Here is how the pieces fit together.

The encoder stack

We run the same open-source codecs that power Google's Squoosh, compiled to WebAssembly:

  • MozJPEG — a JPG encoder tuned for perceptual quality, for JPG and HEIC input
  • libwebp — WebP encoding
  • OxiPNG — lossless PNG optimization
  • libavif and libjxl — AVIF and JPEG XL

Squoosh is the reference point here, and we aren't affiliated with Google or the Squoosh project — we run the same codecs and add what a batch workflow needs.

Why one quality, not a slider

Most compressors expose a quality slider and let you guess. PixSip uses one conservative quality per format instead, then gives every result a 1:1 comparison so you can inspect detail before downloading.

That also means "compressed" never means "blurry mess": JPG and HEIC go through MozJPEG, and photo PNGs are re-encoded to a color palette at 46 dB PSNR on our reference photo.

The pipeline

  1. Decode — JPG, PNG, WebP, AVIF and HEIC are decoded locally; HEIC decoding is our own addition, since Squoosh has none and iPhone photos otherwise fail in Chrome, Firefox and Edge.
  2. Encode — each file goes through its format's encoder inside a Web Worker, with plan-aware concurrency that keeps the page responsive.
  3. Compare — every output gets a Compare view: drag the divider to wipe between original and result, or switch to 1:1 to inspect compression artifacts at full resolution.
  4. Export — download files one by one, or grab the whole batch as a single ZIP, generated locally.

What we skip on purpose

No uploads and no server round trips. That constraint is what makes the architecture simple: there is no upload queue, no image storage to secure, and no server-side encoding bill. The free plan still has published browser-workflow limits: 20 images per batch and 5 MB each, with no daily image quota.

The trade-off is honest: heavy batches use your CPU instead of a server's. Processing time depends on the image dimensions, formats, device, and batch size, while your files never leave the room.

img

If you care about the details, open PixSip in your browser's network tab and watch what doesn't get sent. That absence is the whole design.


Keep reading: Why browser-side covers the privacy rationale, the image format guide turns the numbers into format decisions, and the Squoosh alternative comparison shows where a batch-first workflow differs. Try the tools: compress JPG, convert HEIC to JPG, convert to WebP.