How AIM buddy icons were chosen, made, installed, and seen

Choosing and installing an icon

The exact menus changed between AIM releases, but the basic ritual was consistent: find or make a small image, open the client’s preferences or buddy-icon control, choose the file, and publish it as part of your profile. Other people’s clients downloaded and displayed the icon beside conversations or buddy information.

Static images worked as portraits or emblems. Animated GIFs added a short loop: blinking text, a reaction, a clip from a show, or a character moving through a few frames. Third-party clients documented an important quirk of the era: the way an image was selected could determine whether its animation survived.

Designing for a tiny canvas

Successful icons favored a readable silhouette, hard contrast, a tight crop, and only a few words. Fine detail disappeared quickly. Animation worked best when the loop was short and the first frame still made sense on its own. Many files in this archive are 48×48 pixels, while surviving documentation and collections include 50×50 images and neighboring variants.

What “original” means here

The download button serves the exact validated bytes stored by the archive. It does not imply that the archive’s copy was the first version ever posted. The provenance section records the observed sources; duplicate clusters identify stored variants when the same visual work survived more than once.