Where Does radio-browser.info Get Its Radio Station Data?

Updated

radio-browser.info is a community-maintained, open directory of internet radio stations. Its station data comes primarily from user contributions and automated collection, not from a single commercial provider or official broadcaster registry. That means the directory can be broad and useful, but individual entries may be outdated, duplicated, or broken when a station changes its stream. If you need a station to work right now, treat radio-browser.info as a starting point and verify the stream against another source.

How the data is collected

The directory is built around a public API and a database that anyone can read from or write to. In practice, entries arrive through a few common paths:

  • Community submissions. Users add stations manually, often by entering a name and a stream URL, then tagging it with country, language, and genre.
  • Automated collection and imports. Streams can be discovered or bulk-imported from playlists, other directories, or scripts that probe known radio endpoints.
  • Edits and corrections. Other users can update a station's metadata, fix a broken URL, or flag a duplicate, so the record reflects many small contributions over time rather than one authoritative edit.

Because there is no single gatekeeper approving every change, quality varies by entry. A popular, frequently edited station is usually more reliable than an obscure one added once and never touched.

What fields a station record typically contains

A typical entry is metadata plus one or more stream endpoints. The fields most relevant to whether you can actually play a station include:

Field What it tells you Why it matters
Station name Display name Can differ from the broadcaster's official branding
Stream URL The actual audio endpoint The single most failure-prone field
Codec / bitrate Format and quality (e.g. MP3, AAC) Determines player compatibility and bandwidth
Country / language Geographic and language tags Useful for filtering, but user-supplied and sometimes wrong
Genre / tags Content categories Often inconsistent across contributors
Votes / clicks Community popularity signals A rough proxy for whether others got it working

The stream URL is the field to check first. Names, tags, and even country labels are descriptive; the URL is what your player actually connects to.

Why entries go stale

Internet radio is volatile. A station can change its streaming provider, switch codecs, move to a new URL, or go offline entirely, and nothing in the directory updates automatically. Common failure modes:

  • Dead stream. The URL returns an error or times out because the station moved or shut down.
  • Redirect changes. The old URL still resolves but points somewhere unexpected or to a different station.
  • Metadata drift. The name, genre, or language no longer matches what the station now broadcasts.
  • Duplicates. The same station appears several times with slightly different URLs, only one of which works.

This is normal for a crowd-sourced directory. It is not a sign the service is broken; it reflects the fact that no one is contractually responsible for keeping each entry current.

How to check reliability before you rely on it

If you are building an app, a playlist, or just want a working stream, verify rather than assume:

  1. Test the stream URL directly in a player or with a command-line tool before shipping it.
  2. Cross-check against another source — the broadcaster's own website, an official app, or a second directory — especially for stations you depend on.
  3. Prefer entries with community activity (votes, recent edits) over untouched ones, but treat that as a hint, not a guarantee.
  4. Handle failure gracefully in anything you build: expect some percentage of URLs to be dead and plan a fallback.
  5. Contribute fixes back if you find a working URL for a broken entry, since the directory improves only through edits.

The short version

radio-browser.info aggregates station data from community contributions and automated collection, storing names, stream URLs, codecs, and tags in an open, editable database. It is a good discovery and integration source, but it is not authoritative and its entries can go stale. Confirm the stream URL against another source before you depend on it, and design for the possibility that any given entry has stopped working.