Convert HEIC to JPG — right in your browser.

An iPhone photo in HEIC that simply will not open — on a Windows PC, an Android phone, an older Mac, or in a web form — is one of the most common frustrations people hit the moment they move a photo off their phone. The file is fine. The world around it cannot read it. This tool converts HEIC to JPG entirely inside your browser, so the result opens everywhere: in any browser, on any device, in any upload form, with anyone you share it with.

What makes it different is that nothing is uploaded. Decoding and re-encoding happen locally through WebAssembly. Your photo stays on your device, the conversion runs in a second or two, and you download a JPG that behaves the way JPGs always have — universally, predictably, anywhere.

Why convert HEIC to JPG

The reason to convert HEIC to JPG is simply that JPG works everywhere and HEIC does not. That is the whole of it.

HEIC has been the default photo format on iPhones since iOS 11 (released in 2017). Every photo your iPhone has taken in the last several years is most likely HEIC unless you changed the camera setting. On the phone itself, that is invisible — iOS displays HEIC natively and you never notice. The moment you send that photo somewhere non-Apple, the trouble starts. Windows PCs historically needed a HEIC codec from the Microsoft Store, and on Windows 10 often still do. Most Android phones cannot open HEIC at all without a third-party app. Many older macOS versions, photo editors, content management systems, and online services either fail silently or reject the file outright.

Converting to JPG sidesteps all of it. A JPG made from your HEIC opens on any operating system from the last thirty years, in any browser, in any app that reads images, on any form that accepts a photo upload. It is the closest thing digital photography has to a universal format.

The point is not that JPG is technically superior to HEIC — HEIC produces smaller files at the same visual quality, which is exactly why Apple adopted it. The point is that JPG is universally accepted where HEIC is not. For anything that leaves your phone, JPG is the safe choice.

Why HEIC won’t open everywhere

HEIC’s compatibility problem has a specific history, and understanding it helps you avoid the dead-ends.

HEIC was standardized as part of MPEG’s HEIF (High Efficiency Image File Format) family, built on the same HEVC (H.265) video codec that powers modern video compression. Apple adopted it as the default photo format in iOS 11 because the compression savings over JPEG are real — roughly half the file size for the same visual quality. For a phone producing thousands of photos a year, that is a meaningful saving in storage and iCloud bandwidth.

The reason the rest of the industry did not follow is a mix of patents and politics. HEVC licensing is notoriously tangled, with multiple patent pools claiming royalties on implementations. Browser makers and OS vendors outside Apple largely chose to avoid the format rather than pay. AVIF, a newer royalty-free alternative, is what much of the non-Apple world has settled on instead — but AVIF has its own support gaps, and HEIC remains Apple’s default.

Today’s reality looks like this. On iOS and modern macOS, HEIC works natively. On Windows, support arrived in Windows 10 but requires HEIF and HEVC extensions from the Microsoft Store, and many users never install them — so files appear broken. On Android, native support varies by version and manufacturer. In browsers, Safari reads HEIC; Chrome, Firefox, and Edge generally do not, and an <img> tag pointed at a raw HEIC file shows nothing.

That is why people hit the wall at the worst possible moment: when they email a photo to a Windows-using relative, attach it to a job application, upload it to a government form, or paste it into a document. The photo looks fine on their phone and broken everywhere else. Converting to JPG before you share removes the question entirely.

Why JPG is the universal choice

JPG (more formally JPEG, after the Joint Photographic Experts Group that defined it in 1992) is the most compatible image format in existence. Every browser, every operating system, every image-handling app, every form upload, every CMS, every chat client, and every email program reads it. There is no platform on Earth that handles images and does not handle JPG.

That is the reason forms and websites specify JPG. When an upload field says “JPG or PNG only” — or, more bluntly, rejects your HEIC without explanation — it is not being awkward on purpose. The system behind it needs to guarantee it can read whatever you upload, and JPG is the one format it can safely assume. Building HEIC support into every form backend would be expensive and fragile, so most simply do not bother.

For photographs specifically, JPG is also a better fit than PNG. PNG is lossless but inefficient — a full iPhone photo as a PNG can be tens of megabytes, several times the HEIC original, with no visible quality gain over a sensibly-encoded JPG. JPG was designed for photographs and produces small, good-looking files; that is why it has survived for thirty years as the default.

When you convert HEIC to JPG, then, you are not “downgrading” in any sense that matters. You are putting the photo into the format the rest of the world actually uses. Your original HEIC stays untouched — the tool reads it and produces a new JPG alongside it — and the JPG behaves the way you expect an image to.

How to convert HEIC to JPG, step by step

The tool is deliberately simple — no account, no settings menu, nothing to install.

1. Open the converter on this page. The engine loads once, the first time you visit, and then runs locally.
2. Drop your HEIC photo into the box, or click to select it from your device. The moment you choose a file, the tool decodes it and shows you a preview — useful, because most browsers cannot display HEIC natively, so without this step you would be guessing what you uploaded.
3. Leave the target KB field alone if all you want is a straight conversion. The tool produces a high-quality JPG at the resolution of your original. If you also need a size cap — many forms do — see the next section.
4. Click Convert. Decode and re-encode run locally, usually within a second or two for a phone photo.
5. Compare the before and after side by side, so you can see exactly what the converted JPG looks like.
6. Download the result. You get a standard .jpg file, ready to share, upload, or attach.

Your original HEIC is never modified or deleted — the tool reads it and produces a new JPG. Nothing is uploaded; nothing leaves your device. Close the tab and both files are gone from memory, with the downloaded JPG the only trace.

