Photos are personal.
So we never ask for them.
LocalPhotoTool exists because image tools online have settled into a bad habit: to do something as ordinary as shrink a photo, you are expected to hand the original over to a stranger's server.
The idea
Everything here runs in your browser. The site is static — there is no backend that accepts image data, no upload endpoint, no processing queue. When you compress a photo, your own CPU does the work, and the result is handed straight back to you through a local download.
That constraint is not a limitation we worked around. It is the product.
It changes the privacy story
Most privacy policies for image tools say something like "files are deleted after one hour". Ours can say something stronger: the files were never uploaded, so there is nothing to delete. We cannot lose them, leak them, subpoena them or train on them, because we never had them.
It changes the speed story
A 25 MB photo does not need to travel across the ocean and back before anything happens. Local processing starts the instant you drop a file. On a slow connection this is the difference between seconds and minutes, and it keeps working when your connection does not.
It changes the quality story
Servers bill for compute, so free online compressors tend to run one cheap, fixed preset over everything. Your device is already more powerful than the server most of these tools rent by the hour. That headroom is what pays for the analysis this engine does — measuring each image and choosing settings that fit it.
How the compressor earns its keep
The core trick is refusing to guess. A test pass is encoded at several quality levels, decoded again and scored against the original. The engine keeps the smallest result that still clears a perceptual fidelity floor, rather than applying the same number to a smooth gradient and a hedge full of leaves. Where the format allows it, WebP and AVIF do the heavy lifting; where PNG is the right answer, a median-cut quantizer with dithering does the work that a naive re-encode never could.
You can read the full breakdown on the compressor page, including which strategy suits which job.
What is next
Compression ships first because it is the tool people reach for most often. The same engine is being extended into resizing, format conversion, cropping and metadata editing — all under the same rule: your device, your files, your call.
One honest caveat: the optional WASM codec modules are fetched from a public CDN on first use. That request contains no image data whatsoever. If the CDN is unreachable, the built-in browser encoders take over and every feature still works.
Talk to us
Found a bug, or want a tool that does not exist yet? We build what people actually ask for. Reach us at [email protected].