Classic Winamp fits inside a browser, skins and all

The little player window, equalizer and playlist are back in a browser tab. Webamp turns the familiar Winamp interface into working web controls, so the nostalgia includes something to click. A skin can change the wrapper while the music keeps playing. Finally, a reason for a browser tab to have an actual skin condition.

The Webamp project calls itself a reimplementation in HTML5 and JavaScript. That wording matters: the browser is running a reconstruction of the classic experience. An old-looking player does not mean the original Windows application has somehow learned to run unchanged inside Safari.

The live demo is the quickest place to encounter that distinction. Its appeal is in the small, separate controls and movable windows as much as the outline of the player. Recognizing a picture lasts a moment; recognizing how the controls fit together can send someone looking for a skin they thought had disappeared with an old hard drive.

The README promises “full skin support” and names modern Edge, Firefox, Safari and Chrome among supported browsers. Internet Explorer is explicitly unsupported. There is a pleasing amount of historical confusion available in that combination: an old desktop interface can return through current browser capabilities while the old browser sits this one out.

The visualizations come through Butterchurn, a WebGL implementation of MilkDrop. That is another reconstruction with its own code and behavior. The player, skin collection and visualizer can therefore be inspected as connected projects instead of being sealed together in a single nostalgic executable.

The Webamp repository also separates reusable packages from its demonstration site and skin database. An application builder can investigate the player library without needing to reproduce the whole public site. That division gives the reconstruction a second use beyond a visit: the interface can become part of somebody else’s web experiment under the relevant project licenses.

For a listener, a useful first test is more ordinary. Does the music file you want to play work in your browser? Can you read the controls at the size you use? Does the visualization remain smooth when the rest of the machine is busy? The fact that a familiar skin loads cannot settle every part of playback.

A preservation collection could keep both a favorite skin file and a screenshot of it in use, recording the player version alongside them. That would preserve the actual styling asset and an example of how it appeared. A screenshot alone cannot give another player its buttons back, while the skin file alone leaves the intended appearance harder to verify.

The reconstruction leaves plenty of room for personal experimentation without pretending that the whole late-1990s desktop came along. Someone can revisit the equalizer, try a different skin and let the visualization occupy the screen again. The remaining compatibility question belongs to the particular skin, browser and media someone brings to it.

Internet Explorer remains unsupported.