HEIC to JPG Converter — Bulk, Offline, No Upload

Why iPhone photos won't open on Windows or Android

Since iOS 11, iPhones save photos as HEIC (High Efficiency Image Container) instead of JPG. HEIC files are roughly half the size of equivalent-quality JPEGs, but Windows, most Android phones, Slack, Reddit, eBay, Craigslist, and many email clients still don't open them natively. The fix is conversion to JPG, PNG, or WebP — formats every device on earth understands. SimpleTool's converter does this entirely in your browser using a WebAssembly build of libheif (the same C library Apple, Adobe, and Mozilla use). Your photos never touch a server.

Why “just upload to a converter site” is the wrong answer

Most online HEIC converters upload your files to their server, convert them there, and send the JPGs back. That means a third party now has copies of your family photos, passport scans, or whatever else you converted — plus all the EXIF metadata baked into them: GPS coordinates, camera serial number, exact timestamp. Many of those services explicitly reserve the right to scan or retain uploads in their terms of service. SimpleTool's converter runs the libheif decoder directly in your browser tab. Once you close the tab, the photos are gone from RAM. Nothing is logged, retained, or sent anywhere.

EXIF & GPS scrub — what actually gets stripped

When the “Strip EXIF metadata” toggle is on (default), the output JPG/PNG/WebP contains no metadata at all. The decode happens through libheif, the pixels are drawn to a fresh canvas, and the canvas is re-encoded — so every embedded tag is dropped:

• GPS coordinates — where the photo was taken
• Date / Time / Time Zone — exact capture timestamp
• Camera make, model, serial number — device fingerprint
• Lens model, focal length, aperture, ISO, shutter speed
• Software fingerprint — iOS version, edit history
• Apple-specific tags — Live Photo identifiers, depth-map references

Turn the toggle off if you need the converted file to retain metadata — e.g., for an archival workflow or because a downstream tool relies on the timestamp. Image orientation is always preserved correctly either way (we read and apply the orientation tag during decode, then bake the result into the pixels).

JPG vs. PNG vs. WebP — which output should I pick?

Known limitations