Initializing... drag & drop files here
Supports: HEIF
Drop in one or more HEIF images and each becomes a frame of a single animated PNG, played in upload order. This is the fix for HEIF's central problem: HEIF renders natively only in Safari 17 and later — roughly 15% of browsers by global usage — while APNG reaches about 96% and degrades gracefully to a static picture everywhere else. Upload one HEIF and you get an ordinary static PNG; upload several and you get a looping animation whose pace you set with the FRAMERATE control.
.heif images or click "+ Add Files". Upload order is frame order, so add them in the sequence you want them played..apng. Files are uploaded over an encrypted connection, converted on our servers, and deleted automatically after a few hours — no sign-up, no watermark.| Property | HEIF | APNG |
|---|---|---|
| Standard | ISO/IEC 23008-12, finalised March 2015 | Part of the PNG Specification, Third Edition — a W3C Recommendation published 24 June 2025 |
| Payload | HEVC and other codecs; .heic specifically means HEVC Main or Main Still Picture |
PNG image data with DEFLATE compression |
| Compression | Lossy or lossless, very space-efficient | Lossless |
| Animation | Image sequences, when the file carries one | Native, via the acTL, fcTL and fdAT chunks |
| Transparency | Alpha supported | 8-bit alpha, preserved by this conversion |
| Native browser rendering | Safari 17+ only, about 15% globally | About 96% — Chrome 59+, Firefox 3+, Safari 8+, Edge 79+, Opera 46+ |
| Fallback when unsupported | The file simply will not open | Decoders that ignore the animation chunks show the first frame as a normal PNG |
| Opens on a clean Windows PC | Needs Microsoft's HEVC Video Extensions | Any browser or standard image viewer |
| FRAMERATE | Time on screen per frame | Best for |
|---|---|---|
| 1 FPS (Slideshow) | 1 second | Photo slideshows where each image needs reading time |
| 2 FPS (Slow) | 0.5 seconds | Before-and-after comparisons, step-by-step sequences |
| 5 FPS | 0.2 seconds | Simple UI demos and loose stop-motion |
| 10 FPS (Recommended) | 0.1 seconds | The default; smooth enough for burst photos without bloating the file |
| 25-30 FPS | About 0.03-0.04 seconds | Genuine motion captured as a fast burst |
| 50 FPS (Max Speed) | 0.02 seconds | Very short, very fast sequences; expect a large file |
Because APNG stores every frame losslessly, doubling the frame rate over a fixed set of photos does not add data — it just plays them faster. Adding more photos is what grows the file.
Yes, and that is the main point of this page. Leave "Combine?" on "Single animation", upload your photos in the order you want them shown, and each becomes a frame. Switch to "Individual files" if you would rather get one APNG per photo. A single upload with "Single animation" still works — with one picture there is nothing to animate, so it produces a plain static PNG that any viewer opens.
No. We checked the option set that renders for a HEIF-to-APNG job and it is deliberately short: Image resolution, FRAMERATE, and "Combine?". There is no quality percentage and no palette or colour-reduction control, because APNG output here is full-colour and lossless. The only levers on output size are how many frames you include and what resolution you output at. To shrink an APNG afterwards, run it through compress APNG, which has the reduction controls this page does not.
Usually yes, sometimes dramatically. HEIF is one of the most space-efficient image formats in use, packing a photo with HEVC compression, while APNG stores each frame losslessly with the same DEFLATE scheme PNG has always used. A handful of camera-resolution photos can produce an APNG several times the size of the sources combined. The practical remedies are to lower the output resolution before converting, include fewer frames, or compress the result afterwards.
Yes. APNG carries a full 8-bit alpha channel, and transparency in a source image is preserved rather than flattened onto a background. If your HEIF files are ordinary camera photos they have no alpha to begin with, so this only matters for images that were composited or exported with a cut-out subject.
It shows the first frame as a static PNG. That is by design — APNG stores its animation in ancillary chunks (acTL, fcTL, fdAT) that a plain PNG decoder is required to ignore, so the file remains a valid PNG no matter what opens it. That graceful degradation is the strongest argument for APNG over a video format when you cannot control the viewer.
It is a standard now. APNG began as an extension outside the original PNG specification, but it is formally part of the PNG Specification Third Edition, published as a W3C Recommendation on 24 June 2025. Browser support arrived long before that — Firefox from version 3, Safari from 8, Chrome from 59, Edge from 79, and Opera again from 46 after a gap.
Compatibility, and it is not a close call. Only Safari 17 and later renders a .heif natively, so on Windows, Android, Chrome, Firefox, or Edge your file is either unopenable or requires a codec pack. APNG opens in essentially every browser and image viewer with nothing installed. You give up HEIF's compression efficiency in exchange for a file the recipient can actually see.
Then pick a still target instead. HEIF to PNG gives a lossless single image, HEIF to JPG gives the most universally readable one, and the HEIF converter lets you pick any supported image format. Come to APNG specifically when you want motion — a burst of photos, a short sequence, or a looping animation that must survive being embedded anywhere.
They are uploaded over an encrypted connection, converted on our servers, and deleted automatically a few hours later. There is no sign-up, no watermark on the output, and files are never shared or made public. On a large batch the practical constraint is upload size and time rather than the conversion itself.