You photograph a signed form with your phone, open the site that needs it, choose the file, and get back a red message about an unsupported format. The photograph is fine. The problem is that your phone quietly saved it in a format that a surprising number of websites, forms and desktop programs still refuse to accept.
Converting it takes seconds. Knowing when you need to — and what you lose when you do — takes a couple of minutes, and saves you from converting four hundred photos that never needed it.
Why your phone chose HEIC in the first place
Since iOS 11, iPhones have saved photographs as HEIC by default. HEIC is a container built on the same compression family as modern video codecs, and it is genuinely better than JPEG: roughly half the file size at equivalent visual quality, plus support for transparency, multiple images in one file, and depth data.
That is not a marketing claim, it is the reason Apple switched. A phone with limited storage taking thousands of photographs benefits enormously from halving every file. The trade-off is compatibility, and the trade-off was made on Apple's side of the line.
Why so many things still refuse it
The format is not obscure, but supporting it in software is more work than supporting JPEG, and JPEG has a twenty-year head start.
- Backend libraries. A website's image pipeline is often a decade-old library that knows JPEG, PNG and GIF. HEIC simply is not in the list, and adding it means a dependency change and a redeployment.
- Decoding cost. HEIC decoding is computationally heavier. Sites processing thousands of uploads a day notice.
- Older desktop software. Windows did not decode HEIC natively until recent versions, and then only via an optional extension. Older Photoshop, older Office, and most point-of-sale systems still will not open it.
- Patent and licensing history. The codec family has a more complicated licensing story than JPEG, which discouraged some implementers from adopting it at all.
None of these are your problem to solve, but together they explain why a file that looks perfectly ordinary to you is rejected by a form that looks perfectly modern.
When conversion is genuinely necessary
Four situations come up again and again, and in all of them the receiving end is the constraint rather than the file.
- An upload form rejects it. Government portals, visa applications, university systems, insurance claims and most marketplace backends. Do not fight it; convert.
- You are sending it to someone on Windows or an older Android phone. They may see a blank file or an error, and will not necessarily tell you.
- Old desktop software has to open it. Print shops, accounting packages, and anything that expects a folder of JPEGs.
- A batch has to be consistent. Mixed HEIC and JPEG in one folder breaks sorting, thumbnailing and most scripts.
When you can skip the conversion entirely
Inside the Apple ecosystem you rarely need to convert anything. AirDrop, Messages, Mail and Photos all handle HEIC, and a modern Mac or iPhone will open it natively. Recent Windows versions can too, once the HEIF extension is installed. Chrome, Safari and Firefox all display HEIC in a page in current versions.
The practical test is not "is this file HEIC" but "can the thing that has to receive it open HEIC". If the answer is yes, converting only makes the file larger and loses a little quality for no benefit.
What the conversion actually costs you
HEIC is already a lossy format. Converting a lossy format to another lossy format means the image is decoded and re-encoded, and the second encoding discards a little more — the same generational loss you get from re-saving a JPEG.
In practice it is small at sensible settings. Export to JPEG with quality at 90 or above, and the difference is not visible at normal viewing size. Below 80 it starts to become visible, and the damage concentrates in exactly the places that matter for document photographs: fine print, thin signature lines and the texture of paper.
Two rules follow from this. Convert once and keep the HEIC original — never convert a converted file. And if the photograph needs editing, edit before the conversion, not after.
Metadata, Live Photos and depth data
Conversion is not lossless in the literal sense, and the parts that disappear are not pixels.
- EXIF, including GPS coordinates. Usually carried across, which is worth remembering before you publish a photograph taken at home.
- Live Photos. The video portion is dropped. A JPEG cannot hold it.
- Depth data. Portrait-mode depth maps are lost, which matters if you later want to re-edit the blur.
If any of that matters, keep the original alongside the converted copy rather than replacing it.
Converting a batch without losing the order
Converting forty photographs one at a time is tedious, and the usual mistake is what happens to the filenames afterwards.
Phones name files sequentially — IMG_4821.HEIC, IMG_4822.HEIC — and that numbering is your only reliable ordering. A converter that renames to something generic, or that reorders files by size, destroys it. Check that the output keeps the original names with a new extension, and that it preserves capture timestamps so folder sorting still works.
The image converter runs in the browser and keeps names and metadata intact, which matters if the photographs include anything you would rather not upload: a batch of identity documents, or pictures taken inside a client's premises.
The setting worth changing on your phone
If this is a recurring problem, the fix is at the source rather than per file. On iPhone, open Settings, then Camera, then Formats, and select Most Compatible. New photographs will be written as JPEG directly — no conversion, no generation loss, no compatibility surprises.
The cost is storage: files will be roughly twice the size. If that is acceptable, this removes the problem permanently and is a better answer than converting every file for the next three years.
For one-off cases, converting is faster than changing the setting and changing back. For everything else — particularly documents that have to be submitted once and forgotten — the setting is the fix. And if the converted file still fails to upload, the cause is usually file size rather than format, which is a separate problem with a much quicker fix.