HEIC to JPG Converter

Turn iPhone photos into JPG files that open anywhere. 100 at a time, and nothing is uploaded.

Files never leave your device Batch up to 100 No signup, no watermark

Drop your HEIC or HEIF files here

or choose files — up to 100 at once, 100 MB each

No upload. Files are processed in your browser.

92%

Files never leave your device · EXIF and GPS removed

Works on Chrome, Safari, Firefox and Edge · No installation

HEIC is the format iPhones use by default since iOS 11. It saves roughly half the space of JPEG at the same visual quality — great on your phone, annoying everywhere else. Windows photo viewers, older Android phones, website upload forms and email clients often refuse to open it.

This converter decodes HEIC in your browser and re-encodes it as JPG. Your photos are never sent to a server, so there is no upload wait, no file-size limit from us, and no copy of your pictures sitting on someone else’s disk.

Why convert HEIC to JPG?

It opens everywhere

JPG is supported by every browser, phone, printer and upload form. HEIC support is still patchy outside Apple devices.

Upload forms accept it

Job portals, visa applications, school systems and marketplaces commonly reject .heic files with a generic “unsupported format” error.

Smaller risk, same look

At quality 90–95 the difference is invisible on screen, and you keep the original HEIC files untouched.

How to convert HEIC to JPG

  1. Drop your HEIC files. Drag a folder or select up to 100 photos. Nothing is uploaded — the browser reads them locally.
  2. Pick quality and size. Quality 92 is a good default. Lower it to 80 for forms with a 2 MB limit, or resize the long edge to 2048 px.
  3. Download JPGs. Save files one by one or grab everything as a single ZIP. Metadata, including GPS location, is removed.

What settings actually change

SettingTypical resultWhen to use
Quality 95~30% larger than 92Archiving, printing
Quality 92Baseline — about the source sizeDefault for sharing
Quality 85~17% smallerSharing, most upload forms
Quality 80~25% smallerUpload limits, email
Max width 2048 px~56% smaller than full sizeWeb, chat, marketplaces

Measured: what these settings actually produce

We ran this exact converter on six 12 MP photos (4032 × 3024, 7.1 MB of HEIC in total) in Chrome 156 on an Apple M6 Mac. No upload, same code you are using.

Output qualityAll six photosPer photoBatch time
959.2 MB1.5 MB1.6 s
92 (default)7.1 MB1.2 MB1.6 s
855.9 MB1.0 MB1.4 s
805.3 MB0.9 MB1.4 s
  • Roughly 0.25 s per 12 MP photo, decode and encode included. Resizing the same batch to 2048 px took the same 1.5 s and produced 3.1 MB.
  • Output size follows image detail: foliage, crowds and text can produce files three to four times larger than a smooth sky at the same setting.
  • In this test the JPGs came out close to the HEIC size because the source files were already encoded at high quality. Photos straight from a camera usually produce larger JPGs than the HEIC they came from — the reason to convert is compatibility, not size.

Which quality should I pick?

  • 92 — Default. Visually identical to the original on screen, reasonable size.
  • 85 — Noticeably smaller, still fine for sharing and most upload forms.
  • 80 — Use when a form caps you at 2 MB or similar.
  • 95+ — Only worth it if the file will be edited again.

Questions

Are my photos uploaded to a server?

No. The conversion runs entirely in your browser using WebAssembly. You can disconnect from the internet after the page loads and it will still work.

How many files can I convert at once?

Up to 100 per batch on desktop, fewer on phones with limited memory. Each file can be up to 100 MB.

Does converting reduce quality?

JPG is lossy, so some data is discarded. At quality 92 and above the difference is not visible on screen; keep your original HEIC files if you need a perfect archive.

Is HEIC the same as HEIF?

HEIF is the container, HEIC is the HEVC-coded variant Apple uses. This tool accepts both .heic and .heif files.

What happens to the date and location data?

It is removed. Canvas-based re-encoding drops EXIF metadata, which also strips GPS coordinates — useful when you share photos publicly.