I didn't realize support for this had improved, but it's still missing Edge: https://caniuse.com/#feat=apng

You could probably polyfill something in WebAssembly for it, however!

still ridiculously large file compared to webm/mp4. The alpha support is cool though.

Here is an existing poly fill (I have not reviewed or tested this. I got it from the caniuse site)

https://github.com/davidmz/apng-canvas

> better compression

Better compression than MP4?

For certain kinds of content, possibly.

For some reason your Github page makes my FF 57 (Win7) process' memory jump from 114Mo to 4.5Go.

Opening the apng directly in a Firefox tab froze my whole linux system completely.

FF59 Win10 went from 1.7gb to 6.2gb

A weird thing about apng is it doesn't do any interframe compression. Even GIF has that. It's just a series of png images crammed into a single file.

That's not true. It has basic controls to use/clear/revert the last frame and whether the new frame draws on top or replaces part of it.

It's still useless when things are moving, but it's no worse than gif.

Oh, huh my mistake. I was thinking about how PNG compression is entirely based around using the previous pixels to predict the next one. But as far as I know, apng doesn't update the filters to use information from the previous frame. I guess you can use transparent pixels to compress pixels that don't change though.

Oh, yeah, it definitely resets the compression context between frames. But so does a video format.

No format that I'm aware of supports lossless compression that spans frames. Which leads to a funny situation where some images compress best by custom outputting a .gif or .png with no compression, and then zipping it.

As I understand it all video compression uses delta compression between frames. And you mention another issue I forgot, that it can't reuse Huffman codes or any common segments between frames. Since they are independently compressed.

> As I understand it all video compression uses delta compression between frames.

And so does apng, more or less, via alpha. But that's less important than motion interpolation, which it utterly lacks.

That github page and the apng made my firefox eat multiple gigabytes of ram and almost killed my system.

Holy crap you weren't kidding!

Fresh start of latest release version of Firefox and it shoots up to 4GB memory the moment I open just that page!

https://i.imgur.com/KJaWy2G.png

Note that Chrome also has the same page open (as well as several others) and is using less than 800MB memory.

Is there data on GIF vs APNG vs video compression?

Is the compression actually better? I just tried re-encoding some of my larger gif files with it and they all came out 2x the size.

This usually happens when you have colour pallet increases. If you had a simple animated Gif with only 256 colours and convert it to any video you instantly have more data to compress. The better use case is where you start with video and convert down to gif (like when you use gif.ski)