How to Convert HEIC to JPG Online Free

HEIC is the photo format an iPhone saves by default. It uses the same efficient HEVC compression that video uses, so a HEIC photo is roughly half the size of the equivalent JPG at the same quality. The problem is not the format itself, it is that a lot of software still cannot open it: older Windows PCs, many web upload forms, some email clients, and plenty of editing tools show nothing but an error.

Converting HEIC to JPG trades that space efficiency for the thing JPG has always had going for it, which is that absolutely everything can read it. This guide covers what actually changes in the file, the very different ways the two formats compress a photograph, how to convert in your browser, and the one case where you should hold onto the HEIC.

Why HEIC needs converting at all

A HEIC file stores the same photograph a JPG would, just packed more tightly. When you convert to JPG you are re-encoding the decoded image into the older, simpler JPG scheme. Nothing about the picture you see is lost in any way you will notice at a sensible quality setting, because both formats can represent full-color photographs. What you gain is compatibility, and what you give up is the smaller file size HEIC was designed to deliver.

HEIC is a specific brand of the High Efficiency Image File Format, or HEIF, which the Moving Picture Experts Group standardized as ISO/IEC 23008-12 in 2017.^[2] The .heic extension signals that the image data inside is coded with HEVC (High Efficiency Video Coding, also known as H.265), the same codec used for modern video.^[1] Apple adopted it across iOS and macOS in 2017, which is why the format is now everywhere on Apple devices and almost nowhere else. That split, ubiquitous on one platform and unreadable on many others, is the entire reason the conversion exists.

It is worth knowing that HEIC can also hold extras a plain JPG cannot, such as the depth data behind Portrait mode or a short Live Photo motion clip. A straight conversion keeps the still image and quietly drops those extras. For an ordinary snapshot you will never miss them, but if the depth or motion matters to you, that is a reason to keep the original.

Two ways to compress the same photo

HEIC and JPG both start from the same thing: a grid of pixels, each with a red, green, and blue value drawn from a space of roughly 16.7 million colors. Where they differ is in how they throw away the data your eye is least likely to miss, and HEVC is simply a much newer and cleverer scheme than the one JPEG uses.

JPEG, standardized as ISO/IEC 10918 and first published in 1992, is one of the oldest image compression standards still in daily use.^[3] In everyday files its compressed data is wrapped in the JFIF interchange structure that gives a .jpg its familiar layout.^[4] Its approach is elegant but dated: it converts color into a brightness-plus-color representation, often discards half or three quarters of the color detail because human vision is far more sensitive to brightness, chops the image into 8-by-8 pixel blocks, and transforms each block into frequency coefficients that can be quantized away. HEIC keeps the same broad idea of discarding imperceptible detail but applies decades of additional research, which is why it reaches the same visual quality in roughly half the bytes.

The practical upshot is that HEIC is the more efficient format and JPG is the more compatible one. Converting between them is not about fixing a broken file; it is about choosing which of those two properties you need for a given task.

How the conversion works under the hood

A HEIC-to-JPG converter runs a short, predictable pipeline. First it decodes the HEIC, which means running the embedded HEVC bitstream through an HEVC decoder to reconstruct the full grid of pixels the image describes. This step alone is why some old software fails on HEIC at all: without an HEVC decoder present, the operating system cannot turn the file back into a picture.

Once the image is decoded into raw pixels, the converter re-encodes those pixels using the JPEG algorithm at the quality level you pick. This is a fresh, independent compression pass: the JPEG encoder does not know or care that the source was HEIC, it simply compresses the pixel grid it was handed. Finally the converter writes out a standard JFIF-wrapped .jpg, copies across whatever metadata it can preserve, and hands you the file. Because the picture passes through a raw-pixel stage in the middle, the JPG's quality is governed entirely by your quality setting, not by how the HEIC was originally compressed.

HEVC intra-coding versus JPEG's DCT blocks

The reason HEIC is so much smaller comes down to one word: prediction. JPEG treats every 8-by-8 block in isolation. It has no way to say "this block looks a lot like the block to its left"; it just transforms each block into frequency coefficients using the Discrete Cosine Transform, quantizes those coefficients to throw away high-frequency detail, and packs the result. That independence is simple and fast, but it is also wasteful, because real photographs are full of regions that resemble their neighbors.

