When an Upload Form Accepts JPG but the Phone Gives You HEIC
The article discusses a common issue where upload forms request JPG files, but users on iPhones often have photos in HEIC format. While HEIC is efficient and maintains photo quality, many older systems still require JPG compatibility. The author suggests that product teams should either accept HEIC files or provide a straightforward method for users to convert their images without compromising privacy.
- ▪Many web products request JPG uploads, but iPhone users often have HEIC photos.
- ▪HEIC format is efficient and maintains high photo quality, but compatibility issues arise with older systems.
- ▪Product teams should either accept HEIC files directly or offer a clear conversion path for users.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3965637) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Ding Posted on Jun 3 When an Upload Form Accepts JPG but the Phone Gives You HEIC #tools 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.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
