radio-browser.info

radio-browser.info is a community-maintained directory of internet radio stations, and you can search it by name, country, language, or tag to find a station, then copy its stream URL into a player. The directory is built for browsing and for pulling data into third-party apps, so the same station data is reachable both through the website and through its public API. If you just want to listen, the website search is enough; if you want to build a playlist or feed a player, you'll want the stream URL or the API.

Ways to Search for a Station

The directory organizes stations along a few axes, and you can combine them to narrow results:

• By name — best when you already know the station (e.g., a specific call sign or brand).
• By country — useful for browsing everything broadcast from a given country.
• By language — filters to stations broadcasting in a language you understand.
• By tag — genre or theme labels such as jazz, news, or classical, applied by contributors.

A practical approach is to start broad (country or language) and then narrow with a tag or name. If a name search returns nothing, try the tag route — station names are often inconsistent, while tags tend to be more stable.

What You Can See in the Results

Each station entry in the directory typically exposes fields you can use to judge whether it's worth trying:

The stream URL is the key field if you want to listen outside the browser. Copy it into VLC, a hardware internet radio, or any player that accepts a network stream.

Getting the Stream URL for a Third-Party Player

1. Find the station through search.
2. Open its detail entry and locate the stream URL.
3. Copy the full URL (it usually ends in a playlist or audio file extension).
4. Paste it into your player's "open network stream" or "add station" field.
5. If it fails, return to the results and try a different entry for the same station — many stations are listed more than once with different stream endpoints.

The directory also exposes a public API, which is what most third-party apps use to pull station lists programmatically. If you're building something, query the API rather than scraping the website.

When a Station Won't Play

Not every listed stream works. Entries go stale: a station changes its stream address, goes offline, or restricts access by region. This is expected in a community-maintained directory, and it's the main reason to check more than one result.

If a stream fails:

• Try another entry for the same station — duplicates often point to different servers.
• Check the codec and bitrate; some players don't support every format.
• Prefer entries with recent activity or higher vote counts, which are more likely to be live.

Treat the directory as a starting point rather than a guarantee: it tells you a station exists and where its stream was last reported, not that the stream is currently up.

radio-browser.info is a public, community-maintained database of internet radio stations. It is not a player itself; it is a data source that catalogs station names, stream URLs, genres, countries, languages, and related metadata. You use it when you want to find stations, browse by category, or feed station data into your own app or script.

What the database contains

Each entry in radio-browser.info describes a single internet radio station. Typical fields include:

• Station name and alternative names
• Stream URL (the actual audio endpoint)
• Homepage and logo/favicon links
• Country, language, and region
• Tags and genres (for example jazz, news, classical)
• Codec and bitrate information
• Votes and click counts that reflect community activity

Because the catalog is community-driven, entries are added, edited, and voted on by users. That means coverage is broad but not perfectly uniform: popular stations tend to have richer metadata, while obscure ones may have gaps.

Who it is for

Listeners

If you just want to discover stations, radio-browser.info works as a searchable directory. You can filter by country, language, tag, or codec and then open a station’s stream in a compatible player. The site helps you find a station; playback happens in whatever player or app you use.

Developers

The database is also an API-backed resource. Developers query it to populate radio features in apps, build custom players, or run analytics on station metadata. Instead of scraping individual broadcaster sites, you get a single structured source with search and filter endpoints.

How it is used in practice

A common workflow looks like this:

1. Search or filter the catalog by a criterion such as country or genre.
2. Inspect the station record to confirm the stream URL, codec, and bitrate.
3. Use the stream URL in a player or application.
4. Optionally contribute by adding missing stations or voting on existing ones.

For developers, the same steps happen programmatically: send a query to the API, receive structured results, and pass the stream URL to an audio component.

What it is not

• It is not a streaming service. It does not host or rebroadcast audio.
• It is not a guaranteed playlist. Stream URLs can change or go offline, since they point to third-party broadcasters.
• It is not a curated editorial product. Quality and completeness depend on community contributions.

Practical considerations

• Stream reliability varies. A listed URL may stop working if the broadcaster changes it. Re-checking the record or the station’s homepage helps.
• Metadata quality varies. Tags and genres are user-supplied, so the same station might be classified differently over time.
• Check licensing and terms before redistributing data or building a commercial product on top of it.

If you need a single place to discover internet radio stations or to source station data for an app, radio-browser.info is built for exactly that. If you want a ready-made listening experience with a polished interface, you will still need a separate player.

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:

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.

Yes. radio-browser.info is built around a community-maintained radio station database that developers can query programmatically, so it can serve as a data source for apps that need station names, stream URLs, codecs, bitrates, and related metadata. The practical conditions are that you should confirm the current usage terms and community guidelines before shipping, and you should design your integration to tolerate stale or dead stream links, since the dataset is crowd-sourced and changes over time.

What radio-browser.info provides to developers

At a high level, the service exposes a searchable catalog of internet radio stations rather than a single curated playlist. For development purposes, the useful part is the station records themselves: each entry typically describes a station and the technical details needed to play it.

