Convert Always

format

HEIC

HEIC is Apple's default photo format, storing HEVC-compressed images at half JPEG's size.

Also known as HEIF, High Efficiency Image Container.

Convert a file now

What is a HEIC file?

A container based on the HEIF standard holding HEVC-compressed images, used by default on iPhone since iOS 11.

Technical characteristics

Representation
binary
Compression
HEVC
Lossy
Yes
Transparency
Yes
Animation
Yes
Open specification
Yes

History and origin

Introduced
2015
Organisation
MPEG

Compatibility

  • Windowsplugin
  • macOSfull
  • Linuxpartial
  • Androidfull
  • iOSfull

Browsers: Safari only.

Advantages of HEIC

  • About half the size of JPEG at similar quality
  • Stores depth maps, bursts and Live Photos

Limitations to know about

  • Patent licensing limits adoption
  • Poor support outside Apple platforms

When to use HEIC

  • iPhone photography
  • Storage-constrained photo libraries

Convert HEIC files

Recommended next step

  • Convert to JPEG

    JPEG is the reliable choice when a HEIC photo has to open on Windows, in older editors or in a web form.

    Trade-offs: File size roughly doubles; Depth maps and Live Photo data are lost.

    Learn about JPEG

HEIC scores

Deterministic scores calculated from the structured facts above. Identical facts always produce identical scores.

Overall score

61/100

  • Performance score

    100
    • smaller payloads mean less I/O and faster first paint
    • it compresses lossily, which produces much smaller files than lossless coding

    Confidence 54% · evidence coverage 100%

  • Archiving score

    88
    • the specification is public, so a decoder can always be rebuilt
    • the specification is published openly
    • it is actively maintained and current
    • it carries EXIF-style embedded metadata

    Confidence 52% · evidence coverage 100%

  • Streaming score

    87
    • it compresses lossily, which produces much smaller files than lossless coding
    • smaller payloads mean less I/O and faster first paint
    • native browser support is incomplete or undocumented

    Confidence 58% · evidence coverage 63%

  • Openness score

    87
    • the specification is published openly
    • an openly specified format can be implemented without a licence negotiation

    Confidence 42% · evidence coverage 100%

  • Longevity score

    87
    • it is actively maintained and current
    • the specification is published openly
    • the specification is public, so a decoder can always be rebuilt
    • it does not satisfy: mainstream applications ship support for it

    Confidence 56% · evidence coverage 100%

  • Web score

    71
    • it compresses lossily, which produces much smaller files than lossless coding
    • smaller payloads mean less I/O and faster first paint
    • it supports transparency
    • the specification is published openly
    • native browser support is incomplete or undocumented

    Confidence 58% · evidence coverage 100%

  • AI score

    66
    • the specification is published openly
    • smaller payloads mean less I/O and faster first paint
    • only a narrow set of applications handles it
    • lossy artefacts add noise that models can learn by mistake

    Confidence 42% · evidence coverage 100%

  • Compatibility score

    44
    • an open specification means cloud SDKs can implement it without licensing friction
    • native browser support is incomplete or undocumented
    • at least one mainstream platform needs extra software

    Confidence 65% · evidence coverage 100%

  • Photography score

    39
    • it carries EXIF-style embedded metadata
    • it compresses lossily, which produces much smaller files than lossless coding
    • it discards detail during encoding, and every re-save compounds the loss
    • each edit-and-save cycle compounds compression damage

    Confidence 33% · evidence coverage 100%

  • Editing score

    21
    • it carries EXIF-style embedded metadata
    • each edit-and-save cycle compounds compression damage
    • it discards detail during encoding, and every re-save compounds the loss

    Confidence 35% · evidence coverage 100%

  • Printing score

    17
    • it carries EXIF-style embedded metadata
    • lossy artefacts become visible when the image is enlarged for print
    • it discards detail during encoding, and every re-save compounds the loss

    Confidence 34% · evidence coverage 100%

What HEIC is recommended for

Every conclusion below is derived from the structured facts on this page — nothing is written by hand.

  • Compression efficiency100/100

    • Because it compresses lossily, which produces much smaller files than lossless coding.
    • Because it uses a recent codec generation, which encodes more efficiently than older designs.
    • Because it defines a documented compression scheme.

  • Transparency100/100

    • Because it supports transparency.
    • Because it stores a full alpha channel, allowing soft edges and partial opacity.

  • Animation100/100

    • Because it stores multiple frames, so animation is supported natively.

  • Cloud compatibility100/100

    • Because an open specification means cloud SDKs can implement it without licensing friction.
    • Because it converts into many other formats, which suits automated pipelines.

  • Open standards100/100

    • Because the specification is published openly.

  • Decode performance100/100

    • Because smaller payloads mean less I/O and faster first paint.
    • Because mature formats benefit from hardware and SIMD-optimised decoders.

  • Future-proofing100/100

    • Because it is actively maintained and current.
    • Because open specifications outlive the companies that create them.
    • Because nothing in the graph supersedes it yet.

  • Long-term archiving76/100

    • Because the specification is public, so a decoder can always be rebuilt.
    • Because it is a current, actively maintained format.
    • Because it has a decade or more of proven, stable implementations.

What HEIC is not recommended for

  • Printing suitability0/100

    • Because lossy artefacts become visible when the image is enlarged for print.
    • Because it does not satisfy: it is a page-description format built around fixed layout.

  • Professional editing0/100

    • Because each edit-and-save cycle compounds compression damage.
    • Because it does not satisfy: professional applications read and write it.

  • Browser compatibility33/100

    • Because native browser support is incomplete or undocumented.

  • Operating system compatibility33/100

    • Because at least one mainstream platform needs extra software.

  • Software compatibility33/100

    • Because only a narrow set of applications handles it.

Related to HEIC

File extensions

Created by

Compared with

Frequently asked questions

Why won't my HEIC photos open on Windows?

Windows needs the HEIF Image Extensions from the Microsoft Store. Converting to JPEG avoids the issue entirely.

Data quality

Every claim on this page is classified as a verified fact, a derived fact or an assumption.

Overall confidence
78%
Verification status
verified
Last reviewed
2026-08-03
Verified facts
3

3 classified claims backed by 1 source.

  • Convert Always editorial review — Convert Always

Sources and review status

Review status: verified · confidence 80%

Last reviewed 2026-08-03 (revision 1).

  • Convert Always editorial review — Convert Always