HEIC = High Efficiency Image Container. That's the whole acronym. But the story behind those four letters explains a quiet shift in how every photo on your phone is stored — and why your team has probably hit a "file type not supported" error at least once this year.
The 30-second version
- Apple made HEIC the default iPhone photo format in 2017 (iOS 11)
- It stores the same photo at roughly half the JPEG file size, with better color depth (10-bit vs 8-bit)
- It's built on the HEVC/H.265 codec — the same tech behind efficient 4K video
- The tradeoff: older software, some websites, and Windows PCs without the codec can't open it
Why this matters at work
This isn't just a consumer quirk. It shows up in real workflows:
- Marketing teams receive HEIC assets from iPhone shoots that their CMS rejects
- HR and admin get HEIC scans of documents that won't attach to legacy systems
- Support teams get HEIC screenshots from customers that their ticketing tools can't preview
The fix is always the same: convert once, at the point of handoff. And for anything sensitive — contracts, IDs, employee documents — the conversion should happen without uploading the file to a third-party server. Browser-local conversion (WebAssembly, no server round-trip) exists precisely for this.
The 3-minute deep dive
Efficiency: HEIC's compression comes from modern inter-frame-style prediction borrowed from video codecs. In practice: a 12MP iPhone photo that would be ~4MB as JPEG is ~2MB as HEIC, and holds more highlight/shadow detail.
Container, not just codec: The "C" in HEIC matters. One HEIC file can hold a burst sequence, depth maps, and the Live Photo video clip — things JPEG simply can't represent.
Where it's headed: Android flagships shoot HEIF/HEIC now. Camera makers are experimenting. JPEG isn't dying tomorrow, but HEIC is the format new pipelines are built around.
What to do today: Keep shooting HEIC (the storage math is real). When compatibility bites, convert — JPG for viewing, PNG for editing, PDF for archiving. I built a free tool for exactly this: full disclosure, I'm the developer of FileOnTap (https://fileontap.com/), and you can read the longer version of this explainer — what HEIC stands for and how to work with it (https://fileontap.com/what-is-heic/) — with a no-upload converter built in.
The licensing footnote (why adoption took a decade)
One reason HEIC was slow to spread: HEVC, the codec inside it, sits in a patent pool. Browser and OS vendors had to navigate licensing, which is why Chrome and Firefox were late to native support and why some open-source tools still can't ship HEVC decoding out of the box. Newer royalty-free alternatives (like AVIF, based on AV1) are now competing for the same role — worth watching, but HEIC has the installed base.
The storage math, made concrete
Take a 20-person team where everyone takes ~10 work photos a week on iPhones:
- JPEG at ~4MB each: 20 × 10 × 4MB = 800MB/week
- HEIC at ~2MB each: 400MB/week
That's ~20GB/year saved in shared drives and backups — before counting the downstream copies in email, Slack, and ticketing systems. It's not a line item anyone notices, but it's real money in storage and real time in uploads. The only cost is the occasional conversion at the compatibility boundary, which is seconds.
The takeaway for your team
Add one line to your asset workflow: "iPhone photos arrive as HEIC — convert at handoff." Thirty seconds of conversion beats a broken upload form, a rejected attachment, or a support ticket. And if the files are sensitive, make sure the conversion never leaves the device.
I'm the developer of FileOnTap (https://fileontap.com/) — a free browser-based file converter where files never leave your device. No uploads, no accounts, no watermarks.
Top comments (0)