Radio Browser vs Wallhaven

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d95.1%82.4%
Uptime · 30d98.3%71.7%
P50 · ms556625
P95 · ms24313981
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree and open source — no keyFree tier — key may be required
Rate limitUnpublished (clients asked to send a descriptive User-Agent)45 req/window · 44 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Radio Browser vs Wallhaven: common questions

Which is more reliable, Radio Browser or Wallhaven?

On our scheduled checks, Radio Browser leads on measured uptime — Radio Browser at 95.1% versus Wallhaven at 82.4% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Radio Browser or Wallhaven?

Radio Browser has the lower median latency in our checks — Radio Browser responds in 556 ms versus Wallhaven at 625 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Radio Browser and Wallhaven need an API key?

Radio Browser needs no key, while Wallhaven requires a free API key. If you want to start calling without signup, reach for Radio Browser first.

Can I call Radio Browser and Wallhaven from the browser?

Only Radio Browser is browser-friendly — it returns CORS headers over HTTPS. Wallhaven needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Radio Browser and Wallhaven free for commercial use?

Radio Browser has unclear commercial terms, and Wallhaven has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.