Building a Browser-Only Image Compressor: What We Actually Measured
Most "online image compressor" pages upload your file, compress it on a server, and hand back a download link. That works, but it costs you two things: your file leaves your machine, and the result depends on someone else's queue depth.
We wanted the opposite: the pixels never leave the browser. Here is what that looks like in practice, and what the measurements actually say.
Why "local" is an architecture decision, not a promise
A privacy claim is only as good as its architecture. If a page uploads your image, "we delete it in 24 hours" is policy. If a page never uploads, there is nothing to delete.
The verification is trivial: open the page, disconnect the network, drop an image in, and see whether a result comes out.β¦