SnappyKit

Keeping everything client-side and enforcing it with an automated test suite is a strong trust signal for a tool that handles personal photos. One question on the EXIF remover: does it also strip location and camera data embedded in HEIC and WebP files, or only JPEG? Phone photos carry GPS in several container formats, so that is the case I would test first.

The client-side-only approach is the real differentiator — stripping EXIF before sharing photos is something most tools claim, but backing it with an automated test suite is a strong trust signal. HEIC conversion with no uploads is genuinely useful for iPhone users. A before/after file size comparison per tool would make the savings even more tangible.

The HEIC conversion alone is worth bookmarking — iPhone photos are a constant headache when you need JPG/PNG for portals that don't accept HEIC. Doing it 100% client-side with an automated test suite enforcing it is the right call; too many 'free' image tools quietly upload your files. Batch processing with ZIP download is a thoughtful touch for anyone handling dozens of images at once.

Love that everything runs client-side, and that you enforce it with an automated test suite: that's a detail most "no upload" tools skip. Quick question: for batch HEIC to JPG, is there a practical limit on how many files or total MB the browser can handle before memory becomes an issue? And do you keep the original capture date when you strip the other EXIF data?

The 100% client-side architecture is the whole point, and I like that you don't just claim it — enforcing it with an automated test suite turns a marketing promise into something verifiable. That's exactly the standard privacy-sensitive tools (HEIC conversion, EXIF stripping, watermarking) should be held to. Batch processing with ZIP download is a smart inclusion too; without it, single-file tools feel like demos. One suggestion: an in-browser before/after comparison slider for compression would make the quality trade-off tangible at a glance, which is the #1 hesitation people have with compressors.

Love the positioning — "no uploads, no account" removes the two biggest frictions for quick image tasks. The client-side-only architecture enforced by an automated test suite is a great trust signal. One suggestion: a single "drop any image here" entry point that auto-suggests the best tool could make the 40+ tools feel less overwhelming for first-time visitors.

I will try this tool.

The automated test suite enforcing client-side-only behavior is the detail that won me over — anyone can claim "no uploads", but proving it with tests makes the privacy promise verifiable rather than a marketing line. Batch processing with ZIP download is also the right call for real workflows. One idea: a side-by-side quality preview for AVIF vs WebP at matched file sizes would help users pick the better format without guessing.

As someone who also ships free browser-based tools, the automated test suite enforcing client-side-only behavior is the detail I respect most — privacy claims are easy to make and hard to verify. Small UX idea: since batch processing is a headline feature, showing a progress indicator with per-file savings (e.g. compressed 68% per image) would make large batches feel faster and more transparent.

The client-side guarantee matters for EXIF cleanup. Does the batch ZIP preserve original filenames and offer a per-file confirmation that metadata was removed? That would make it easier to verify the privacy step before sharing.