Skip to content
Server-sideDeleted in 30 minutes

Convert HEIC to GIF

A phone camera can produce a perfectly ordinary-looking photo inside a HEIC file that an old forum, badge system, or desktop application cannot read. GIF is a compatibility escape hatch, but it is a severe one for photographs: the primary camera image is flattened into a single frame and its colors are fitted to GIF's 256-color limit. Use it when the receiving system leaves no better option.

Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.

Add to Chrome — free
HEICGIF

Drop your HEIC file here, or click to browse

Up to 50 MB. Deleted automatically after 30 minutes.

What it does

  • Camera HEIC decoded for software that only accepts GIF
  • Extra camera layers represented by the primary flat image
  • One static GIF frame at up to 256 colors
  • No watermark and no sign-up

How to use HEIC to GIF

  1. 1

    Add the camera HEIC

    Upload the still photo from an iPhone or another HEIF camera workflow. Keep the original because a GIF cannot carry the full HEIC package, including depth data, gain maps, or motion associated with a Live Photo.

  2. 2

    Flatten and convert

    The server decodes the HEVC image and writes the displayed primary image as a single GIF frame. GIF's indexed palette then reduces the available colors; this is why a photograph can look posterised even when the source looked clean.

  3. 3

    Use the GIF only at its destination

    Test it in the legacy application that rejected HEIC. For a modern website, message, or photo library, prefer JPG or WebP when available because they keep photographic gradients much better at a reasonable size.

How it works

The server opens the HEIC container, decodes its primary HEVC image, and passes the result through a GIF encoder. The encoder builds an indexed palette and maps the image's full-color pixels into that smaller set. The file is therefore genuinely a GIF, rather than a HEIC renamed with a friendlier suffix.

HEIC is especially easy to underestimate because the phone presents it as a single photo. Internally, a camera file can carry the main image alongside depth, HDR gain, thumbnail, burst, or Live Photo information. A GIF is a flat raster format, so the conversion keeps what a viewer sees in the primary frame and discards the structures that need a HEIF-aware photo application.

Why camera compatibility is the reason

The normal destination for a phone photograph should be JPG or WebP. Both are more appropriate for sharing and web display, and both preserve gradients far better than an indexed GIF. The case for GIF is narrower: an older forum, kiosk, form, or image reader has an extension check or decoder that accepts GIF and refuses HEIC.

That distinction matters because a successful conversion does not prove GIF was a good image choice. It only proves that the restrictive endpoint can receive a file. If you control the endpoint, update its image support instead. If you do not, make the GIF from a copy and leave the camera original untouched.

The static and color limits

This route writes one frame, even though some phone workflows involve motion or multiple related images. GIF can animate in general, but a still HEIC input does not provide a sequence for this page to preserve, and camera Live Photo motion is a separate asset. Do not promise recipients a moving image because the result ends in .gif.

The 256-color ceiling is also decisive. Logos and small illustrations may fit the palette comfortably. A high-resolution photograph usually does not, so inspect a face, a smooth wall, and a bright sky after conversion. A smaller canvas can make a GIF less expensive, but resizing does not remove the palette limitation.

Preserve the source package

The GIF is a compatibility copy. It is useful for the one old reader that needs it, but it cannot carry the camera's depth controls, HDR presentation data, or original color distinctions. Keep the HEIC, and export a JPG or WebP from that original when the next destination supports a better still-image format.

Examples

An iPhone photo for an old forum uploader

IMG_7420.heic — 4032x3024, 2.7 MB, camera photograph
IMG_7420.gif — 4032x3024, 3.1 MB, one frame, 256-color palette

The forum now recognizes the extension, but the full camera resolution makes a very large GIF and the sky may show visible banding. Resize first if the forum permits a smaller image, and choose JPG instead whenever it accepts JPG; the purpose here is compatibility with a particularly restrictive destination.

A Portrait-mode image sent to a badge system

IMG_1198.heic — 1200x1200, Portrait mode with depth metadata, 680 KB
IMG_1198.gif — 1200x1200, flat still image, 256-color palette

The visible portrait is converted, but the depth map that allowed later blur changes is not part of the GIF. Any Live Photo motion, HDR gain information, or alternate camera layer is likewise outside the output. The GIF is a display derivative, not a replacement for the photo-library original.

Frequently asked questions

What does flattening a camera HEIC mean here?

It means the output contains the primary rendered image only, rather than the collection of related data a camera can place in HEIC. Portrait depth maps, HDR gain maps, thumbnails, and Live Photo motion have no equivalent in a single GIF frame. The visible photograph is retained as pixels, but those editable or alternate layers cannot be recovered from the GIF later.

Why does my phone photo look worse as a GIF?

HEIC can represent many more colors and compress a photograph efficiently, while GIF uses indexed color with at most 256 entries per frame. A palette reduction must approximate skin, sky, foliage, and shadows, which can produce banding or dithering. This is an inherent GIF limitation, not a camera defect or a sign that the HEIC was decoded at the wrong resolution.

Will the HEIC become an animated GIF?

No. Camera HEIC conversion here produces one static GIF frame. A Live Photo is not an animated HEIC image that can be carried into GIF; it combines a still with a separate motion asset and GIF output has no place for that camera package in this route. Export the motion separately if the moving moment is important, and keep the original HEIC either way.