Typical fields you can expect to work with include:

• Station identity: station name, possible alternative names, country, language, and tags/genres.
• Stream endpoint: the stream URL that a player would open.
• Technical playback details: codec (for example MP3 or AAC) and bitrate.
• Availability signals: whether the station is currently reachable, plus vote or click counts that indicate community usage.
• Metadata: homepage, favicon/logo references, and other descriptive fields where available.

Because the catalog is community-maintained, field completeness varies by station. Some entries are rich; others may be missing logos, tags, or even a working stream.

How developers typically integrate it

The common pattern is to treat radio-browser.info as a remote station directory and cache what you need locally.

1. Query the directory for stations matching your criteria (genre, country, language, name).
2. Store the returned records in your own database or local cache, keeping the station ID as a stable reference.
3. Resolve a stream URL at play time from your cached record, then hand it to your audio player.
4. Refresh periodically so new stations appear and removed ones disappear.

A simplified request flow looks like this:

Your app
  -> query radio-browser.info for stations by tag/country/name
  -> receive station records (name, url, codec, bitrate, ...)
  -> cache records locally
  -> on play: open stream URL in your audio player
  -> on failure: mark station as unavailable, retry later

The exact endpoint paths, parameters, and response format are defined by the service itself, so check its current developer documentation rather than hard-coding assumptions from an older tutorial.

Handling updates and dead links

This is the part that separates a demo from something users will keep. Internet radio streams go offline, change URLs, or move to a different codec without warning, and a community database will always lag behind reality.

Practical safeguards:

• Never assume a stream works. Attempt playback, and if it fails, surface a clear "station unavailable" state instead of a silent error.
• Cache aggressively, refresh regularly. Serve from your cache for speed, but schedule background refreshes so your data doesn't drift.
• Track failures per station. If a stream fails repeatedly, deprioritize or hide it rather than retrying on every user action.
• Keep the station ID, not just the URL. IDs let you re-fetch updated details when a stream URL changes.
• Handle missing fields gracefully. Don't require a logo, bitrate, or codec value to render a station entry.

Before you ship: terms and etiquette

Because the data is community-contributed, using it responsibly matters as much as the technical integration.

• Read the usage terms and community guidelines for the service before building it into a product, and re-check them if your usage grows.
• Respect rate limits and avoid hammering the service. Batch and cache queries instead of querying on every user interaction.
• Attribute appropriately where the guidelines or your own product norms call for it.
• Consider contributing back corrections or new stations if your app surfaces broken entries, since the catalog depends on community maintenance.

When this is a good fit — and when it isn't

Good fit: you're building a radio player, a discovery feature, or a directory that benefits from a broad, community-maintained station list and can tolerate occasional broken entries.

Weaker fit: you need guaranteed uptime, contractual SLAs, or a fully verified, always-live stream for every station. In that case, treat radio-browser.info as a starting point and add your own validation and curation layer on top.

The short version: yes, developers can use radio-browser.info as an API-style data source for radio station metadata and stream URLs. The work that makes it production-ready is caching, refresh logic, graceful failure handling, and staying within the service's usage expectations.

radio-browser.info is best understood as a community-maintained radio station directory and metadata service, not a consumer listening app. If you want to browse, search, or pull structured station data into your own project, it fits that job. If you just want to tap a station and hear audio with recommendations and a polished player, a typical streaming app is the better fit — and you will likely need a separate player to actually listen to stations you find here.

The core difference: directory and data vs. playback experience

A typical radio streaming app bundles three things into one product: a catalog of stations, a built-in player, and discovery features like recommendations, favorites, and curated lists. radio-browser.info concentrates on the first layer — the catalog and its metadata — and leaves playback to whatever tool you point at it.

What "metadata-focused" means in practice

Because the emphasis is on station records rather than playback, the useful output is structured information about stations — things you can search, filter, and feed into another program. That is why the service tends to appeal to people building something: a custom player, a dashboard, a script, or an integration into another app.

If your goal is to use station data rather than consume audio, this orientation is an advantage. If your goal is to press play, it is a detour.

Who each option suits

Choose radio-browser.info when you:

• Need to look up or search radio station data
• Want to integrate station information into another tool or project
• Are comfortable pairing it with a separate player to actually listen

Choose a typical streaming app when you:

• Want one-tap playback without assembling anything
• Rely on recommendations, favorites, and curated discovery
• Prefer an all-in-one listening experience

The practical catch: you may need a third-party player

The most common friction point is expecting playback inside the service. Since the focus is the directory and its metadata, listening usually means taking a station you found and opening it in a player that handles the stream. Plan for that two-step workflow; if it sounds inconvenient, a standard streaming app will feel more natural.

Quick decision guide

• Just want to listen? Use a typical streaming app.
• Need station data or an integration? radio-browser.info is the more appropriate starting point.
• Want both? Use radio-browser.info to find the station, then play it through a separate player.