A small UX problem shows up in many web products: the form says “upload a JPG,” but the user is on an iPhone and the photo is HEIC.
HEIC is not the problem by itself. It is efficient, keeps photo quality high, and saves storage. The problem is compatibility at the edge of the workflow: older CMS tools, support desks, school portals, insurance forms, and some Windows workflows still expect JPG.
For product teams, I usually think about this as a conversion boundary:
Keep the original HEIC file when storage and quality matter.
Convert a JPG copy only for the system that requires it.
