If you own an iPhone, your camera has probably been saving HEIC files for years without telling you. They are smaller and technically better than JPG, and they also cause more support tickets, failed uploads and confused relatives than any other photo format in circulation. This is a straight comparison of the two, and a practical answer to what you should actually keep on your phone and what you should send to other people.
The two formats in brief
JPG, the 1992 survivor
JPEG was published as an international standard in 1992 and has been the default photo format of the internet ever since. It works by throwing away detail the human eye is bad at noticing, which is why the file is small and why saving repeatedly degrades the image. The format is simple, ancient, and supported by essentially every camera, phone, browser, printer and piece of software made in the last three decades.
Note that JPG and JPEG are the same thing. The three-letter extension is a leftover from old Windows filename limits.
HEIC, the efficient newcomer
HEIC is not really a format on its own. It is a HEIF container (ISO/IEC 23008-12, finalised in 2015) holding image data compressed with HEVC, also known as H.265, the video codec. Apple made it the camera default with iOS 11 in September 2017, on iPhone 7 and later. Since then most iPhones, many iPads, and a growing number of Android flagships have shot HEIC out of the box.
Because HEIC borrows a video codec, it inherits a decade of compression research that JPEG never had access to. Because it borrows a video codec, it also inherited that codec’s patent licensing problems, which is the main reason it never replaced JPG on the open web.
Compression: the headline difference
The rule of thumb everyone quotes is that HEIC is about half the size of JPG at comparable visual quality. That is roughly right for typical phone photos, and it is the single strongest argument for the format.
The savings are not uniform. HEIC does best on smooth content: skies, skin, out-of-focus backgrounds, flat walls. It does less well on dense fine detail like foliage or textured fabric, where the gap narrows. A photo of a forest might only shrink by a third, while a portrait against a plain wall can be well under half.
Treat “half the size” as a typical outcome, not a guarantee. If you want to see the real number for your own pictures, convert a few shots with HEIC to JPG and compare the before and after sizes it reports for each file.
The storage maths on a phone
Rough figures for a 12-megapixel phone photo: somewhere around 1.5 to 3 MB as HEIC, and roughly double that as a JPG at similar quality. Actual numbers vary a lot with scene complexity.
Scale that up. A library of 5,000 photos might sit at around 10 GB in HEIC and around 20 GB as JPG. On a 128 GB phone that difference is the gap between comfortable and constantly deleting things. It also affects how much iCloud or Google Photos storage you pay for every month.
That is the honest case for leaving your camera on High Efficiency.
Quality ceiling: colour depth and gamut
Baseline JPG, the version every device actually reads, stores 8 bits per colour channel. That gives 256 levels per channel, which is enough for most photos but not for a smooth sunset gradient, where you get visible banding. JPG is also usually tagged sRGB, so wide colour gamut information from a modern camera sensor gets squeezed down or clipped.
HEIC can store 10 bits per channel, giving 1024 levels, and carries wide gamut colour profiles like Display P3 properly. Combined with HDR gain information, that is why a photo taken on a recent iPhone looks noticeably richer on the phone than the same shot emailed to yourself as a JPG. The JPG is not broken. It simply cannot hold what the original held.
If you are archiving photos you may want to edit heavily later, the higher bit depth is a real advantage. If you are posting to a website or sending to a print shop, it is irrelevant, because the destination will flatten everything to 8-bit sRGB anyway.
What else lives inside a HEIC
The container is more capable than JPG in ways that go beyond the pixels:
- Alpha transparency. HEIF supports an alpha channel. JPG has never supported transparency at all, which is why cutouts and logos end up as PNG.
- Depth maps. Portrait mode stores a depth map as an auxiliary image alongside the main photo, so the blur can be re-edited after the fact.
- Image sequences. The spec can hold multiple related images in one file, which is how bursts and animated content are represented.
- Live Photos. On an iPhone, a Live Photo is a HEIC still paired with a short companion video file. Open the HEIC on its own and you get the still frame only.
- Thumbnails. HEIF embeds reduced-size previews so a file list renders without decoding every full image.
One thing that is not in the file: your edit history. When you crop or adjust in Apple Photos, the app keeps the untouched original plus a separate adjustment record, exported as an .AAE sidecar rather than stored inside the HEIC. Converting a copy in a browser cannot touch it.
When you convert to JPG, the container features above go away. You keep the picture and lose the extras. That is not always bad, and it is often the point, but it is worth knowing before you delete the originals.
HEIC vs JPG at a glance
| Attribute | JPG | HEIC |
|---|---|---|
| Standardised | 1992 | 2015 (HEIF container) |
| Compression | JPEG DCT | HEVC / H.265 |
| Typical file size | Baseline | Around half |
| Colour depth | 8-bit per channel | 8-bit or 10-bit |
| Wide gamut and HDR | Limited in practice | Yes |
| Transparency | No | Yes |
| Depth maps, sequences | No | Yes |
| Opens on Windows | Always | Needs a codec installed |
| Opens on Android | Always | Android 10 and later, mostly |
| Displays in a browser img tag | Every browser | Safari only |
| Accepted by upload forms | Nearly always | Frequently rejected |
| Patent licensing | Effectively unencumbered | HEVC pools apply |
The compatibility reality check
On Apple hardware, HEIC is invisible in the best way. Photos, Preview, Messages, Mail and Finder all handle it, and you will rarely see the extension.
Step outside that fence and things get uneven.
Windows. Windows 10 and 11 can display HEIC once the HEIF Image Extensions are installed, and on many machines that also depends on the HEVC Video Extensions, which cost about a dollar in the Microsoft Store unless your PC maker preinstalled them. Whether a given laptop opens a HEIC comes down to who built it. Our guide on how to open HEIC files on Windows walks through the options.
Android. Android 10 and later can read HEIF at the platform level, so modern phones generally cope. Older devices and plenty of individual apps still do not.
The web. No mainstream browser except Safari will render a .heic in an <img> tag, so you cannot use HEIC on a website. If you are choosing a format for a site, the real contenders are WebP, AVIF and JPG, which we cover in the best image format for a website in 2026 and WebP vs PNG vs JPG.
Upload forms, printers and older editors. Job portals, insurance claim systems, school platforms, photo kiosks and legacy versions of Photoshop, Lightroom and GIMP all tend to want JPG or PNG. This is where most people first discover HEIC exists, usually at the worst moment.
Why HEIC never took over
JPEG’s patents expired long ago, which is exactly why it is everywhere. Nobody has to negotiate anything to decode a JPG.
HEVC is the opposite. Its patents are spread across several licensing pools plus rights holders who joined none of them, with no single place to clear everything at once. For a browser vendor shipping to billions of devices, that uncertainty was reason enough to skip native HEIC support entirely, and for most of the last decade they did. The technology was ready years ago. The paperwork was not.
That is also why the open web went to WebP and then AVIF instead. Both are royalty-free by design, and both solve the same problem HEIC solves.
What actually happens when you share a HEIC
iOS tries to protect you from the compatibility problem, with mixed results.
- AirDrop to another Apple device keeps the HEIC intact, which is what you want.
- Mail usually converts to JPG before sending.
- Messages keeps the HEIC between Apple devices, which is why people end up saving
.heicfiles out of threads. It converts only when the recipient drops to SMS/MMS. - Uploading through Safari often hands the site a converted JPG rather than the original.
- Copying to a PC over USB depends on Settings, Photos, Transfer to Mac or PC. Set to Automatic it converts, set to Keep Originals it does not.
- Third-party apps do whatever their developer decided, which is why you occasionally end up with a
.heicin a Google Drive folder that nobody on a Windows machine can open.
So most of the time sharing just works. The failures are the memorable ones, and they cluster around drag-and-drop, cloud folders and anything that bypasses the share sheet.
So which should you use?
Keep shooting HEIC. The storage saving is genuine, the quality is better, and Apple’s automatic conversion handles the common sharing paths. Switching your camera to Most Compatible doubles your storage use to solve a problem you hit occasionally.
Convert to JPG when a file is leaving your ecosystem. Job applications, printers, client deliveries, marketplace listings, insurance claims, anything going to a relative on a Windows laptop. Convert the copy, keep the original.
Convert for long-term archiving too, if the archive matters. JPG will still open in 2050. A format tied to a patented video codec is a less certain bet, and a copy costs you nothing but disk space.
The practical workflow is straightforward. Run the files you need through HEIC to JPG, or HEIC to PNG if you need a lossless copy or transparency. If the result is too big for an email or an upload limit, follow it with the image compressor or shrink the dimensions with the resizer. Sending a set of photos as a single document is easier with image to PDF than as fifteen attachments.
All of that runs inside your browser on Tinyvert. The decoder is WebAssembly and the re-encoding uses your browser’s own Canvas API, so your photos are never uploaded, never queued on a server, and never stored anywhere we could leak them. That matters more than usual with camera roll photos, which tend to include things you would not hand to a stranger. One side effect worth repeating: metadata is stripped during conversion, so GPS coordinates and capture dates do not travel with the JPG. Good for privacy, inconvenient if you were relying on those tags, so keep the originals.
The free tier handles 5 files per batch, as often as you like. If you are converting a whole camera roll, Pro is a one-time US$9 upgrade that removes the batch limit. For everything else, the answer to HEIC versus JPG is simply: both, for different jobs.