You attach a photo to a form and it tells you the file type is not supported, without saying which types are. Or you email a picture to somebody and they see a blank icon. The photo looked completely normal on the phone that took it, which is what makes this so hard to diagnose from the sending end.
The file is a .HEIC, and it has been the iPhone camera default since iOS 11 in 2017. On its technical merits it beats JPEG comfortably. That is no help at all when the file will not open, and nothing goes wrong until the photo leaves Apple's world, so the person who took it usually has no idea anything is wrong.
There are three separate things worth understanding, and they solve different problems: what the format is, how to stop your phone making them, and how to rescue the ones you already have.
What a .heic file actually contains
Two acronyms get used as if they were one thing. HEIF is the container - a box that holds image data plus everything that goes with it, in the same way an MP4 holds video, audio and subtitles together. HEVC, also known as H.265, is the codec that compresses the picture itself. A .heic file is normally HEVC-encoded image data sitting inside a HEIF container. Apple made that combination the camera default in iOS 11.
The motivation was space. JPEG was standardised in the early 1990s and works on eight by eight blocks of pixels. HEVC arrived roughly two decades later, designed for video, and can predict one region of an image from another region of the same image before it encodes anything at all. The practical result is around half the file size at comparable quality, which is a large saving when a phone holds thousands of photos. How large depends on the picture: a plain wall compresses beautifully either way, fine gravel does not.
The container also carries things JPEG has no way to express, which matters later when you convert. A single .heic can hold ten bits per colour channel instead of JPEG's eight, which is why skies band less. It can carry transparency. It can store the depth map from Portrait mode that lets the phone re-adjust background blur after the fact, and it can hold a whole burst of frames as one file rather than forty.
Where it opens, and where it does not
A format is only as portable as its decoder, and the HEVC decoder is genuinely not everywhere. Underneath the patchiness sits patent licensing: HEVC is covered by patents administered through more than one pool, which has made browser vendors and open-source projects cautious about shipping a decoder at all. JPEG's patents expired a long time ago, which is the real reason it remains the format that everything understands.
| Where the file ends up | Does a .heic open? | What is going on |
|---|---|---|
| iPhone, iPad, recent Mac | Yes | Decoding is built into the operating system and has been since 2017. |
| Windows 10 and 11 | Only with codecs installed | HEIF and HEVC support arrives as separate add-ons from the Microsoft Store rather than being present out of the box. |
| Recent Android | Usually | Android gained system-level HEIF decoding around 2018, but individual apps and older handsets often still cannot. |
| Safari | Yes | It borrows the decoder the operating system already has. |
| Chrome, Firefox, Edge | Historically no | No built-in HEIC decoder, so a web page cannot simply put one in an image tag and hope. |
| Upload forms | Usually rejected | Most check the file extension against a short allowlist, typically jpg, jpeg, png and pdf. |
| Photo editors and office software | Mixed | Recent versions of the major editors handle it. Older releases, print kiosks and in-house corporate tools frequently do not. |
| Anything reading JPEG only | No | Renaming the file to .jpg does not help. The extension is a label, not a description of the bytes. |
Renaming a .heic to .jpg is the most common piece of bad advice on this subject and it never works. A JPEG decoder reads the first few bytes, finds HEVC data in an ISO base media container, recognises nothing, and stops.
Why upload forms are the strictest of all
Forms fail earlier and more bluntly than software does. A typical file input checks the extension against a list before anything examines the image, so the rejection happens without your photo ever being decoded. The error message is generic because at that point the site genuinely does not know what you sent.
Even forms that accept the upload can fail afterwards. Plenty of sites run on server-side image libraries that were built without HEIF support, so the file uploads successfully and then the thumbnail comes out blank, or the processing step errors out some time later. Government portals, university admissions systems and job applications are the usual offenders, and they are exactly the situations where a silent failure costs you the most.
If a form rejects your photo and the message only says invalid file type, look at the extension before you look at anything else. That single check explains the large majority of these cases.
The setting that stops the problem at the source
Converting files one at a time treats the symptom. If you keep hitting this, change what the camera writes. On the phone, open Settings, then Camera, then Formats. High Efficiency writes HEIC stills and HEVC video. Most Compatible writes JPEG and H.264 instead.
Two things worth knowing before you switch. It only affects photos taken from that moment onwards, so it does nothing for the thousands already in your camera roll. And it costs storage: expect roughly double the space per photo, which is the whole saving you were getting handed back. A couple of high frame rate video modes require High Efficiency, and the phone will tell you if you try to use them.
There is a second setting that causes most of the arguments about this, because it changes what happens without changing what the camera does. Settings, then Photos, then Transfer to Mac or PC, offers Automatic or Keep Originals. Automatic converts HEIC to JPEG when you connect the phone to a computer. Keep Originals hands over the file exactly as stored. Plenty of people are on Keep Originals without ever having chosen it, which is why the same phone can seem to produce openable photos one week and not the next.
How you send it decides what arrives
This is the part that makes the problem feel random. The format that reaches the other end depends on the route the photo took off the phone, and none of the routes announce what they did.
- AirDrop to another Apple device generally preserves the original HEIC, because it assumes the receiving end can read it.
- A USB cable to a computer transfers whatever Transfer to Mac or PC is set to - the original HEIC on Keep Originals, a converted JPEG on Automatic.
- Mail and Messages attachments are frequently converted to JPEG on the way out, which is why some of your photos seem fine and others do not.
- Most social and chat apps re-encode everything they receive anyway, usually to JPEG and usually smaller than you sent.
- Uploading through Safari on the phone often hands the site a JPEG, though this varies and is not something you can rely on.
Converting the files you already have
For photos already taken, conversion is the only route, and it is worth being honest about how it works in a browser rather than overselling it. Safari can decode HEIC because macOS and iOS already have the decoder and lend it to the browser. Chrome and Firefox historically do not ship one, for the licensing reasons described earlier.
So a browser-based converter has to bring its own decoder. Libraries such as libheif get compiled to WebAssembly, downloaded as part of the page and run on your own processor inside the tab. That means a megabyte or two of code arrives before anything can happen, and decoding a twelve megapixel HEVC still takes noticeably longer than opening a JPEG of the same picture. The compensation is that the file never leaves your machine, which for photographs of passports and bank statements is the entire point.
It also means these converters are not uniformly reliable, and anyone claiming otherwise is not being straight with you. Ten-bit files, depth maps, image sequences and newer encoding profiles all trip WebAssembly decoders, and Apple ships new capture modes faster than the decoders catch up. If one photo in thirty fails while the rest work, that is normally the reason. Open the file on a Mac and export from there, or switch the phone to Most Compatible and retake it.
Browser support for decoding HEIC is inconsistent and will always lag behind what Apple's cameras produce. If your photos are heading for a Windows machine, a print shop or an upload form, the dependable fix is to set Formats to Most Compatible before you take them. Converting afterwards is the fallback, not the plan.
What conversion costs you
Both formats are lossy, so converting is a transcode rather than a repackaging. The file is decoded back to pixels and then re-encoded by a different lossy codec that discards a slightly different set of details. That is generation loss, and it is real, though at a sensible quality setting it is not something anyone notices in a single pass. You also drop from ten bits per channel to eight, which shows up as faint banding across a clear sky more often than anywhere else.
The file also gets bigger, which surprises people who expect conversion to be a tidying-up step. A 2 MB HEIC commonly lands somewhere around 3 to 4 MB as a high-quality JPEG, because you are asking a thirty-year-old codec to carry the same picture. If the destination has a size limit, that is a second problem to solve after the format one.
Live Photos lose the most. A Live Photo is not one file but a still image paired with a short video clip, shown as a single item in the Photos app. Convert it and you keep the key frame; the motion and its audio do not travel. For a document scan or a receipt that is exactly what you wanted. For a picture of a child mid-run, the frame the phone picked may not be the moment you had in mind.
None of this should stop you converting. A file that will not open has a quality of zero to the person who needs it. Keep the HEIC as your original, export a fresh JPEG from it each time you need one, and never convert a conversion.
Common questions
How do I open a HEIC file on Windows?
Recent Windows versions can, provided the HEIF and HEVC extensions from the Microsoft Store are installed, and on some machines they already are. If yours will not open the file, converting it to JPEG is usually quicker than working out which extension is missing. Some third-party viewers bundle their own decoder and open HEIC files without any of that.
Why will this website not accept my iPhone photo?
Almost always because the file ends in .heic and the form only accepts jpg, jpeg, png or pdf. The form is checking the extension rather than looking at the image, so the rejection happens before anything examines your photo. Convert it to JPEG and the same picture uploads without complaint.
How do I make my iPhone take JPGs instead?
Settings, then Camera, then Formats, then Most Compatible. From that point the camera writes JPEG stills and H.264 video. It does not change photos you have already taken, and it roughly doubles the storage each new photo uses. Also check Settings, then Photos, then Transfer to Mac or PC, and set it to Automatic if you want existing HEIC files converted when you plug the phone in.
Does converting HEIC to JPEG lose quality?
A little. Both formats are lossy, so converting means decoding and re-encoding, and you drop from ten bits per colour channel to eight. At a good quality setting the difference is not visible in a single pass. Keep the HEIC as the original and export a fresh JPEG from it whenever you need one, rather than converting an earlier conversion.
Why did the converter fail on one photo but work on the rest?
Browser-based converters use a WebAssembly decoder rather than the one built into your operating system, and those decoders do not handle every variant. Ten-bit files, Portrait depth maps, burst sequences and newer capture modes are the usual causes. Opening that photo on a Mac and exporting as JPEG, or retaking it with Formats set to Most Compatible, will get you past it.
Tools for this
Convert HEIC to JPEG or PNG in the browser, with the file staying on your own machine.
Bring the JPEG back down after conversion, since a converted file is usually larger than the HEIC was.
Hit a specific kilobyte limit when the form that rejected your HEIC also has a size cap.