A GIF royalty announcement helped create PNG in about two months

A licensing announcement helped send an image format back to the drawing board. After the GIF royalty uproar reached the internet in early 1995, a group of developers began designing PNG. Roughly two months later, the specification had reached its freeze. Apparently “save image” could also mean save everyone another licensing headache.

The history in PNG: The Definitive Guide locates the trigger in CompuServe’s announcement three days after Christmas 1994. Unisys held the patent on the LZW compression used by GIF. The announcement brought a licensing problem into view for software developers who had treated a familiar image format as a settled part of their work.

That timing matters because it separates the event that prompted action from the goals of the resulting design. The group wanted an unencumbered replacement and a better format. The history describes the target as “better, smaller, more extensible, and free.” Treating quality as irrelevant would leave several of the group’s actual decisions unexplained.

Thomas Boutell posted the first draft on January 4, 1995. The group worked through compression, color support, integrity checks and transparency while the design evolved. A shared file format has to be specific enough that two people can independently build software and agree on what the bytes mean, even after the argument about the filename has finally ended.

The group’s decision process helped that happen. The history describes a regularly updated scorecard of accepted, rejected and unsettled features, with Boutell able to decide when consensus failed. That gave disagreement somewhere to end. An online discussion can generate an impressive volume of text without producing one image anybody can open.

The March 1997 RFC records the technical result as a lossless raster format with indexed color, grayscale, truecolor and optional alpha. Its abstract explicitly identifies a patent-free GIF replacement as part of the purpose. The artifact carries both parts of the story: the permission problem and the extra capabilities built while solving it.

Transparency is a useful example of why the replacement’s details matter. A program selecting a format needs to know what it can preserve, alongside whether its developers can implement it. Those questions meet in the exported file. A politically satisfying format that discards something an application needs still leaves the application’s owner with work to do.

For teams choosing a dependency or an interchange format, this history makes the exit route tangible. A specification, multiple implementations and files that can cross between them reduce the amount of reinvention a surprise licensing change demands. That is a more useful readiness test than assuming a widely installed component will always come with the same terms.

The early PNG design sprint produced a specification quickly. Getting every application to treat the replacement as an ordinary choice was a separate task, with its own compatibility work waiting beyond the finish line of that first two-month effort.

The pixels found another way out.