Cookies for analytics and advertising
We use cookies for analytics and advertising, both sent to Google. Refusing changes nothing you can see.Read the privacy page
Converting HEIC to GIF gets an iPhone photograph into a format that even the oldest upload form will accept. It is a steep reduction — a HEIC holds millions of colours and a GIF holds 256 — so read the second section before committing a camera roll to it.
Up to 100 files at once. Mixed formats are fine.
They convert one after another and download together as a ZIP.
HEIC to GIF
Since 2017 an iPhone has recorded HEIC by default, and the codec inside it is HEVC — covered by patent pools whose terms a large part of the industry declined to accept. So support never became universal: Windows asks for a paid codec, several browsers will not display the format, and a great many upload forms, print services and web applications reject it outright.
That is the whole reason this page exists. Nothing is wrong with the photograph, and the destination cannot read it. Which format to convert into is then a choice, and GIF is rarely the best one.
A HEIC carries ten bits per channel, wide colour and high dynamic range — it is the reason a modern iPhone photograph looks right on a modern screen. A GIF carries at most 256 colours in total, chosen for the whole image.
The result is not subtle. Skies band into visible stripes, skin tones go blotchy, and any smooth gradient breaks into steps. Dithering scatters the error so the banding reads as texture instead of stripes, which some people prefer and neither of which is the photograph. No setting avoids this, because the limit is the format rather than the conversion.
It is worth ten seconds. Almost every form that accepts GIF also accepts JPG and PNG, and both are dramatically better here: JPG is a fraction of the size with no banding at all, and PNG keeps every colour losslessly.
GIF is the right answer only when something names it specifically — an old forum, a signature image, a system nobody has updated in a decade. If the list of accepted extensions includes anything else, take the anything else.
A HEIC from an iPhone can be a container holding more than a picture: the still, a short video from around the moment of capture, and on portrait shots a depth map. Converting produces the still and discards the rest.
People frequently come here hoping to turn a Live Photo into a shareable animation, and GIF is the wrong destination for that even when it works. Converting the video part to MP4 keeps every frame, plays everywhere, and is typically a fraction of the size an animated GIF would be — a three-second clip is a couple of hundred kilobytes rather than several megabytes.
HEIC carries wide-gamut colour data with a profile describing it, and a conversion that ignores that profile produces images which look flat and desaturated next to what the phone shows — most visible on skies, foliage and skin. That is the common complaint about converted iPhone photographs, and it is usually the profile rather than the target format.
This conversion does not handle it. The decoder hands back pixels, nothing here reads the embedded profile, and GIF has nowhere to record one even if it did — so a Display P3 photograph is written as though its numbers were sRGB and comes back duller than the original. It is the second reason, after the 256-colour palette, that a phone photograph is the wrong material for this conversion. If the colour matters, open the result next to the original before the GIF becomes the file anyone sees.
An iPhone photograph carries the date, the camera settings and, unless location services were off, the exact place it was taken. GIF has essentially nowhere to put any of it, so the converted file arrives without.
That is a loss for a personal archive — a photo library that will not sort chronologically is a great deal of work to repair — and a benefit for anything being published, since the location is the field people most often forget they are sharing. Either way it is worth knowing which of the two situations you are in before converting a camera roll.
Converting is a lossy step twice over: the HEIC was already compressed, and the GIF throws away nearly all the colour. Doing it once for a specific upload is fine; deleting the originals afterwards is throwing away the photographs.
Keep the HEIC as the master and generate whatever a particular destination needs. The originals also hold the ten-bit data, the Live Photo and the metadata, and no conversion recovers any of them.
The conversion runs inside the browser tab on your own processor, so the photographs are never uploaded. There is no account, no queue and no daily limit, and a whole camera roll can be dropped at once — each file converts in turn and the batch comes back as a single ZIP.
For personal photographs that is the substantive point rather than a feature. The most reliable way to keep a picture private is not to send it anywhere, and it also means a hundred images convert without a hundred uploads.
| HEIC | GIF | |
|---|---|---|
| Full name | High Efficiency Image Container | Graphics Interchange Format |
| File extension | .heic | .gif |
| Media type | image/heic | image/gif |
| Compression | Lossy — file size is bought with quality | Lossless — nothing is discarded |
| First published | 2015 | 1987 |
| Published by | MPEG | CompuServe |
| Specification | ISO/IEC 23008-12 | GIF89a |
| Licensing | Published, not standardised | Open standard |
| Standing today | Current | Legacy, still read everywhere |
| Bit depth | 10 | 8 |
| Colour it can describe | YCbCr, wide gamut | indexed palette |
| Largest image | — | 65,535 px per side |
| Opens in a browser | Some browsers | Every browser |
| Considered instead | JPG, AVIF, WebP | WebP, MP4 |
GIF has no alpha channel. A transparent HEIC comes out with those areas filled in — white unless something else is set — and no setting in GIF brings the transparency back.
GIF holds a single still image. An animated HEIC keeps its first frame and loses the rest, so a conversion is a way to take a still out of one, not a way to move it.
GIF stores at most 256 colours per frame. A photograph converted into one is reduced to a palette, which is what makes the sky look stepped rather than smooth — it is the format, not a quality setting.
HEIC carries up to 10 bits per channel and GIF stores 8. The extra precision is what survives heavy correction without banding, so the conversion is best made after the editing rather than before it.
GIF opens in every current browser. HEIC has narrower browser support than that. If the file is going onto a web page or into a form, that is usually the whole reason for the conversion.
The usual programs do not overlap: HEIC opens in Apple Photos and Adobe Lightroom, GIF in GIMP, Adobe Photoshop and ImageMagick — so whoever receives the result needs something from the second list.
The result is larger than the original and no better. HEIC has already discarded detail, and GIF stores what is left without discarding more — it prevents further loss rather than undoing the first one.
The two are aimed at different work: HEIC at phones and photography, GIF at the web. That is worth weighing before converting, because the reason one exists is usually the reason the other is awkward.
HEIC is MPEG's format, published in 2015. It records 10 bits per channel.
GIF comes from CompuServe and dates from 1987, specified as GIF89a. GIMP, Adobe Photoshop and ImageMagick all read it.
GIF was published in 1987 and HEIC in 2015. The older one is generally the safer file to hand to somebody; the newer one usually does the job in fewer bytes.
No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is libheif, the reference decoder for Apple's HEIC; your browser fetches it once and caches it.
GIF holds at most 256 colours in the whole image and a HEIC holds far more — ten bits per channel, with wide colour. Reducing a photograph to 256 colours makes skies band into visible stripes and skin tones go blotchy. It is the format, not the conversion.
Almost certainly, and both are accepted essentially everywhere GIF is. JPG is the right target for an iPhone photograph — small, no banding, and universally understood. Choose GIF only if something specifically demands it.
Not here. This produces a still image. A Live Photo is a still plus a short video inside the same container, and only the still comes out — converting the video part to MP4 keeps the motion and is smaller than an animated GIF would be.
The codec inside is HEVC, which is covered by patent pools that many vendors declined to license. Windows asks for a paid codec from the Store, several browsers do not display the format, and many upload forms reject it — which is the usual reason people are converting at all.
Settings, then Camera, then Formats, and choose "Most Compatible" instead of "High Efficiency". The camera then records JPEG and the problem stops recurring, at roughly double the storage per photograph.
No. The conversion runs inside your own browser, so the photographs never leave your device. There is no account, no queue and no daily allowance, and a whole camera roll can be dropped at once.
The claims this page makes about HEIC and GIF are checkable, and these are the documents that settle them.