The easiest way to check if a "private" web tool is actually private: turn off your wifi

There's a whole category of browser tools (PDF converters, image editors, redaction tools) that advertise "files never leave your device" or "100% local, in-browser." Some genuinely do the work in your browser with WebAssembly. Plenty just say they do.

You don't need DevTools or any technical skill to check. Load the page, disconnect your internet, and try to actually use it.

  • Still works fully offline: the processing is happening on your machine. Your file physically cannot have left; there's no connection for it to leave through.
  • Breaks the moment you go offline: it needs a server to do the job. That doesn't automatically mean it's uploading your file (could just be loading code); but you can't rule it out anymore, and you're back to trusting their word.

I ran this on a handful of popular "local" PDF tools recently. Most stopped working the second I disconnected. A couple passed. Not naming names (I don't want to start a brigade or send anyone traffic): the point is the test, not a list. Run it yourself on whatever you use.

This is the one privacy claim you can verify with zero tools and zero trust. Pull the plug. Either it works or it doesn't.

reddit.com
u/EmoticonGuess — 3 days ago
▲ 184 r/privacy

The easiest way to check if a "private" web tool is actually private: turn off your wifi

There's a whole category of browser tools (PDF converters, image editors, redaction tools) that advertise "files never leave your device" or "100% local, in-browser." Some genuinely do the work in your browser with WebAssembly. Plenty just say they do.

You don't need DevTools or any technical skill to check. Load the page, disconnect your internet, and try to actually use it.

  • Still works fully offline: the processing is happening on your machine. Your file physically cannot have left; there's no connection for it to leave through.
  • Breaks the moment you go offline: it needs a server to do the job. That doesn't automatically mean it's uploading your file (could just be loading code); but you can't rule it out anymore, and you're back to trusting their word.

I ran this on a handful of popular "local" PDF tools recently. Most stopped working the second I disconnected. A couple passed. Not naming names (I don't want to start a brigade or send anyone traffic): the point is the test, not a list. Run it yourself on whatever you use.

This is the one privacy claim you can verify with zero tools and zero trust. Pull the plug. Either it works or it doesn't.

reddit.com
u/EmoticonGuess — 8 days ago

Pregnant woman speaks out after Dutch police assault

I can't believe nobody has taken any action yet on these officers

u/EmoticonGuess — 10 days ago
▲ 4 r/pdf

Hey r/PDF 👋

I've been quietly building ConvertPrivately (github ConvertPrivately) for the last year; a set of ~250 file tools that all run client-side in the browser. No uploads, no sign-ups, no "free tier with watermark." I wanted to share the PDF side of it here because this sub is the right audience to tear it apart.

The thing that surprised me most while building it: how much stuff a typical PDF carries that the author (and myself) has no idea about. Author name, software fingerprint, edit history, embedded thumbnails of redacted images, hidden form field values, JavaScript actions, even GPS coords from scanned phone photos. So a few of the tools are aimed specifically at that:

  • PDF X-Ray — drop a PDF in and it shows you every piece of metadata, embedded font, JS action, and hidden object. Eye-opening on PDFs exported from Word or Acrobat.
  • PDF Visual Metadata Stripper — removes the visible-but-forgotten stuff (headers/footers with usernames, "Draft" stamps, comments).
  • PDF PII Redactor — actual redaction that rewrites the page content stream, not the "black rectangle on top" trick that people copy-paste right through.
  • PDF Repair

+ PDF Validator — for the broken files clients send you at 5pm on a Friday.

Plus the usual suspects, done locally:

Everything is free. No login. The site is a static React app on Cloudflare Pages — you can literally pull your wifi cable after the page loads and the tools still work. You can also install it on your computer...

There are also write-up of (such as) Private PDF Cleanup Workflow (X-Ray → Redact → Compress → share) for anyone who handles sensitive docs regularly.

What I'd love feedback on:

  1. Which PDF features are missing that you reach for daily?
  2. Is "client-side only" actually a selling point for you, or do you not care?
  3. Has anyone here been burned by a "redacted" PDF that wasn't actually redacted? Curious how common that war story is.

Happy to go deep on the technical side too: pdf.js quirks, Tesseract WASM, why "compress PDF" in a browser is harder than it sounds.

u/EmoticonGuess — 1 month ago