Initializing... drag & drop files here
Supports: TIFF, TIF
TIF and APNG are both lossless raster formats, so the instinct is that nothing is lost. That is only half right. APNG adds the one thing TIF cannot do — play as an animation in a browser — and drops three things TIF is good at: bit depths above 8 per channel, CMYK, and multiple pages in one file. The short answer: convert to APNG when you have a sequence of separate TIF files that needs to loop on a web page, and keep the TIFs when depth, colour space or archival fidelity is the point.
| Property | TIF / TIFF | APNG |
|---|---|---|
| Specification | TIFF 6.0, Aldus 1992, now maintained by Adobe | W3C PNG Specification Third Edition, Recommendation 24 June 2025 |
| Compression | Lossless (LZW, Deflate, PackBits) or lossy JPEG, depending on how it was saved | Always lossless, per-frame DEFLATE |
| Bit depth | 1 to 32 bits per channel; 8 and 16 are the common cases | 8 bits per channel |
| Colour models | Greyscale, RGB, CMYK, Lab, palette | RGB only |
| Transparency | Optional alpha via ExtraSamples | Full 8-bit alpha, 256 levels |
| Multiple images in one file | Yes — pages as separate IFDs | Yes — as animation frames |
| Animation | None; pages are static | Frame delays and an infinite or counted loop |
| Renders in a browser | No | Yes, about 95.9% of browsers globally per caniuse |
| Practical size ceiling | 4 GB for classic TIFF's 32-bit offsets (BigTIFF lifts it) | No format limit, but every frame is stored in full |
| Typical use | Scanning, print prep, archival masters, scientific imaging | Short looping graphics on the web |
.tif/.tiff images onto the page or use the file picker. Add two or more, in the order you want them played — the list order on the page is the frame order.| Control | Choices | What it does |
|---|---|---|
| Framerate | 1, 2, 5, 8, 10 (default), 12, 15, 20, 25, 30, 50 FPS | Writes an exact 1/N-second delay on every frame. Total runtime is frame count ÷ FPS |
| Image resolution | Keep original (default), Preset Resolutions, Width, Height, Width x Height, Resolution Percentage | The dominant size lever, since each frame is stored in full. Also sets the shared canvas when your TIFs differ in size |
| Combine? | Single animation (default), Individual files | Merge the batch into one animation, or convert each file separately |
There is no quality slider, no palette-reduction setting and no loop-count control on this conversion. APNG frames are lossless by definition, and the output is always written to loop forever. Frame count, frame dimensions and frame content are the only things that move the file size.
No and no. They are two spellings of the same format — the three-letter form is a leftover from DOS-era 8.3 filenames — and this page accepts either extension, as does its TIFF to APNG twin. Nothing about the conversion changes based on which spelling your files use.
Each uploaded file is normalised to one image before the frames are assembled, and that step reads only the first page (the first IFD) of a multi-page TIF. Pages two onward never reach the assembler, so the result is one frame — and a one-frame APNG is just an ordinary static PNG. Split the document first with Photoshop, GIMP, ImageJ/Fiji or tiffsplit, then upload the individual TIFs together as one batch.
Two or more, and they must actually differ. The assembler discards duplicate consecutive frames, so uploading the same image twice still produces a file with no animation control chunk — a plain static PNG. Any set of two or more visibly different TIFs produces a genuine animated PNG that loops indefinitely.
No. APNG stores 8 bits per channel in RGB, so a 16-bit-per-channel scan is reduced to 8 bits and a CMYK TIF is converted to RGB. For photographic content the visible difference is usually small, but the data is genuinely discarded — always convert a copy and keep the TIFs if they are your masters.
Yes, when the TIF has one. APNG carries a full 8-bit alpha channel, so semi-transparent pixels, anti-aliased outlines and soft shadows all come through at their original opacity rather than being flattened onto a background. A TIF saved without alpha simply stays fully opaque — the conversion never invents transparency that was not there.
They are unified onto one canvas, because APNG requires every frame to share the same dimensions and the assembler cannot resize. Each smaller frame is scaled with its aspect ratio preserved, centred, and padded out to a canvas as large as the widest and tallest frame in the set; the padding is left transparent. Nothing is cropped or stretched. If every file already shares one size, this step is skipped entirely.
Two reasons. Each frame is stored independently — APNG has no inter-frame motion prediction of the kind H.264 uses — so ten frames cost roughly ten times one frame. And many TIFs on disk are LZW- or JPEG-compressed at high ratios that PNG's lossless DEFLATE cannot match on photographic content. Reducing Image resolution is by far the most effective fix, since bytes track pixel count per frame; for a long sequence, TIF to MP4 will be smaller by an order of magnitude.
It shows the first frame as an ordinary still image. The PNG Third Edition specification requires a decoder that does not recognise the acTL, fcTL and fdAT chunks to ignore them and display the static image, so an APNG degrades gracefully in old viewers, thumbnailers and image libraries instead of failing. If you need guaranteed inline animation in chat apps, forums and HTML email, TIF to GIF is the safer target despite its 256-colour ceiling.