Insurance claim portals are picky about file formats in a way that feels unfair when you are already dealing with damage. You take photos on your iPhone, upload them to the claim form, and the portal either rejects them or the adjuster replies that they cannot open the attachments. The usual cause is not a bad photo — it is HEIC.
iPhones have saved photos as HEIC by default since iOS 11. HEIC stores the same photo in roughly half the file size of a JPG, which is great for storage and terrible for compatibility: many claim portals, older Windows viewers, and some email systems still expect JPG or PNG, not HEIC.
The fix is to convert a copy before you upload, not to re-shoot anything:
- Keep your original HEIC photos untouched. They are your best-quality evidence, and you may need them again if the insurer asks for a re-upload.
- Convert copies to JPG for the claim portal. JPG opens everywhere, and for claim documentation the small quality difference from HEIC is irrelevant — what matters is that the adjuster can actually see the damage clearly.
- Check the converted files before you submit. Open each JPG once to confirm it shows the right photo, then upload the JPGs and keep the HEIC originals filed separately.
You do not need to install anything or upload your photos to a server to do this. I built FileOnTap so you can convert HEIC to JPG for insurance claims entirely in your browser: drop in the HEIC photos, download JPGs, nothing is uploaded, and no account is needed. That matters here more than usual — claim photos show your home, your car, and your belongings, and they should not pass through a stranger's server just to change format.
One caution: do not just rename a .heic file to .jpg. Renaming changes the label, not the contents, so the portal still cannot read it — and the error message becomes harder to understand. Convert a real copy, keep the original, and submit the JPG.
Disclosure: I'm the developer of FileOnTap. The "keep the original, convert a copy for the portal" order is the real takeaway whichever tool you use.
Top comments (0)