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.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/ding_00aea4cb8281a3d69ef3/when-an-upload-form-accepts-jpg-but-the-phone-gives-you-heic-2hcc |
| Publication time | Wed, 03 Jun 2026 04:22:09 +0000 |
| Retrieval time | 2026-06-03T04:41:55.008Z |
| Last seen | 2026-06-03T04:41:55.008Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ADFS74GbLyXS |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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)
