Since iOS 11 the iPhone saves photos as HEIC by default: a HEIF container holding HEVC-compressed image data. At the same visual quality it is roughly half the size of a JPG, which is why Apple switched. The cost is compatibility — plenty of Windows setups, upload forms, and older software still refuse to open it. Converting to JPG trades that smaller file for a format everything can read.
Why the file will not open
HEIC needs an HEVC decoder. Windows 10 and 11 require the HEIF Image Extensions from the Microsoft Store, and the codec half of that has historically been a paid add-on. Many upload forms, email clients, and older versions of Photoshop simply reject the file outright. JPG has none of these problems.
What the conversion costs you
HEIC stores 10-bit colour and can carry an HDR gain map; JPG is 8-bit with no HDR. On an ordinary photo you will not see a difference, but in high-contrast scenes — backlit subjects, sunsets — highlight gradients can turn slightly harder. Depth data and the video track of a Live Photo are not carried over either: you get the still frame.
Metadata does not come along
The JPG is drawn fresh in your browser, so EXIF such as capture date, camera model, and location is not copied into it. That makes the converted file safer to post publicly; if you need the original metadata, keep the HEIC alongside the JPG.
- A Windows PC, a Linux box, or an older phone cannot open the photos you just sent from your iPhone.
- An upload form, a print shop, or an email client accepts JPG only and rejects the file without explaining why.
- To avoid the problem at the source: on the iPhone, Settings → Camera → Formats → Most Compatible makes the camera shoot JPEG directly. Photos then take up roughly twice the space, which is exactly the trade Apple made by defaulting to HEIC.
- You plan to edit the photo further, or it has transparent areas to keep — the HEIC to PNG converter skips the JPG step entirely.
- The converted JPG files are larger than you expected — run them through the image compressor to bring the size back down.
Does converting to JPG lose quality?
The photo is compressed as JPG on the way out, but at the default quality the loss is very hard to see. The change you are more likely to notice is structural: HEIC is 10-bit and JPG is 8-bit, so smooth gradients in very bright or very dark areas have fewer steps to work with.
What happens to a Live Photo?
You get the still frame. A Live Photo is a HEIC image paired with a short video track, and JPG has nowhere to put the video. If you need the motion, export it as a video from the Photos app instead.
Why is the JPG bigger than the HEIC was?
That is expected. HEVC compresses far more efficiently than JPG, so the same photo typically lands 1.5 to 2 times larger as a JPG. You are paying file size for the ability to open it anywhere.
Are my photos uploaded anywhere?
No. The HEIC decoder runs in your browser, so the photos never leave your device. That matters more than usual here, since iPhone photos routinely carry location data in their EXIF.
Most HEIC files come straight off an iPhone or iPad, often after an AirDrop, a USB transfer, or a cloud download that kept the original format. This page is built for exactly that case: it accepts only .heic and .heif files and always produces JPG. Below is what happens to a photo on the way through, which setting actually matters, and what to check when a conversion does not come out the way you expected.
Why the first conversion takes longer
Browsers cannot read HEIC on their own, so this page loads libheif, an open-source HEIF decoder compiled to WebAssembly, and runs it on your device. The decoder is only fetched on this tool, and it starts downloading in the background as soon as the page is idle, before you have picked a file. Once you add a photo, a line under the upload area tells you where it stands: preparing, ready, or delayed.
Once it is ready, every photo goes through two stages you can follow in the file list. Decoding is the expensive part: the full-resolution HEVC data is unpacked in a background worker. After that the pixels are drawn onto a canvas and encoded as JPG. On a recent laptop this takes a moment per photo; on an older phone the decode step is noticeably slower. That is normal, and it is not a sign that anything is being uploaded.
If the decoder could not load, for example because the connection dropped, the status turns amber and the page tries again when you press Convert. You do not need to reload the page or add your files again.
Why quality above 92% does not help
The HEIC route has one step the other converters on this site do not. The decoder first hands the photo over as an intermediate JPEG at 92% quality, and the quality slider, which runs from 10% to 100% and starts at 85%, then controls a second encode that becomes your download. The slider still decides the final file size, but it cannot bring back detail that the 92% step has already rounded off.
In practice, 85% is a sound choice for sharing and viewing on screen, and 90–92% is the useful ceiling if you plan to print or keep editing. Going above 92% makes the JPG heavier without making it any sharper. If you want an untouched master copy, keep the original HEIC next to the JPG.
Metadata: the JPG starts clean
The JPG is written from canvas pixels, and a canvas carries no metadata. Capture date and time, camera and lens model, exposure settings, and GPS location are not copied from the HEIC into the converted file. For photos you are about to post publicly, that is a useful side effect: the location your phone recorded is gone.
It has a cost as well. Photo libraries and many apps sort pictures by the EXIF capture date, and without it they fall back to the file date, which is the moment you downloaded the JPG. If you are converting an album for your archive, keep the HEIC originals so the real dates stay available.
Rotation is taken care of before any of this. libheif applies the rotation and mirroring stored in the HEIC while decoding, so the pixels come out upright and there is no orientation tag left for another program to misread.
Files that hold more than one image
A HEIF container can store several images. The decoder reads the list of top-level images in the file but converts only the first one, and a JPG can hold a single picture anyway. For an ordinary iPhone photo that first image is the photo itself. For a HEIF that bundles several shots, you get one JPG, and the others are not exported.
HDR follows the same logic. The decoder produces standard 8-bit RGBA pixels, so on an HDR-capable screen the converted photo will look a little flatter in its brightest areas than it does in the Photos app. That is expected, and no setting on this page changes it.
Converting a whole batch
You can add many files at once, but they are converted one after another in the order shown, not in parallel, and each photo is decoded at full resolution before the next one starts. On a phone or a computer with little free memory, splitting a camera roll into smaller groups is easier on the browser than adding hundreds of photos in one go.
Download All saves each finished JPG as a separate download rather than a ZIP, so your browser may ask once whether this site is allowed to download multiple files. Each file keeps the part of its name before the first dot: IMG_1234.HEIC becomes IMG_1234.jpg, but trip.day1.heic becomes trip.jpg, so two photos can end up with the same name and the browser will add a number to the second one.
When one file fails with a decode error while the rest succeed, the file itself is usually the cause: it may be damaged, cut short by an interrupted transfer, or a different format that was renamed to .heic. Exporting the original from the device again usually fixes it. Files that are neither named .heic or .heif nor reported by your system as HEIC or HEIF are turned away when you add them, with a note under the upload area.