HEIC vs JPG
A practical head-to-head: how each format compresses, what each one keeps, where each works, and which to use for which job.
The verdict first
HEIC is the better format for keeping photos. JPG is the better format for sending them anywhere. That one sentence covers most real decisions: let your iPhone keep shooting HEIC, and convert to JPG at the moment a photo leaves your own devices, whether that is an upload form, an email to someone on Windows or a print order.
The sections below explain why, comparing the two formats on compression, image quality, color depth, compatibility, editing, metadata and storage cost. If you need the background on what HEIC is in the first place, start with what a HEIC file is and come back.
HEIC and JPG side by side
| Feature | HEIC | JPG |
|---|---|---|
| Introduced | HEIF standard 2015; on iPhone since 2017 | 1992 |
| Compression engine | HEVC (H.265) intra-frame coding | Discrete cosine transform on 8 by 8 pixel blocks |
| Typical size for the same photo | Often around half of the JPG | Baseline |
| Color depth | 8 or 10 bits per channel, higher possible | 8 bits per channel in practice |
| HDR | Supported natively and through gain maps | Only through newer gain map extensions, with patchy support |
| Transparency | Possible (alpha layer) | No |
| Multiple images, depth maps | Yes, in one file | No |
| Metadata | EXIF and XMP | EXIF and XMP |
| Opens everywhere | No: Apple devices, many Android phones, Windows with add-ons | Yes: every device, browser and upload form |
| Editor support | Good on Mac, mixed elsewhere | Universal |
Why HEIC files come out smaller
JPG works by slicing a photo into 8 by 8 pixel squares and describing each square with a set of frequency values, discarding the fine ones the eye is least likely to miss. That design dates from an era of slow processors, and it treats every square the same way regardless of what is in it.
HEVC, the engine inside HEIC, is far more adaptive. It splits the image into blocks that can be as large as 64 by 64 pixels in flat areas and much smaller where there is detail, so a clear sky costs very little while a face gets the attention it needs. It also predicts each block from its already decoded neighbors, choosing among dozens of directional patterns, and only stores the difference between the guess and reality. Filters applied during decoding then smooth over block edges before you ever see them.
The result is that HEIC typically needs far fewer bytes to reach the same visual quality. The exact ratio depends on the scene. Smooth, evenly lit shots shrink the most. Photos full of random fine texture, such as dense leaves, sand or high-ISO noise in a dark room, shrink less, because there is less predictable structure for the codec to exploit.
Visual quality: what you can and cannot see
At normal viewing sizes, a straight-from-the-camera HEIC and a high-quality JPG of the same scene look the same to almost everyone. The differences show up at the edges of the format's comfort zone.
- Under heavy compression, JPG falls apart into visible squares and halos around sharp edges. HEVC tends to smear fine detail into a slightly painted look instead, which is usually less jarring.
- In smooth gradients, such as a sunset or a studio backdrop, 8-bit JPGs can show faint banding. HEIC's support for higher bit depth helps here when the camera uses it.
- When zoomed to 100 percent, you can sometimes see that a converted JPG carries tiny new artifacts on top of the original HEIC's. At a quality setting of 90, those are very hard to spot.
Converting HEIC to JPG is a lossy step, because the photo is decoded and then compressed again with a different method. It does not, however, make a photo look noticeably worse when done at a sensible quality. The practical rule: convert from the original HEIC once, at quality 85 to 95, rather than converting a JPG of a JPG.
Bit depth, color and HDR
JPG as people actually use it stores 8 bits per color channel, which gives 256 levels each of red, green and blue. HEIC can store 10 bits or more per channel, giving four times as many levels in each, which is what makes smooth HDR highlights possible.
Recent iPhones also tuck extra brightness information into their HEIC files so that HDR-capable screens can show bright areas, like a sunlit window or a sparkle on water, brighter than the rest of the picture. On a regular screen the photo simply looks normal.
When you convert to JPG with HEIC to PIC, the output is a standard 8-bit image. HDR brightness and the extra bit depth are not carried over, so a photo that glowed on your iPhone will look like a regular, well-exposed photo in the JPG. For sharing, uploads and printing that is exactly what you want. If the HDR look matters, keep the original HEIC and share it to other Apple devices directly.
Compatibility in practice
This is where JPG wins outright. Every browser, operating system, photo printer, office suite, messaging app and web form understands it. Nothing needs installing, and nobody has to ask what the file is.
HEIC works without fuss inside the Apple ecosystem, on recent Android phones through Google Photos, and on Windows once the Microsoft Store extensions are installed. It does not work as an image on most websites, and it is regularly refused by job portals, rental and marketplace listings, school systems and older content management tools. If you send photos to many people outside Apple's world, the guide to sending iPhone photos as JPG covers ways to share that convert along the way.
Editing: which format holds up better
Both formats are lossy, so neither is ideal as a working file you save over and over. Every time a JPG is opened, edited and saved again, it is recompressed and loses a little more detail. After several rounds, the damage becomes visible in skies and around text.
HEIC has the same problem in theory, and it has a practical one too: many editors outside the Mac either cannot open it or can open it but not save it. Apple's Photos app avoids the issue by storing your edits as instructions and keeping the original untouched.
For serious editing outside Apple Photos, convert the HEIC once to a lossless format, do all your work there, and export a JPG only at the end. The comparison of HEIC and PNG explains when a lossless intermediate is worth the larger file.
Metadata: same fields, different handling
Both formats store EXIF and XMP metadata, so a HEIC and a JPG straight from a camera can carry the same capture date, camera model, exposure settings and GPS coordinates. HEIC can additionally hold depth maps and other auxiliary data that JPG has no standard place for.
The bigger difference is what happens during conversion. HEIC to PIC does not copy EXIF into the converted files, so the JPG you download has no location or capture date embedded. That is a privacy plus when you post photos publicly, but it means sorting apps will not know when the shot was taken. If you want to check what a photo reveals before you decide, the HEIC Metadata Viewer reads it locally, and the full privacy picture is in the guide to what iPhone photo metadata reveals.
Storage cost: the reasoning, not a promise
It is tempting to quote a precise saving, but the real figure depends on what you photograph, your iPhone model and its camera settings. A safer way to think about it is in proportions. If your HEIC library is roughly half the size it would be as JPG, then every photo you keep as HEIC frees space for another one.
Where that matters is at plan boundaries. Cloud storage is sold in tiers, and a library that sits just under one tier as HEIC might overflow into the next as JPG. As an illustration only, a collection that would occupy 300 GB as JPG could land somewhere near 150 GB as HEIC, which is the difference between needing a 200 GB plan and needing a much larger one.
The same logic applies to the phone itself. Newer iPhones with 48 megapixel cameras produce large files, and the gap between formats grows with resolution. If your phone is always nearly full, switching to JPG will make that worse, not better.
Decision guide by scenario
Use this table when you are not sure which format a particular job calls for.
| Scenario | Use | Why |
|---|---|---|
| Everyday shooting on an iPhone | HEIC | Smaller files, HDR, no downside on Apple devices |
| Uploading to a job portal, rental site or government form | JPG | Upload fields often reject HEIC |
| Emailing photos to someone on Windows | JPG | Opens without extra extensions |
| Ordering prints or photo books | JPG at high quality | Print services expect it; HDR does not print anyway |
| Long-term archive of originals | HEIC (the originals) | Full quality, metadata and HDR preserved |
| Heavy editing in a third-party editor | Lossless copy, then JPG | Avoids repeated recompression |
| Posting publicly without location data | Converted JPG | The converted copy carries no EXIF |
| A device that is always full | HEIC | Switching to JPG roughly doubles photo storage |
| A workplace where nobody can open HEIC | JPG at capture | Saves converting every single photo |
For that last case, the guide to switching your iPhone to Most Compatible shows the setting and what it changes.
Converting without regret
When a photo does need to be a JPG, convert it from the HEIC original in the HEIC to JPG converter. It runs in your browser, so the photos stay on your device. The default quality of 90 is a good balance for anything you may print or crop later.
If the goal is a small file for email or a size-limited form, drop the quality toward 70 and use a resize preset such as 1920 or 1280 pixels on the longest edge, or open the HEIC Compressor, which starts at quality 60 for exactly that job. Do not be surprised if a high-quality JPG is larger than the HEIC it came from: that is the efficiency gap described above, not a mistake.
Convert copies, keep originals. The HEIC files on your phone or in iCloud remain the best version of each photo, with every bit of HDR and metadata intact.
Frequently asked questions
Is HEIC better quality than JPG at the same file size?
Yes, in most cases. HEVC compression is more efficient, so at an equal file size a HEIC usually holds more detail and fewer artifacts than a JPG. At high quality settings the visible difference becomes very small.
Will converting HEIC to JPG make my photos look worse?
Not noticeably if you convert once from the original at quality 85 to 95. The conversion is technically lossy and flattens HDR to standard brightness, but at normal viewing sizes the JPG looks the same.
Can I edit HEIC photos as easily as JPGs?
On a Mac and in Apple Photos, yes. Many Windows and web-based editors cannot open or save HEIC, so for heavy editing elsewhere convert once to a lossless copy, edit that, and export a JPG at the end.
Should I switch my iPhone camera to JPG?
Only if you regularly upload photos to systems that reject HEIC. Otherwise keep HEIC for the storage savings and convert the few photos that need to go elsewhere.
Does JPG support HDR like HEIC?
Standard JPG does not. Newer gain map extensions can add HDR information to a JPG, but support across apps and screens is uneven, and HEIC to PIC outputs standard 8-bit JPGs.