How Internet Radio Actually Works

Tap a station glyph on the globe and, a breath later, a studio on the other side of the planet is playing in your browser. No app, no account, no middleman relay. The machinery behind that moment is older and simpler than most people expect — and understanding it explains almost everything about why some stations answer instantly while others stay silent.

One server, many listeners

An internet radio station is, at heart, one computer running an encoder. The studio's audio feed goes in; a compressed digital stream comes out, published at a fixed web address — the stream URL. The software doing this is usually a descendant of two late-1990s projects, SHOUTcast and Icecast, whose approach barely changed in twenty-five years because it barely needed to: hold an open HTTP connection and push audio bytes down it, forever.

Your browser's built-in audio player understands this natively. When you tap a station on the globe, the player connects to that stream URL — the broadcaster's own server, directly. LiveEarthViewer hosts no audio and relays nothing; we simply know where the doors are.

The languages the audio speaks

The bytes flowing down that connection are compressed with a codec, and here the field is remarkably concentrated. In the July 2026 snapshot of the radio-browser.info directory, roughly nine out of ten playable streams use MP3 or AAC — formats every modern browser plays out of the box, which is why most stations start within a second or two of your tap.

The notable minority is HLS (HTTP Live Streaming) — about 8% of playable streams as of that snapshot. Instead of one endless connection, HLS serves a constantly-refreshing playlist of short audio chunks. It's the format television-scale streaming uses, published openly by Apple as RFC 8216. Browsers don't all play it natively, so the player quietly loads a small helper library the first time you tap an HLS station — you shouldn't notice anything except perhaps an extra half-second of buffering.

A small remainder broadcasts in OGG and other open formats, which modern browsers also handle directly.

Why some stations stay silent

Every listener discovers this within minutes: some glyphs don't answer. This is the honest texture of internet radio, and it has three main causes.

Streams die. Stations shut down, lose their hosting, or move servers without updating the public directory. The directory's volunteers run automated checks that mark streams as broken, but there is always a gap between a stream dying and the directory noticing. When it happens, the player tells you plainly and offers the next station nearby — no infinite spinner, no fake loading.

The https wall. LiveEarthViewer is served over https, and every browser blocks insecure http:// audio on a secure page — the "mixed content" rule. A station that only publishes an http stream would silently fail for everyone here, so those streams are filtered out of the playable set before they ever reach the globe. We don't proxy them into https, because re-streaming someone's broadcast through our servers isn't our place.

Geo-blocking. Music licensing is territorial, so some broadcasters restrict their streams to listeners in their own country. The stream is alive — just not for you. From the outside this looks identical to a dead stream, which is why the player treats both the same honest way: say so, move on.

The directory underneath

None of this would be navigable without radio-browser.info — a volunteer-run directory of internet radio stations, published into the public domain. As of the July 2026 snapshot it listed roughly 59,600 stations, each with its stream URL, home country, tags, and — for about one in five — real coordinates. Anyone can add a station, fix a dead URL, or contribute missing positions; improvements flow into this globe at the next snapshot. The one courtesy the directory asks of players like ours is a single anonymous click ping per play, which keeps its community popularity rankings honest. That ping is the only telemetry that leaves your session.

The result is a rare thing on the modern web: a global, commercial-grade dataset with no owner, no API key, and no gatekeeper — maintained the way lighthouses used to be, by people who simply want the coast lit.