How the conversion works

It helps to understand what happens during conversion, especially since the privacy claim — nothing leaves your device — depends on it.

The conversion runs in two stages, both inside your browser, both executed by a small WebAssembly module.

1. Decode the HEIC

HEIC is a container holding image data compressed with HEVC. To turn it into something else, you first have to decode it into raw pixels. The browser cannot do this on its own outside Safari, which is why a plain <img> tag pointed at a raw HEIC shows nothing. This tool loads a WebAssembly module containing a pure-Rust HEIC decoder; the module runs inside your browser’s sandbox, reads your file locally, and produces a raw pixel buffer for the next stage. The pixels never leave the browser.

2. Re-encode as JPG

With raw pixels in hand, the tool runs a JPEG encoder and produces a standard .jpg file, byte for byte compatible with anything that reads JPG. Quality is set high by default, since the goal is faithful conversion rather than size reduction. The output is then handed back to you as a download.

That is the whole of it. Two passes, one decode and one encode, both running as WebAssembly inside your browser. No server round trip, no upload, no analytics on the image, no copy kept anywhere. WebAssembly is the piece that makes this possible — it lets real, fast image-processing code run in the browser at near-native speed, without the privacy cost of sending your photo away to be processed.

Quality and metadata

A reasonable question is what changes when HEIC becomes JPG. The honest answer is: very little that you will see, and a few things you might actually want.

Visual quality

Both HEIC and JPEG are lossy formats, so a direct conversion at high quality is effectively transparent — the resulting JPG looks the same as the HEIC original to the eye. HEIC’s compression is more efficient, which is why the HEIC file is usually smaller for the same visual quality, but the photo itself does not visibly degrade when re-encoded. If you re-encode the same JPG many times, generation loss accumulates — but a single high-quality conversion is invisible in practice.

The one caveat is size. A converted JPG will typically be larger than the HEIC it came from, often 2–3× the bytes, because JPEG’s compression is less aggressive. That is the trade-off for compatibility. If you also need a size cap, the next section explains how to combine conversion with compression.

Metadata

When the tool produces the new JPG, it encodes only the pixels. The original HEIC’s EXIF metadata is stripped — that means camera settings, lens information, timestamp, and crucially any GPS coordinates that recorded where the photo was taken.

For sharing, that is usually a feature. The JPG you send to a form, attach to a job application, or share with a relative carries no information about where you were when you took it or what device you used. If you need to keep metadata, you will need a tool that explicitly preserves EXIF; this one does not.

One side-effect to know about: if your original HEIC relied on an EXIF orientation tag to display upright (many phone cameras do), the converted JPG may appear rotated once the tag is gone. Check the before/after preview; if it looks wrong, rotate the photo in your phone’s editor first, then convert.

Convert versus compress

Conversion and compression are related but separate jobs, and understanding the difference helps you pick the right tool.

Conversion means changing the format — from HEIC to JPG — so the photo opens everywhere. The goal is compatibility, not size. The output is a high-quality JPG at the original resolution, usually a few megabytes. If all you need is “make this HEIC readable by humans and forms,” pure conversion is what you want, and this page does that.

Compression means making the file smaller — hitting a specific KB target that a form, portal, or upload imposes. Most online forms do impose one: ≤100KB for government portals, ≤200KB for visa photos, ≤50KB for some exam registrations. A pure conversion ignores size; a compressor always outputs JPG anyway.

If you have an iPhone photo and a form with a KB limit, you need both: convert the format and hit the size. That is what the compressor pages do in one step — type the KB target, get a JPG that fits, locally. Pick a target if you also need a size limit:

• Compress HEIC to 50KB — strict caps, exam registrations, small avatars.
• Compress HEIC to 100KB — the most common ceiling, government and ID forms.
• Compress HEIC to 200KB — visa and document scans with a generous allowance.
• Compress HEIC to 500KB — high-quality uploads with a loose ceiling.

For a deeper walkthrough of getting the file size down — what trade-offs are involved, what to expect visually, and how the compressor works under the hood — see Reduce HEIC file size.

Privacy: nothing leaves your device

The privacy claim deserves to be stated plainly, because the photos people convert are often personal — family shots, document scans, photos meant for a specific recipient.

Your image never leaves your device. There is no upload, no cloud processing, no server that sees your photo. Decoding and re-encoding happen locally inside your browser through a WebAssembly module. When you close the tab, the data is gone — there is no account, no storage, no analytics applied to your image, no copy kept anywhere.

This is a meaningful difference from most “HEIC to JPG” websites. The typical pattern is that you upload your photo, the site’s server converts it, and the result is sent back to you. That works, but it means a copy of your photo existed on someone else’s computer, even if briefly, and you have no way to verify it was deleted. Some services keep uploads for hours or days; some use them for analytics; a few have been caught training models on user uploads.

Running everything locally closes that question entirely. The conversion cannot leak what was never transmitted. There is no server breach that could expose your photo, no logging accident, no policy change that retroactively changes what a service can do with files you uploaded years ago.

It is also faster — no round trip to a server and back — and works the same way on a slow connection as a fast one, because the only thing that needs to move over the network is the small WebAssembly module itself, downloaded once.

Related

If your problem is size rather than format, the same engine hits any target KB:

• Compress HEIC to 50KB — small caps and exam photos.
• Compress HEIC to 100KB — the most common form ceiling.
• Compress HEIC to 200KB — visa and document scans.
• Compress HEIC to 500KB — generous allowances.
• Reduce HEIC file size — a deeper walkthrough of getting HEIC smaller.