1987: 14,400 bps and a Pragmatist Named Wilhite
GIF was released on June 15, 1987, by Steve Wilhite at CompuServe. Wilhite was 39 at the time, leading the forum software team there, and he faced a concrete problem: CompuServe offered online services over modems that reached 9,600 baud at best. Images were technically possible but commercially untenable — a single photo asset could cost a user 20 minutes of online time, and back then online time was billed by the minute.
The requirement handed to Wilhite was pragmatic: a platform-independent image format, small enough for 1,200- and 2,400-baud connections, and able to render on every hardware configuration common at the time (a PC with an EGA card, a Mac with a 1-bit display, a C64 in 16-color mode, an Atari ST). The result was called the Graphics Interchange Format, GIF for short, designated 87a in its first specification.
The Technical Decision: 256 Colors and LZW
GIF supports a maximum of 256 colors per frame drawn from a 24-bit color palette. This limitation wasn't a design flaw but a deliberate choice: 8-bit display hardware was the standard in 1987, and anything beyond that would have been a waste of data. Compression is handled via LZW (Lempel-Ziv-Welch), a dictionary-based algorithm published by Terry Welch in 1984 that was a good fit for the CPU performance of the day.
A subtle quirk: GIF stores its own palette per frame and can vary it per image via a Local Color Table. For animations, this allows different frames to be combined with different 256-color palettes — which noticeably increases the effective color range but complicates the decoder algorithm.
1989: Animation as a By-Product
The first GIF specification (87a) made no provision for animation. Only version 89a (1989) introduced the concept of multi-frame GIFs, originally intended for "a short pause between the images of a slideshow." Nobody at CompuServe in 1989 believed this feature would one day become the culturally defining trait of the format. Animations remained an obscure gimmick for the next six years, because Netscape Navigator didn't support them until 1995 — and in doing so accidentally introduced a bug that interpreted the loop function as "repeat forever" by default, which cemented the format's later cultural character.
December 1994: The Patent Shock
On December 28, 1994, Unisys announced that it would commercially enforce the LZW patent (US Patent 4,558,302, granted in 1985 to Welch and his employer Sperry). Every vendor that sold or distributed a GIF encoder was now expected to pay license fees retroactively. CompuServe itself paid a lump sum but passed the bill on to third-party providers. That was the trigger for the "Burn All GIFs" campaign, which radicalized the young web.
Out of the patent dispute, PNG emerged within months as a patent-free replacement — the full story is in our PNG history article. The LZW patent expired in the US in 2003 and in Europe and Japan in 2004. Since then GIF has been legally unproblematic again — but by that point its technological lead was long gone.
The Pronunciation Debate (2013)
One of the more remarkable episodes in the format's history: in 2013, on the occasion of a Webby Lifetime Achievement Award, Steve Wilhite made his point with a five-word animation on stage: "It's pronounced JIF, not GIF." Wilhite insisted on the soft pronunciation (like the peanut butter brand JIF), while the majority of the web community traditionally uses the hard pronunciation (like "gift" without the "t"). The debate can't be settled on the merits — Wilhite had invented the format, but usage had developed differently — and it has been a semi-religious dispute in every tech discussion ever since. Steve Wilhite died in 2022.
The Decline: 1998–2010
Between 1998 and 2010, GIF seemed technologically finished. JPEG dominated photos, PNG took over graphics and UI elements; animated GIFs were regarded as a 90s relic from the Dancing Baby and Geocities era. Browsers built dedicated performance optimizations for their dominant formats, and GIF was maintained only as legacy. Those who wanted animation used Flash; those who wanted efficiency used MP4 and WebM.
The Resurrection: 2012–2016
Three factors brought GIF back. First: smartphones with always-on internetmade content consumable that could be optimized down to sub-100 KB sizes. Second: social media like Twitter, Tumblr, and WhatsApp supported GIF natively, but not Flash and not all browser video codecs consistently. Third — and culturally decisive: Giphy (founded in 2013 by Alex Chung and Jace Cooke) established GIF reactions as a default building block of digital communication. By 2016, 2 billion Giphy GIFs were being sent every day.
Ironically, hardly anyone sends a "real GIF" over these platforms — Giphy internally converts to MP4/WebM and serves the more appropriate format. What users call a "GIF" is usually an HTML5 video loop. The cultural brand GIF survived; the technical format has since been replaced. More on this in GIF vs. WebP for animations.
What Makes GIF Structurally Bad
For all the nostalgia: in 2026, GIF is the most inefficient popular web format. A 5 MB GIF becomes 1.2 MB as an animated WebP, 900 KB as AVIF, and 400 KB as an MP4 loop. The 256-color limit produces banding in gradients, the binary transparency leaves hard edges, and the lack of interframe coding forces full-frame storage. There's no technical reason to newly deploy GIF in 2026 — except platform compatibility: Slack reactions, some email clients, and archived CMS systems accept GIF exclusively.
Optimization: What's Even Possible?
If you genuinely have to keep an existing GIF, you can pull three levers: reduce the color palette further (from 256 down to 128 or 64, often barely visible), frame-delta encoding (storing only the changed pixel regions per frame, which every modern encoder handles), and adjusting the dithering (coarser dithering compresses better, because the run-length encoding benefits). Tools like gifsicle andImageMagick implement this. Our GIF compressor wraps this pipeline into a single browser-local UI.
The Honest Recommendation
For new content: use animated WebP, animated AVIF, or better still a looping<video> element. For recipient contexts where you have no choice (Slack reactions, email to conservative recipients): classic GIF, but deliberately kept small. For multi-format delivery, the <picture> element with a GIF fallback. You'll find a detailed overview in the article All image formats compared.
Sources
GIF89a specification (W3C mirror) · GIF87a specification · US Patent 4,558,302 (Welch, LZW) · Steve Wilhite obituary (NYT, 2022) · Giphy company history · Webby Awards archive · Wilhite, Steve. "GIF87a: Graphics Interchange Format." CompuServe Information Service, 1987.