Skip to content
← Articles

How to Convert HEIC to JPG Without Uploading Your Photos

Convert HEIC photos to JPG without sending the file to a remote conversion server. Learn how browser-local conversion works and how to verify privacy claims.

ReFormatic ·

Quick answer

To convert HEIC to JPG without uploading the photo to a remote conversion server, use a converter that decodes and re-encodes the file locally in your browser. The page itself still has to load website code, but the photo bytes do not need to be sent to the server. Always verify the converter’s privacy claim rather than assuming every “online” converter works locally.

“Online tool” does not always mean “your file is uploaded”

Two converters can look almost identical in a browser while using very different architectures.

Server-side converter

  1. You select a file.
  2. The browser uploads it to a server.
  3. The server converts it.
  4. You download the result.

Browser-local converter

  1. You load the web application.
  2. You select a file.
  3. JavaScript, WebAssembly or browser media APIs process it on your device.
  4. The output is generated locally.

Both are “online tools” because you opened a website. Only the second design avoids sending the file contents to a conversion server.

Why does that matter for photos?

A personal photo can contain more than the visible pixels.

Depending on the camera and app, it may contain:

  • capture time;
  • camera model;
  • orientation;
  • editing information;
  • GPS coordinates;
  • other EXIF metadata.

That does not mean every image contains sensitive metadata, but it is a reason to understand where a private photo is being processed.

How to convert HEIC to JPG locally with ReFormatic

Open the HEIC to JPG page and add your photo.

The important detail is that the converter should run directly on the page. You should not need to upload the photo and wait for a remote job ID.

Then:

  1. Select JPG as output.
  2. Choose the quality setting.
  3. Decide how metadata should be handled.
  4. Convert.
  5. Open the downloaded JPG to verify the result.
  6. Keep the original HEIC if it matters.

The page may still make ordinary web requests for application code, fonts, analytics or site functions. The privacy question is specifically whether the file contents are transmitted.

How can you verify a “no upload” claim?

A practical way is to inspect your browser’s developer tools.

In Chromium-based browsers:

  1. Open Developer Tools.
  2. Open the Network panel.
  3. Clear the existing requests.
  4. Add a distinctive test image.
  5. Run a conversion.
  6. Inspect requests that occur during the conversion.

You are looking for a request whose payload contains the selected file or a large binary upload associated with it.

This is not a perfect security audit, but it is more meaningful than trusting a marketing badge.

What if the site uses analytics?

Analytics does not automatically mean the image itself is uploaded.

A page can record an anonymous page view or a tool event while keeping file contents local.

A precise privacy policy should distinguish:

  • website usage data;
  • account data, if any;
  • file contents;
  • temporary browser data;
  • remote storage.

Avoid vague claims such as “nothing ever leaves your device” when the page obviously has to communicate with a web server to load.

A more accurate statement is:

the selected file’s contents are processed locally and are not uploaded for conversion.

Does local conversion guarantee total privacy?

No single architectural choice guarantees total privacy.

A browser-local converter reduces one important risk: sending the original file to a conversion service.

You should still consider:

  • whether the website code itself is trustworthy;
  • whether extensions in your browser can access pages;
  • whether the device is shared;
  • whether the converted output retains metadata;
  • whether you later upload the output somewhere else.

For highly sensitive material, an offline desktop workflow on a trusted device may still be appropriate.

Does converting HEIC to JPG remove GPS?

Not necessarily.

File conversion and metadata removal are separate decisions.

A tool can:

  • preserve EXIF;
  • strip EXIF;
  • preserve selected fields;
  • rewrite metadata.

If location privacy matters, explicitly choose a metadata-removal option and verify the resulting file.

Will the JPG be lower quality?

JPEG is normally lossy. Re-encoding therefore can discard information.

Use a sensible quality setting and avoid repeatedly converting the same image through multiple lossy generations.

For example, avoid:

HEIC → JPG → JPG → JPG

when you still have the original HEIC.

Instead, keep the original and export new copies from it.

Why convert to JPG at all?

Compatibility.

Apple devices have supported HEIF/HEIC for years, but a particular upload form, editing tool, older operating system or business workflow may still expect JPG.

JPG remains one of the safest interchange formats for ordinary photographic images.

Bottom line

You do not have to upload a private HEIC photo to a remote conversion server just to make a JPG copy.

Use a genuinely browser-local converter, inspect the privacy behavior when it matters, choose metadata settings deliberately, and keep the original file.

Related ReFormatic pages

Try it with ReFormatic

Open the related tool

How to Convert HEIC to JPG Without Uploading Your Photos · ReFormatic