ImageCompressCloud

How Your Files Stay Private

Every privacy page on the internet says some version of 'we care about your privacy.' Here's how to check ours is actually true, without taking our word for it.

The claim, precisely

Image compression, PDF compression, merging, splitting, rotating, removing pages, and converting between PDF and image formats all run entirely inside your browser tab. The file is read into memory as soon as you select it and never leaves your device during any of that work.

There is one exception, and we'd rather say so plainly than let the claim above overreach: converting to or from Word, Excel, or PowerPoint uses a server. Faithfully rebuilding real Office document layout — fonts, tables, page breaks — needs the same kind of rendering engine Microsoft Office itself uses, which isn't something a browser can do alone. For those specific conversions, and only those, your file is sent to a conversion service, processed, and discarded.

Verify it yourself in under a minute

  1. Open your browser's developer tools — press F12, or right-click anywhere on the page and choose Inspect.
  2. Click the Network tab. Clear it if there's anything already listed.
  3. Go to the PDF compressor (or the image compressor) and compress a file as normal.
  4. Watch the Network tab while it processes. You'll see the page's own scripts and stylesheets load, but no request carrying your file's contents to any server — nothing whose size tracks the size of the file you uploaded.
  5. Now try the same thing on Word to PDF and you'll see the opposite: a request does go out, matching the exception above.

That gap is the whole point — a tool that's honest about the one thing it does send to a server is more trustworthy than one that quietly does it for everything while claiming otherwise.

Why this even works

Browsers ship real, capable APIs for this: the Canvas API can re-encode an image at a different quality level, and JavaScript PDF libraries can parse and rebuild a PDF's internal structure without any of it leaving memory. Most competing tools don't do this — not because it's impossible, but because a server endpoint is simpler to build than doing the work correctly in every browser. The technical tradeoffs are explained in more depth in browser-based vs. server-based file tools.

More

See the privacy policy for what little data is collected, or read more about why this site is built this way in the first place.