Compress an image without uploading it
Not a promise — something you can check yourself, in under a minute.
0 bytes of image data sent — processed on this device
Verify this yourself
- Open DevTools → Network, then convert a file.
- No request carries your image — the only requests are the page's own files.
- Or disconnect from the internet entirely and convert: it still works.
- Step 1Drop your imagesAnywhere on the page
- Step 2Set quality 80%Already selected for you
- Step 3Download the resultOne file or a zip
Most sites that handle your photos tell you they're safe: a line in a privacy policy promising your files aren't stored or shared. That's a statement about what happens on a server you cannot see, and there is no way to check a promise — you either trust it or you don't. This page exists to offer something better than trust: two checks you can run yourself, right now, that don't depend on believing anyone.
The first is the Network tab. Open your browser's developer tools, switch to the Network panel, and drop an image into the tool below. Watch the requests that go out — none of them carry your image. That isn't a policy choice; it's a consequence of how the site is built. This is a set of static files with no upload endpoint anywhere in it, so there is no address on this domain that image bytes could even be sent to.
The second check is stronger: disconnect from the internet entirely, after the page has loaded, and convert a file anyway. It still works, because the code that reads, resizes and re-encodes your image is a browser feature — the same decoder and encoder every page uses to display pictures — and it arrived with the page rather than needing to be fetched again per file. No connection means no possibility of a request, which is a different kind of evidence than simply not seeing one go by.
Quality preserved
Structural, not promised
The distinction that matters is between a policy and a fact about the code. A company can promise not to look at your files and still be wrong, hacked, or acquired by someone who changes the policy. A static site with no server-side code has no mechanism to receive a file at all, whether or not anyone intends to misuse it. That is what "verifiable" means here: check the structure, not the promise.
What this claim doesn't cover
To be precise about scope: loading this page is itself a normal web request, and a small, cookieless analytics beacon reports that the page was viewed. Neither of those carries any image data. The claim is specifically about your photograph, not about the browser making zero network activity ever — an important difference, and one worth stating exactly rather than rounding up.
Not sure it held up? Every result has a Compare button — drag the divider to see your original against the processed version at full size.
Common questions
How do I actually check this myself?
Open your browser's developer tools (F12 on most desktop browsers), go to the Network tab, and convert a file. No request will contain image data. For a stronger check, turn off your internet connection after the page loads and convert anyway — it keeps working.
Doesn't loading the page itself use the internet?
Yes, and it's worth being exact about that rather than overclaiming. Fetching the page and a small analytics beacon are ordinary requests. Neither carries your image — that's the specific claim being made, not that the browser makes no requests at all.
Why shouldn't I just trust a site that says it doesn't store photos?
You can trust it or not, but you cannot check it, because that claim describes behaviour on a server you have no visibility into. Here there is no server-side code capable of receiving a file in the first place, which is something you can confirm from outside rather than take on faith.
Does this matter for identity documents and exam photos?
It's often where it matters most. Passport photos, signature scans and identity proofs are exactly the images people are most uneasy sending to an unknown server, and they're processed here the same way any other file is — never transmitted.