Initializing... drag & drop files here
Supports: HEIC
HEIC and HEIF are sibling formats built on the same ISO/IEC 23008-12 specification. HEIF is the broader container standard defined by MPEG; HEIC is Apple's specific brand of HEIF that always pairs the container with HEVC (H.265) compression. Apple has shipped .heic as the default photo extension on iPhone since iOS 11 in 2017. Some non-Apple software and Linux image libraries recognize the generic .heif extension when they refuse the .heic one, even though the underlying bytes are nearly identical.
.heif (the standardized extension) but block .heic because they associate it with Apple-only content. Renaming the container resolves the rejection..heif extension is the spec-defined one and is more likely to be recognized by future tools written against the ISO/IEC standard rather than Apple's brand..heif routes through the generic decoder path more reliably than .heic.libheif, GIMP's HEIF plugin, and Krita all accept either extension, but build configs and Docker images sometimes only register the .heif MIME type by default.| Property | HEIC | HEIF |
|---|---|---|
| Standard | Apple's brand of HEIF | ISO/IEC 23008-12 (MPEG-H Part 12) |
| Codec inside | Always HEVC (H.265) | HEVC, AV1, AVC/H.264, JPEG, JPEG 2000 |
| File extension | .heic, .heics (sequences) |
.heif, .heifs (sequences) |
| MIME type | image/heic |
image/heif |
| Default on iPhone | Yes, since iOS 11 (2017) | No — Apple writes .heic |
| Live Photos / depth | Stored as auxiliary image items | Same container supports them |
| 10-bit color & wide gamut | Yes | Yes |
| Patent royalties | HEVC has licensing fees | Depends on codec inside |
The image data is identical when the HEIC source is already HEVC — converting changes the container brand, MIME type, and file extension, not the pixels (unless you also re-encode at a different quality preset).
| Preset | Typical output vs original | Best when |
|---|---|---|
| Highest | ~95-100% | You want a perceptually lossless re-save |
| Very High (default) | ~75-85% | Everyday photos; recommended |
| High | ~55-65% | Bulk archiving where small loss is fine |
| Medium | ~35-45% | Sharing previews, gallery thumbnails |
| Low | ~15-25% | Maximum shrinkage, visible blocking acceptable |
| Specific file size | Auto-scales | Hard cap (form upload, attachment limit) |
If you need a more universally compatible format, see HEIC to JPG or HEIC to PNG. For modern web delivery, HEIC to AVIF gives even smaller files using the royalty-free AV1 codec. Going the other direction, use HEIF to HEIC. To shrink files without changing the format, use Compress HEIC.
In practice on Apple devices, yes — an iPhone .heic file is HEVC-coded image data inside a HEIF (ISO/IEC 23008-12) container. The HEIF spec, though, is broader: HEIF can also carry AV1 payloads (then called AVIF with a .avif extension), AVC/H.264 (rare, .avci extension), or even JPEG payloads. So every HEIC is a HEIF, but not every HEIF is a HEIC. Converting HEIC to HEIF rewrites the container brand and extension while keeping the HEVC image data intact.
Not if you pick Highest or Very High. When the underlying codec stays HEVC, the conversion is effectively a container remux — same pixels, different wrapper. Picking a lower quality preset re-encodes the image and does introduce loss; pick Highest if you want a strictly faithful round-trip.
Many tools detect file type by extension before they sniff the actual bytes. If their accept-list contains image/heif but not image/heic, they bounce the upload. This happens with CMS uploaders, some scientific imaging tools, and older HEIF library bindings. Renaming or converting to the standardized .heif extension usually clears the gate.
The HEIF container supports auxiliary image items (depth, alpha, thumbnails) and image sequences. XConvert's converter outputs the primary still image — the Live Photo motion clip and depth aux items are not carried through to the .heif output. If you need those preserved, share via AirDrop or iCloud Link, both of which keep the original .heic intact.
Windows 10 and 11 need the free Microsoft "HEIF Image Extensions" from the Microsoft Store; once installed, both .heif and .heic open in Photos and File Explorer thumbnails work. Android 9 (Pie) and later read HEIF natively in the system gallery. Linux users need a build of libheif plus a viewer that links it (GIMP 2.10+, Krita, Geeqie all work). If a tool still refuses HEIF, converting to JPG is the universal fallback — see HEIC to JPG.
Yes. HEIF carries EXIF and XMP metadata in standardized item references; the conversion preserves date taken, GPS coordinates, camera model, lens, and exposure settings by default. If you want to strip metadata for privacy before sharing, convert to JPG and use that pipeline's metadata-removal option.
For the web, AVIF is the better target. AVIF uses the same HEIF-style container but with AV1 codec, which is royalty-free and produces files roughly 20-30% smaller than HEIC at equivalent quality. Browser support for AVIF is now broad: Chrome 85+, Firefox 93+, Safari 16.4+, and Edge 121+. HEIF/HEIC has essentially no native browser support outside Safari. Use HEIC to AVIF for web embedding; use HEIC to HEIF only when you need a HEIF-compliant file for a specific desktop tool.
.heif is a single still image; .heifs is a sequence (multiple frames, like a burst or short animation, all in one container). Apple uses .heic and .heics analogously. Most consumer use cases are single-image, so you'll see .heif almost exclusively. XConvert outputs .heif for single images.
Yes. Upload as many HEIC files as you want — there's no quantity cap. The same quality and resolution settings apply to every file in the batch, and outputs are available as individual downloads or a single ZIP at the end.