Initializing... drag & drop files here
Supports: JPG, JPEG, JFIF
APNG (Animated PNG) is the lossless, true-colour, full-alpha answer to the animated GIF: part of the PNG format since PNG Third Edition became a W3C Recommendation on 24 June 2025, storing a sequence of frames in an ordinary .png-family file. Converting JPEGs to it makes sense when you have a sequence of photos — burst shots, exported video frames, a step-by-step capture — and you want them to loop without GIF's 256-colour palette flattening every gradient into bands.
One thing to settle before you go further: a single JPEG cannot animate. Upload one photo and you get a one-frame file — in practice a plain static PNG carrying the .apng extension, because there is nothing to move. Animation requires two or more images. If you only have one picture and want motion, you need a video target such as JPEG to WebM or JPEG to MP4, which hold a still on screen for a set duration.
| Property | APNG | GIF | Animated WebP |
|---|---|---|---|
| Origin | Mozilla, 2004; W3C Recommendation since 24 June 2025 | CompuServe, GIF89a in 1989 | Google, 2010s |
| Colour | 24-bit true colour | 256-colour palette per frame | 24-bit true colour |
| Transparency | 8-bit alpha, smooth edges | 1-bit, hard jagged edges | 8-bit alpha |
| Compression | Lossless (DEFLATE) | Lossless, but palettised first | Lossy or lossless |
| Size on a photo sequence | Large | Large and colour-banded | Smallest of the three |
| Browser support | ~96% — Chrome 59+, Firefox 3+, Safari 8+, Edge 79+ | Universal | Chrome, Firefox, Edge, Safari 14+ |
| If the viewer can't play it | Falls back gracefully to the first frame | Never happens | Shows a broken image |
| Best for | Crisp loops, screen captures, anything needing clean alpha | Chat, forums and email that accept nothing else | Web delivery where bytes matter most |
.jpg, .jpeg or .jfif files onto the page, or click "+ Add Files" to browse. Frame order follows the order they are listed, so number your filenames beforehand.| You upload | Combine? setting | What comes out |
|---|---|---|
| One JPEG | Not applicable | A single-frame file — effectively a static PNG under the .apng extension |
| Several JPEGs | Single animation (default) | One looping APNG; each image is one frame, held for 1 ÷ framerate seconds |
| Several JPEGs | Individual files | One output per input, each a single static frame |
At the default 10 FPS, ten photos make a one-second loop — usually far too fast for a slideshow. Drop to 2 FPS or 1 FPS (Slideshow) when your frames are photographs meant to be looked at, and keep the higher rates for genuine motion sequences such as exported video frames or a burst capture.
Because animation needs more than one frame, and one image only supplies one. Our pipeline duplicates a lone image so the assembler has a sequence to work with, but two byte-identical frames collapse back into a single one and the result carries no animation control chunk — it is a plain static PNG wearing the .apng extension. That is the honest outcome rather than a bug: to get movement, upload the whole sequence, or use a video target like JPEG to WebM where a still is deliberately held on screen for a chosen duration.
With the Framerate dropdown, which sets the delay stamped on every frame — the delay is exactly 1 ÷ framerate seconds, so 10 FPS is 0.1 s per frame and 2 FPS is half a second. Total run time is simply your frame count divided by the framerate. There is no per-frame timing control here: every frame gets the same delay. If you need one frame to linger longer than the rest, duplicate that image in the upload so it occupies two consecutive frames.
Usually not, for photographs. APNG compresses losslessly with DEFLATE, which handles flat colour and sharp edges well and continuous-tone photography badly, so a photo sequence can come out very large. GIF gets smaller by first crushing each frame down to 256 colours — that is why its output bands and dithers. The honest summary: APNG wins decisively on quality and on flat graphics, GIF often wins on raw size for photos, and animated WebP beats both when size is what actually matters.
In browsers, close to it — roughly 96% of users, with Chrome 59+, Firefox 3+, Safari 8+ and Edge 79+ all rendering it natively. Outside browsers it is far less certain: many email clients show only the first frame, and plenty of upload pipelines either reject .apng or silently re-encode it. When the destination is email, a forum or a chat platform you don't control, GIF remains the format nothing refuses.
No. JPEG has no alpha channel at all, so there is no transparency information in your source to carry across — every pixel, including everything behind your subject, is opaque colour. APNG's excellent 8-bit alpha support only helps if the frames arriving already have alpha, which is the case for PNG sources: see PNG to APNG. To get transparency from a JPEG you have to cut the background out in an image editor first.
No further quality is lost — APNG is lossless, so it stores exactly the pixels decoded from your JPEGs. It also cannot recover anything: the detail your original JPEG compression discarded is gone, and no format change brings it back. The practical consequence is size, not fidelity. A set of photos that occupied a few hundred kilobytes as JPEGs can become several megabytes as an APNG, because you have traded lossy compression for pixel-exact storage.
Ideally yes. The APNG assembler cannot rescale frames, so images of differing sizes are placed onto a shared canvas before assembly — which means an odd-sized frame will sit within the common frame rather than filling it. For a clean loop, export or crop every image to identical pixel dimensions before uploading. If they are all the same shape but different sizes, use Image resolution to bring them to one target size in the same pass.
They are uploaded over an encrypted connection, assembled on our servers, and deleted automatically a few hours later — no sign-up, no watermark, never shared or made public. Because a lossless animation of photographs is large, the practical constraint is upload and download size and time; reducing the pixel dimensions with Image resolution is the most effective way to keep a long sequence manageable.