Welcome to Squeeze
August 2, 2026
Why exact target-size compression beats vague “make it smaller” tools — and how Squeeze approaches privacy and bulk workflows.
Squeeze started from a simple frustration: most compressors shrink an image *somewhat*, but forms, email limits, and upload caps ask for a specific file size.
Exact KB, not vibes
When a portal says “max 200 KB,” “optimize” is not enough. Squeeze binary-searches JPEG quality first, then scales resolution only if quality alone cannot hit the target. The goal is the number you typed — with as much visual fidelity as that number allows.
Prep in the browser, compress with intent
On the Single tab you can crop, rotate, and resize locally before compression. That prep step stays in your browser. Compression itself uses the Squeeze backend so we can hit precise sizes reliably — including bulk ZIP jobs and URL fetch.
What’s next
This blog is a lightweight place for tips, release notes, and deeper notes on the algorithm. Drop a new markdown file in content/blog/ to publish another post.