Working…
The iPhone format that half the internet refuses to open.
Drop a HEIC or HEIF photo and get a JPG, PNG or WebP back. It runs entirely in your browser, including on Windows and Android where there is no built-in HEIC support at all. Multi-image HEIC files are handled too, and every frame is offered separately.
Drop or click to upload
Drag & drop, or pick from your photos
HEIC, HEIF, HIF — 40MB max
Since iOS 11, iPhones have taken photos as HEIC rather than JPG. It is a genuinely better format: roughly half the file size at the same visible quality, with support for 10-bit colour and multiple images in one file. Apple did not make a bad choice.
The problem is everything else. Windows does not open HEIC without an extra codec from the Microsoft Store. Most Android phones cannot display one. A large share of upload forms, older content systems, print shops and email clients reject the file outright, often with an unhelpful error that just says the format is not supported.
So the file is fine, and it is also useless to you in the moment. Converting to JPG is the fix.
This is the part most converter pages leave out, and it is usually the answer people actually needed. You can tell the iPhone to shoot JPG instead:
From then on the camera writes JPG directly. You give up some storage efficiency and 10-bit colour, which for most people is a fair trade against never hitting this again. There is a second setting worth knowing: under Settings, Photos, the option Transfer to Mac or PC set to Automatic converts photos to JPG as they copy off the phone, while Keep Originals sends the HEIC across untouched.
| Where | HEIC support |
|---|---|
| Apple devices | Native everywhere. iOS, iPadOS and macOS open HEIC with no extra software, which is why the problem is invisible until you send a file to someone else. |
| Windows 10 and 11 | Needs the HEIF Image Extensions codec from the Microsoft Store. Without it, File Explorer shows no thumbnail and Photos will not open the file. |
| Android | Varies by manufacturer and version. Many devices display HEIC in the gallery but cannot attach or upload it successfully. |
| Chrome, Firefox, Edge | No HEIC decoding at all. This is why a page like this one has to carry its own decoder. |
| Safari | Decodes HEIC natively, because it inherits the system codec. |
| Upload forms and print shops | Usually reject it. JPG remains the safe default when something else has to accept the file. |
A HEIC container is not limited to a single image. Burst shots, Live Photo stills and some editing apps store multiple images in one file. Most converters silently take the first one and discard the rest.
This tool reads how many images the file contains and, when there is more than one, shows every frame so you can pick. If you have ever converted a HEIC and felt the result was not the picture you were looking at, this is usually why.
If your browser can decode HEIC on its own, which in practice means Safari, that path is used and nothing extra is downloaded. Everywhere else the page fetches a WebAssembly build of libheif, the reference open-source HEIF decoder, the first time you convert something. It is around 1.4MB, it is fetched once and then cached, and it runs inside the page.
Your photo is not part of any of that. It is read from your device into memory, decoded, drawn to a canvas and encoded again, all locally. Nothing is uploaded, which is also why there is no queue, no account, and no file-count limit.
One consequence worth knowing: converting re-encodes the image, so the original EXIF block does not carry across. That is usually welcome, since it drops the GPS coordinates too. If you want to see what was in there first, the EXIF viewer reads the whole metadata block.
Keep going without re-uploading — your image carries over to the next tool automatically.