Convert HEIC to JPG without uploading

If you searched for this, you already sense the problem with “free online converters”: your photos — faces, kids, homes, documents, often with GPS coordinates embedded — travel to an anonymous server, subject to a privacy policy nobody reads, retained for however long “deleted after processing” really means. For photos, that trade should be unacceptable by default.

This converter is built so the trade never happens: the site is static, there is no upload endpoint to send photos to, and the HEIC decoding runs inside your browser via WebAssembly. “No upload” here isn’t a promise about server behavior — it’s an architectural fact about a page that has no server to receive anything.

Preset: private local HEIC → JPG

Drop HEIC photos here — or click to browse, or paste with Ctrl+V

HEIC · HEIF · AVIF · WebP · JPG · PNG — converted on your device, never uploaded

How it works

  1. Open this page — the converter is already set for “Convert HEIC to JPG without uploading”.
  2. Drop your photos into the box, click to browse, or paste with Ctrl+V. Batches are fine.
  3. Your browser decodes and re-encodes each photo on your own device — nothing is uploaded.
  4. Check the preview and file size on each result card, then download.

Verify it — don’t trust it

Two checks, two minutes, no expertise needed. Check one: press F12 to open your browser’s DevTools, switch to the Network tab, then convert a photo. You’ll see the page’s own files load — and no POST or upload request carrying your photo, because none exists. Check two: load this page, disconnect Wi-Fi entirely, and convert. It works, which no upload-based converter can do.

Run the same two checks on any converter that claims to be private. The ones that upload fail check two instantly — and that includes several that advertise “local” conversion in their marketing.

The metadata bonus most people don’t know they need

iPhone photos carry EXIF metadata: precise GPS position, capture time, device model. Because this tool redraws the image and re-encodes it fresh, the output JPG carries none of that — sharing the converted file doesn’t reveal where it was taken. (The original HEIC on your device keeps its metadata; only the converted copy is clean.) For photos headed to marketplaces, forums or strangers, that’s a second privacy win stacked on the no-upload one.

Good to know

Frequently asked questions

How can a website convert HEIC without a server?

The decoder (libheif, the same open-source library many desktop tools use) is compiled to WebAssembly and runs inside the page. Your browser does the decode and re-encode locally; the site only ever serves the page’s own files to you, nothing travels back.

Is local conversion slower than uploading?

Usually faster in practice: decoding takes about a second per photo, while upload converters move your photos over the network twice (up, then down) and often through a queue. On a slow connection, local wins by minutes.

What does the site learn about my photos?

Nothing — not the images, not names, not sizes, not thumbnails. The only measurement on this site is cookieless, aggregate page-view counting (how many people visited this page), which contains nothing about files. Details in the privacy policy.