Take one photo and save it two ways. As HEIC it comes out at about 1.8 MB. As JPG at quality 90 it comes out at about 3.4 MB. View them side by side at normal size and you cannot tell them apart. Zoom to 400% and the JPG looks a little softer in the hair, the grass, the dark wall behind the subject.
That softening is the honest answer to the question in the title: yes, the conversion loses data at the pixel level, and no, it usually does not lose what your eyes are doing. The useful question is when that "yes" turns visible. This article shows it with real numbers and tells you how to convert without crossing that line.
What converting actually does
HEIC stores the image with HEVC (H.265), a codec built for video. JPG stores it with a DCT block transform plus chroma subsampling. When you convert HEIC to JPG, the image gets decoded and re-encoded in a different scheme, and the re-encode is lossy. Some information does not survive the round trip.
Two things change. First, the compression method produces different artifacts. HEVC hides its losses better than JPG does at the same bitrate, which is the whole reason a HEIC file is smaller. Second, the color depth drops. HEIC supports 10-bit or 16-bit channels; JPG is fixed at 8-bit. If your photo stores 10 bits per channel, converting to JPG throws away the extra tones permanently.
For the byte-level picture of how HEIC is put together, the HEIC technical deep dive walks through the container boxes and file signature.
Why bit depth is where the detail hides
An 8-bit channel holds 256 levels of red, green, and blue each. A 10-bit channel holds 1,024, which is 16 times more precision per color. On most phone photos you cannot see the difference, because a photo rarely fills the whole range with smooth gradients. The difference shows up in the obvious places: a sunset sky that should fade from deep orange to pale yellow, a portrait lit against a window. Those smooth ramps are where an 8-bit file starts to show bands, distinct steps instead of a continuous fade.
So the loss is real, but it is not random. It lands on gradients and low-light noise before it lands on a face or the sharp edge of a building. If you convert at high quality, the other losses (blocking, ringing, softening) stay small enough that you will not notice them without zooming.
HEIC vs JPG at three quality settings
The same 12 MP photo, saved four ways, with HEIC as the reference:
| File | Size | What changes vs HEIC |
|---|---|---|
| HEIC (source) | 1.8 MB | baseline |
| JPG quality 95 | 4.1 MB | nothing visible at normal zoom |
| JPG quality 90 | 3.4 MB | slight softening in fine texture at 400% |
| JPG quality 75 | 2.1 MB | banding in skies, ringing around text |
The numbers are typical, not exact; your photo and camera change them. The pattern does not. You can convert at a size close to the original HEIC and keep the visible detail. You only start paying for it when the quality slider drops far enough that the encoder starts cutting corners.
Where the loss shows up first
If you want to know what a bad conversion costs, check for these in order:
- Banding. Smooth gradients collapse into steps. This is the bit-depth loss and the first thing to appear.
- Ringing. Thin halos around high-contrast edges, most visible on text and window frames.
- Blocking. Visible 8 × 8 grid blocks in flat areas, usually gone above quality 80.
A single high-quality conversion triggers none of these on most photos. Re-encoding is what compounds them: every pass adds a little quantization noise, and the noise adds up. That is the generation-loss effect explained in detail in lossy vs lossless compression.
How to convert without losing visible detail
The rule is short: convert once, from the original HEIC, at high quality. Do not convert from a JPG that has already been through an encoder, and do not run the result through another conversion later.
Our HEIC to JPG converter runs the conversion in your browser with a quality setting you control, and it reads straight from the original file. Drop the HEIC in, pick quality 90 or higher, and what you get is about as much as a JPG can carry.
If you need lossless output or transparency, JPG is the wrong target regardless of quality; that is a job for PNG. HEIC vs PNG covers when that switch is worth it, and the HEIC to WebP guide covers the format for people shipping images to the web.
The bottom line
Converting HEIC to JPG does lose data, because JPG cannot hold everything HEIC can. At quality 90 or above, the loss stays below what you can see at normal viewing sizes on almost every photo. If someone tells you conversion always ruins image quality, they are describing a low-quality conversion, not conversion itself.
