Inspect live ICY frames, audio headers, and automated artwork matching across any radio CDN.
---
Online broadcast streaming relies on protocol standards developed in the early days of Nullsoft's SHOUTcast server and the open-source Icecast platform. Known collectively as the ICY protocol, this architecture embeds text metadata directly inside active binary audio streams without requiring a separate socket connection.
When a media player connects to an Icecast, Revma, or Triton stream, it sends an initial HTTP header: Icy-MetaData: 1. If the stream server supports in-band metadata, it replies with the icy-metaint header followed by an integer (typically 16000 or 32000).
This number defines the byte interval. The client reads exactly that many audio bytes, followed by a 1-byte length header. If metadata exists, the server inserts an encoded payload matching the format:
StreamTitle='Artist Name - Song Name';StreamUrl='';
The ICY protocol was designed purely for plain-text strings. Binary image data (JPEGs or PNGs) cannot be embedded directly into ICY metadata chunks without corrupting legacy audio decoders.
Modern broadcast apps (such as OneCMS, Triton Digital widgets, and custom React radio players) perform client-side catalog lookups. When the player parses a new StreamTitle, it queries commercial databases like Apple Music, Spotify, or Last.fm in the background to fetch matching high-resolution album art.
StreamTitle='';) during ad intervals to protect client commercial tracking.Access-Control-Allow-Origin). Inspecting streams from a web browser requires server-side or edge proxying.