HEVC uses intra-frame prediction, the same technique that lets a single video frame compress well on its own. Before coding a block, the encoder predicts what it should look like based on the already-decoded pixels around it, using one of many directional prediction modes, and then stores only the small difference between the prediction and the real block. Because that difference is usually tiny, there is far less data left to compress. HEVC also works with flexible block sizes rather than JPEG's fixed 8-by-8 grid, so it can use large blocks for smooth areas like a clear sky and small blocks for detailed areas like foliage. Stack these advantages together and you get the same-looking photo in about half the space, which is exactly the efficiency you surrender when you convert to JPG.

Convert HEIC to JPG, step by step

1. Open the converter and add your HEIC

   Open the FileFormer image converter and drop the HEIC photo in. It is decoded right in your browser, so the picture is never uploaded anywhere.

2. Set the output to JPG

   Choose JPG as the target. This is the format that upload forms, older PCs, and email clients all understand without any extra software.

3. Pick a quality level

   Keep quality high, roughly 85 to 95. That gives you a JPG you cannot tell apart from the HEIC while keeping the file reasonable. Lower it only if you specifically need a smaller result.

4. Convert and download

   Convert and save. You now have a JPG you can post, print, or attach anywhere, alongside the untouched original if you kept it.

What happens to quality and size

The visible quality stays essentially the same at a high setting. The file size, however, usually goes up, because JPG is a less efficient compressor than HEIC. It is normal for a JPG to be noticeably larger than the HEIC it came from even though it looks identical. That is the direct cost of switching to the more compatible format.

Metadata, orientation, and lost extras

A HEIC file carries more than just pixels. Because HEIF is built as a container, it can wrap several related items together: the main still image, a thumbnail, an embedded color profile, EXIF metadata such as the camera model, exposure, and GPS location, and, on Apple devices, the depth map and Live Photo motion that ordinary JPGs cannot represent. When you convert, the tool has to decide what survives.

The main still image always survives, that is the whole point. EXIF metadata and the color profile can usually be copied straight across, since JPEG supports both. The extras that JPEG has no slot for, the depth map and the motion clip, are dropped, because there is simply nowhere in a standard JPG to put them. Orientation deserves special mention: cameras often store a photo in its raw sensor orientation plus a flag that says "rotate this 90 degrees for display." A good converter reads that flag and bakes the correct rotation into the JPG so the picture appears upright; a poor one can produce a sideways image. If a converted photo comes out rotated, mishandled orientation metadata is almost always the cause.

Real-world scenarios and settings

The right quality setting depends on where the JPG is going. A few common cases:

The recurring theme is that JPG is a destination for sharing, not a place to store your originals. Convert a copy when something downstream cannot read HEIC, and let the smaller, higher-fidelity HEIC remain your master.

JPG versus PNG and WebP as targets

JPG is not the only format you can convert a HEIC to, and it is not always the best one. It is worth understanding the three realistic targets so you pick the one that fits the job rather than defaulting to JPG out of habit.

JPG is the maximum-compatibility choice. Every device, browser, upload form, and printer made in the last thirty years reads it, and its lossy compression is well suited to the photographic content most HEIC files contain. Its weaknesses are that it cannot store transparency, it is less space-efficient than modern formats, and repeated re-saving slowly degrades it. For a photo that needs to open literally anywhere, it remains the safe answer.

PNG is the lossless choice. Converting HEIC to PNG reproduces the decoded image pixel for pixel with no compression artifacts, and it supports transparency. The catch is size: because PNG is lossless and built for graphics rather than photographs, a photographic PNG is usually much larger than the equivalent JPG, and larger than the original HEIC. Choose it when you need perfect fidelity or an alpha channel, not when you need a small file.

WebP is the modern middle ground. Converting HEIC to WebP keeps a file nearly as small as the HEIC while enjoying broad support across current browsers and many apps, and it can carry transparency too. Its only real drawback is that some older or niche software still does not read it. If your destination is the web or a modern app, WebP often gives you the best of both worlds: small like HEIC, compatible like JPG. The honest rule is to reach for JPG when compatibility is the priority, PNG when fidelity or transparency is, and WebP when you want small and web-friendly at once.

When to keep the HEIC instead

Keep the HEIC when you are only storing photos on Apple devices and want them to take up less space, or when the shot uses depth or motion you care about. If you need JPG only for one upload, convert a copy and leave the library in HEIC. If you want the compatibility of a modern format without JPG's bulk, a better middle ground is often converting HEIC to WebP, which stays small and is widely supported on the web. Repeated JPG re-saves also compound losses, since each save re-applies lossy compression, so an archive kept in HEIC and exported to JPG on demand stays cleaner than one converted to JPG once and edited thereafter.