How to Convert HEIC to JPG: Open iPhone Photos Anywhere, in Bulk

It is one of modern computing's most reliable small frustrations: your iPhone takes a beautiful photo, you move it to a Windows PC, a school portal or an older app — and the file will not open. The photo is not broken. It is HEIC, the efficient format iPhones use by default, and a large part of the non-Apple world still cannot read it. The fix takes about a minute and should not involve uploading family photos to a random server: our HEIC converter decodes and converts entirely in your browser, in batches of up to 20, to JPG or PNG. This guide covers the three steps, the JPG-versus-PNG decision with real file sizes, how the in-browser conversion works, and the mistakes that quietly cost people quality or storage.

How to Convert HEIC to JPG, Step by Step

1. Drop your HEIC photos in. Drag .heic or .heif files from your iPhone or Mac onto the tool — up to 20 at a time, each up to 100 MB. They stay on your device from the start; nothing is uploaded to any server at this step or any later one. 2. Pick JPG or PNG and set quality. Choose JPG for small, shareable files and set the quality slider — 85% is the default and the sweet spot the worked example below uses — or choose PNG for lossless output when further editing is planned. Conversion starts automatically and runs one photo at a time on your device. 3. Preview and download. Check each converted photo in the preview, download the ones you want individually, or use Download all to collect the whole batch at once. Converted files keep the original filename with the new extension, so a sorted photo folder stays sorted. The very first conversion of your first visit runs a little slower, for a reason the next sections explain — every conversion after it starts instantly.

JPG or PNG? The Decision in Real Numbers

The tool page works this example in full: 20 iPhone photos totalling 34 MB as HEIC. Converted to JPG at 85% quality, the batch becomes 61 MB — about 3 MB each — visually identical to the originals and openable everywhere, including Windows and older Android phones. The same 20 photos converted to PNG become 148 MB. Nothing about the PNGs looks better on screen; they are bigger because PNG is lossless, storing every pixel exactly rather than compressing cleverly. That exactness is worth paying for in precisely one situation: when the photo will be edited and re-saved repeatedly, because each JPG re-save throws away a little more quality while a PNG master never degrades. For everything else — sharing, uploading to forms and listings, emailing, printing at ordinary sizes — JPG at 85% is the right answer, and the 87 MB difference on a 20-photo batch is storage you keep. A useful way to hold the formats in your head: HEIC is the master, JPG is the copy you hand out, PNG is the workbench file. The same logic governs our PDF to PNG converter, which turns PDF pages into images for exactly the places that accept pictures but not documents.

How In-Browser HEIC Conversion Works

iPhones save photos as HEIC because it stores roughly the same quality as JPG at about half the file size — your phone's storage thanks Apple for that choice even when your PC curses it. Browsers cannot decode HEIC natively, so the tool loads heic2any, an open-source WebAssembly decoder, once from a CDN. Each photo is then decoded to a bitmap in your device's memory and re-encoded as JPG at your chosen quality or as PNG. Two practical consequences follow. First, privacy: your photos never leave the device, and the only network request in the whole process is that one-time decoder download of about 1–2 MB. Second, speed: because the decoder is cached after the first load, later conversions — including the rest of a 20-photo batch — start instantly, and a full batch of 20 takes roughly 90 seconds on a typical laptop. The pattern will be familiar if you have used our background remover, which accepts HEIC photos directly for the same reason: Apple formats should be a one-step conversion, not a dead end. If the backdrop itself has to go next, its companion walkthrough — how to remove a background from an image — uses the same in-browser approach.

Common Mistakes

Deleting the HEIC originals after converting. The JPG is a compatibility copy, not an upgrade. HEIC holds the same picture in about half the space, so the originals are the better archive — keep them, share the JPGs. Re-saving the same JPG repeatedly. Every JPG save re-compresses. Edit from the HEIC or a PNG copy, export a fresh JPG at the end, and quality loss stays at one invisible step instead of compounding. Converting everything to PNG 'for quality'. On the worked batch that choice costs 148 MB against 61 MB for no visible difference. PNG is for editing pipelines, not for sharing. Converting one photo at a time. The tool is built for batches of 20 with a single Download all at the end; one-by-one converting is the slow path the batch exists to replace. Assuming a failed file means a broken tool. Most failures mean the file is not actually a valid HEIC photo — a renamed JPG, or a corrupted download. Open it on the device that created it first; if it opens there, convert again, and convert very large panoramas (over roughly 100 megapixels) one at a time to stay inside browser memory limits. Forgetting Live Photos are two files in one. The still converts normally, but the short video portion is dropped — export the video from the Photos app separately if it matters.

Converted stills are ingredients. One dish they end up in: the Cinemagraph Maker, which freezes most of a frame and lets one region keep moving — a living photo built from the same camera roll you just converted.

Frequently Asked Questions

More guides from ToolNest