How to convert HEIC to JPG without installing anything
August 20, 2026 · 5 min read
If you've ever AirDropped a photo to yourself, emailed it to a colleague, or uploaded it to a site that replied with something like "unsupported file type," you've run into HEIC. It's the format the iPhone camera has saved to by default since iOS 11, and outside of Apple's own apps, support for it is still patchy nearly a decade later.
What HEIC actually is
HEIC (High Efficiency Image Container) isn't a new invention — it's Apple's packaging around HEVC, the same video codec behind H.265. Applying a video codec's compression to a single still frame turns out to work well: HEIC files are routinely 40–50% smaller than an equivalent-quality JPG, which is why Apple switched. Storage on a 128GB phone goes noticeably further when every photo is half the size.
The trade-off is compatibility. JPG has been a fixed, universally implemented standard since 1992. HEVC decoding, by contrast, is patent-encumbered and several major platforms — most of Windows outside a paid Microsoft Store extension, most Android phones, most web upload forms — never built in support for reading it. The format is genuinely better; it's just not something everything else agrees to open.
Where it actually breaks
In practice, three situations account for nearly all HEIC frustration:
- Uploading to a website. Government portals, e-commerce forms and older
content management systems frequently reject
.heicoutright or, worse, accept it and render a broken image icon. - Opening on Windows. File Explorer's thumbnail and preview both fail without the (non-free) HEIF codec extension installed from the Microsoft Store.
- Sending to an Android phone. Messaging apps on Android generally can't decode HEIC, so a photo that looks fine on the sender's iPhone arrives as a grey square or a "cannot preview this file" message.
Fix it at the source: change what the camera saves
If most of your HEIC problems come from sharing photos you're about to take, the cleanest fix doesn't involve converting anything after the fact — change the format the camera writes in the first place:
Settings → Camera → Formats → Most Compatible.
This switches new photos to JPG (and new videos to H.264) at capture time. The trade-off is the storage saving disappears — JPGs run larger — and nothing about photos already on the phone changes, since this setting isn't retroactive.
Convert photos you already have
For an existing library, there are three practical routes, in rough order of convenience.
In the browser. ihateimg's HEIC to JPG tool decodes each file locally using WebAssembly and re-encodes it to JPG — nothing is uploaded to a server, so there's no size limit and no wait for a queue. Drop in a folder's worth of exports at once and download them individually or as a ZIP.
On a Mac. Preview can do this without any extra software: open the HEIC file, choose File → Export, and pick JPEG as the format. It handles one file at a time, which is fine for the odd photo but slow for a whole album — batch conversion on a Mac generally means Automator or a Finder Quick Action instead.
On Windows. Install the free "HEIF Image Extensions" and the "HEVC Video Extensions" from the Microsoft Store first — File Explorer and the Photos app can't even generate a thumbnail without them. Once installed, the Photos app can open a HEIC file and use "Save As" to write a JPG copy, again one file at a time.
The pattern across all three device-native options is the same: they work, but they're built for occasional single-file conversion, not for clearing out a camera roll's worth of exports in one pass. That's really the gap a batch browser tool fills.
What happens to your metadata
A reasonable worry when converting is whether the photo loses information in the process. It doesn't, by default: EXIF metadata — capture date, camera model, and GPS coordinates if location services were on — is read from the HEIC container and written back into the new JPG's EXIF block. The pixels are decoded and re-encoded, but nothing about when or where the photo was taken gets stripped unless you deliberately run it through a metadata-removal step afterwards.
If you do want that data gone before sharing — GPS coordinates in a public photo are a genuine privacy leak — that's a separate, deliberate step, not something conversion does for you automatically.
Is the converted JPG smaller or larger?
Almost always larger, which surprises people used to HEIC's storage savings. JPG is the less efficient codec, so representing the same image detail costs more bytes. If the destination has its own size limit — an upload form capped at 2MB, for instance — run the converted JPG through an image compressor afterwards rather than assuming the conversion alone will fit.
Quick answers
Will converting HEIC to JPG lose quality? A small amount, since JPG is also a lossy format — decoding HEIC and re-encoding as JPG at a high quality setting (85–95) keeps the loss invisible to the eye. Repeating the round trip on an already-converted file is where visible degradation accumulates.
Can I convert a whole camera roll at once? Yes — that's the main reason a batch tool is worth using over the device-native single-file options above.
Does converting remove the photo's location data? No, EXIF including GPS carries over by default. Strip it separately if that's what you actually want.
Do I need to install anything? No — a browser-based converter decodes and re-encodes locally, so there's nothing to download and no account to create.