RadioKing Website: Keep RadioKing and Add a Full Station Website

If RadioKing runs your stream and automation, you can keep it and still have a full station website. RadioSiteMaker plays your RadioKing stream as it is and builds the site around it: a player that keeps playing across pages, a schedule, show and DJ pages, podcasts and events.

Disclosure: RadioSiteMaker and RadioHost Studio are our own products. RadioKing prices were checked on RadioKing's own website and pricing pages on 5 November 2026; we say below where RadioKing's website add-on is the better fit.

Which URL to paste: two shapes, two results

RadioKing stream addresses come in two shapes, and RadioSiteMaker treats them differently.

1. The slug address (recommended):

https://play.radioking.io/mystation

The last part, mystation, is your station's slug. With this address the site reads RadioKing's public widget API for that slug and gets the artist, title and cover of the current track.

2. The numeric address:

https://listen.radioking.com/radio/123456/stream/789012

This one contains only numeric ids, no slug. RadioKing's widget API is keyed by the slug and does not accept the numeric id, and there is no public way to look up a slug from the id. So for this address the site does not call RadioKing's API at all. It reads the track titles carried inside the audio stream (ICY metadata) instead.

The practical difference: with the numeric address you still get artist and title, as long as the stream carries them, but no cover art from RadioKing; the site looks covers up in Apple's iTunes Search instead. If the stream carries no titles, the player shows your show name or station name. If you have a play.radioking.io/<slug> address for your station, use that one.

Paste the HTTPS address in Settings → Stream on your RadioSiteMaker dashboard and leave Stream Type on Auto-detect. Test it first; the tester shows whether now-playing data came back:

How now-playing works with RadioKing

For a slug address, the site asks RadioKing's widget API for the current track and reads the artist, title and cover. When the cover RadioKing returns is just the station's default image, the site drops it and looks up the real album cover instead, so listeners do not see your default image on every song. Turn on Hide Song Art if you prefer a vinyl placeholder.

The show name in the player comes from your RadioSiteMaker schedule, and every track change goes into the site's Recently Played list. The site does not show a listener count for RadioKing slug streams.

This is not an account integration: the site reads public addresses only. It does not see your RadioKing dashboard and cannot change anything there.

What stays in RadioKing, and what moves to the website

• RadioKing: everything you use it for today: the stream, and whatever automation, playlists and statistics you run there.
• RadioSiteMaker: the public website. Home page and persistent player, schedule grid, show pages, DJ profiles, podcasts (including RSS import), events, blog, charts, dedications, polls, chat, voice messages, contact form, donation links, and a custom domain with SSL. Ten themes, seventeen site languages.

The website schedule is entered on the website; it does not sync from RadioKing.

RadioKing's own website add-on: when it is enough

RadioKing sells a Radio Website add-on at $44 / 39€ / £34^[1] per month, or $468 / 408€ / £348^[2] per year. RadioKing lists these features for it: Player bar on all pages; podcasts module; show grid (Shows & Hosts); 'What's this track?'; multiple admins; 100 GB monthly traffic; 5 GB storage; external streams allowed^[3]. A RadioSiteMaker website is $99 a year + tax, billed separately from your stream host.

RadioKing's add-on is the better fit if:

• you want the website managed in the same RadioKing account as your stream, with one supplier;
• its listed features (player bar on every page, podcasts, show grid) cover what you need;
• you are staying with RadioKing for the long term.

A RadioSiteMaker site is the better fit if:

• you need things beyond the features RadioKing lists for its add-on, such as DJ profiles, events, blog, charts, dedications, polls, chat, voice messages and donation links, in the same site;
• you want the site to stay put if you change stream host later: you paste a new stream URL and the website, domain and content stay the same;
• you want the lower yearly price.

If you are thinking of leaving RadioKing entirely rather than adding a website, see RadioKing alternatives.

Frequently Asked Questions

Which RadioKing URL should I use?

Use the play.radioking.io address with your station's slug if you have one. The site then reads track, artist and cover from RadioKing's widget API. A numeric listen.radioking.com address also plays, but the site can only read titles carried inside the stream and finds covers through iTunes Search.

Why does my numeric RadioKing URL show no song title?

For numeric addresses the site cannot use RadioKing's API, because that API is keyed by the slug and there is no public lookup from id to slug. It reads the titles inside the stream instead, so if the stream carries none, nothing comes back. Switching to the play.radioking.io slug address fixes it.

Do I have to cancel RadioKing to use RadioSiteMaker?

No. RadioSiteMaker is a website and plays your existing RadioKing stream. RadioKing keeps doing the streaming and automation, and you pay for each service separately.

Does RadioSiteMaker need my RadioKing login?

No. It reads your public stream and RadioKing's public widget endpoint. It cannot see or change anything in your RadioKing account.

Is RadioKing's website add-on more expensive?

At the prices we checked, the add-on is listed at $468 / 408€ / £348 per year, against $99 a year plus tax for RadioSiteMaker. The add-on can still be the simpler choice if you want the website in the same account as your stream.