Convert HEIC to JPG

What this HEIC to JPG converter actually does

You hand over one photo or the whole camera roll. Each file is read, decoded, re-encoded as JPG at the quality you choose, and handed back — with a download for every picture and one ZIP for the lot. None of it travels anywhere: this site runs nothing that could take a photograph off you in the first place.

Before anything is converted you see what you dropped: file name, size, pixel dimensions, and whether the file carries GPS coordinates. Those dimensions come out of the file header, not out of a decode, so they appear the instant you drop the files rather than after a second of work. That ordering is the point. The decision you are about to make — quality, location data, whether to scale anything down — needs that information first, not afterwards on a receipt.

HEIC and JPG, in brief

HEIC

Full name	High Efficiency Image Container
Extension	.heic, .heif
Format type	Lossy raster image container (HEIF)
MIME type	image/heic

JPG

Full name	Joint Photographic Experts Group
Extension	.jpg, .jpeg
Format type	Lossy raster image
MIME type	image/jpeg

Why your iPhone writes HEIC in the first place

HEIC is a container built around HEVC, the same video codec used for 4K streaming, applied to a single frame. It is roughly twice as efficient as JPEG at equivalent visual quality, which is how a twelve-megapixel photo fits into two megabytes instead of four. Apple switched the default camera format in iOS 11 and never switched back, so every iPhone since 2017 fills its camera roll with files that Windows, older Android builds, most upload forms and a good number of web apps still refuse to open.

That gap is the entire reason this page exists. The format is better; the support is worse. Converting is not an admission that HEIC was a mistake — it is what you do when you need to hand the picture to something that has never heard of it.

Who is usually standing in front of these files

The photographs mostly do not belong to the person converting them. Somebody with an iPhone sent a folder — grandchildren, a leaking pipe, a dented fender, a move-out inspection — and the machine that has to open them shows a row of blank icons instead. A grandparent, a claims adjuster, a caseworker, a contractor writing an estimate from a customer's photos.

Windows can be taught the format. It takes the HEIF extension from the Microsoft Store, and on many builds a second, paid extension for the HEVC part underneath, and both of those assume you are allowed to add software to the desktop you are sitting at. A work PC with the Store switched off, a computer at a front counter, a machine signed in under an account that is not yours: none of them will let you. Opening a tab is the one thing every one of those desks still permits, which is why doing the decode in the page is not merely tidier than the extension — quite often it is the only route left.

The JPG will usually be bigger, and that is correct

Expect the converted file to land somewhere between one and a half and two times the size of the original. People often read that as a failed conversion. It is not. You are moving from a modern codec to one designed in 1992, and the extra bytes are what compatibility costs. HEIC vs JPEG puts numbers on that trade, and on the cases where the newer format is measurably worth keeping.

HEIC is not the only format that arrives this way. AVIF comes out of the same family of codecs and fails to open in the same places for the same reason — the software predates it — so a file ending in .avif belongs at AVIF to JPG rather than here.

If the size matters more than the format, the quality slider is right there, and dropping from 82 to about 70 is invisible on a photograph while cutting the file meaningfully. If you need to hit a specific number — a form that caps at 2 MB, an email attachment limit — convert here first and then compress the JPG to a target size, which searches for the quality that lands under your limit instead of making you guess.

Two decoders, and your browser picks the cheaper one

Safari on macOS and iOS can decode HEIC using the same system codec the Photos app uses. If you are on an iPhone or a Mac in Safari, that is what runs, and nothing at all is downloaded. Chrome, Firefox and Edge cannot decode HEIC — not even on a Mac, where the operating system decoder exists but the browser never calls it. In those browsers a decoder is fetched once, about one megabyte, and cached. The progress bar shows the real byte count, because a fake one is worse than none.

The decoding runs in a background worker rather than on the page. A twelve-megapixel photo takes a few hundred milliseconds to decode, and thirty of them on the main thread would freeze the tab solid. Off the main thread, the page stays responsive and you can still remove a file or change the quality while the batch runs.

The location data, and why it matters more here

A HEIC straight out of an iPhone carries an EXIF block, and that block normally includes the exact coordinates where the photo was taken. Home addresses, schools, hotel rooms. Location removal is switched on by default here for that reason. Orientation is a separate matter and is always preserved: the rotation is applied to the pixels during decoding, so the picture comes back upright whether or not you keep the metadata. For a photo that is already a JPEG or a PNG, converting it is the wrong instrument for the same errand: removing EXIF data clears the block without touching the pixels at all, and shows you the coordinate before it goes.

That is also the argument against uploading photos to a conversion site. Whatever the privacy policy says, the coordinates arrive on the server before anything is stripped. Here the file is opened by your own browser, and you can confirm it in the network tab.

Live Photos, bursts, and what one JPG can hold

A JPG holds exactly one image. A Live Photo is a still plus a short video, and a burst is a sequence — so the conversion keeps the primary image, the same key frame the Photos app shows you, and says so rather than quietly discarding half the file. Files that turn out not to be HEIC at all get flagged instead of failing: a JPEG that someone renamed, an AVIF that needs a different codec, a partial copy that never finished. The file is identified by its magic bytes, never by its extension, because the extension is a claim the user made and the bytes are a fact.

Why there is no JPG to HEIC direction

Because no browser can encode HEIC. The decoding side is solvable — that is what the decoder above does — but writing HEVC requires an encoder no browser exposes and a patent situation nobody wants to walk into. A page promising it would either upload your photos or not work. The honest sibling in this cluster goes the other way instead: HEIC to PNG, for when the picture is going into an editor, a print pipeline that refuses lossy input, or anywhere the alpha channel has to survive. Expect several times the file size — that is what lossless costs.

There is a third destination worth knowing about, and it is the one people actually want more often than they expect. If the reason you are converting is that the pictures have to be sent somewhere as a single attachment — a claim, an expense report, a set of receipts photographed on a phone — then separate image files are an awkward halfway house. HEIC to PDF collects the whole batch into one document instead, in an order you set, and applies the same rotation handling described above so that portrait shots get portrait pages.