Shoutcast hosting in 2026: what it is, what it costs, and what replaced it

Shoutcast is the piece of software that made internet radio a thing normal people could do. It shipped with Winamp in 1999, it worked, and a quarter of a century later the phrase “Shoutcast hosting” still means the same thing it did then: renting a slot on somebody’s streaming server. This guide is the honest state of it in 2026 — what a Shoutcast server does, where it stops, why the tier is so cheap, and what actually happens if you move a Shoutcast station somewhere modern (short version: your encoder almost certainly comes with you).

1. What a Shoutcast server actually does

Shoutcast’s server component — the DNAS, for Distributed Network Audio Server — does exactly one job, and does it well. It accepts a single incoming audio feed from a broadcaster, and re-sends that same audio to everybody who asks for it. One in, many out. That is the whole design.

“Shoutcast hosting”, then, is a company running DNAS instances and renting you one: a hostname, a port, a source password, and a listener limit. You point an encoder at it, listeners point a player at the resulting URL, and the counter in the admin panel tells you how many of them there are. Everything else a modern station has — automation, scheduling, a public page, apps, analytics beyond a live count — is either a bolt-on the host adds around the DNAS, or it is not there.

2. Shoutcast vs Icecast, honestly

These two are the reason the same station can be described as “Shoutcast hosting” by one provider and “Icecast hosting” by the next. They solve the same problem and arrived from opposite directions.

The practical consequence is the good news of this whole article: encoders speak both. BUTT, Mixxx, SAM Broadcaster, RadioDJ, RadioBoss and virtually every hardware encoder can push to either. So can Virtual DJ, with one wrinkle worth knowing — its Icecast login sends the standard source username on the wire whatever you type in the box, which is a common cause of “my password is right and it still won’t connect”.

3. What Shoutcast hosting gets you — and where it stops

A DNAS slot is a genuinely complete answer to one question: how do I get one audio feed to many listeners? Everything below is what stations discover they also needed.

• The stream stops when your source stops. A DNAS has no library of its own. Close the encoder, reboot the studio PC, lose the home internet — the station is silence until you come back. Cloud automation exists to make that impossible.
• One bitrate for everybody. A single stream means the listener on patchy mobile data gets the same file as the listener on fibre, and drops out. Adaptive delivery (HLS) is what fixed that, and a DNAS does not do it.
• Stats are a live counter. Current listeners, maybe peak. Where they were, what they listened to, which show held them — that is a different class of tool.
• No compliance help. Nothing in a DNAS knows or cares that you played the same artist four times in an hour. If you broadcast commercial music in the US under the statutory licence, that rule is yours to keep.
• AutoDJ, where offered, is a bolt-on. Panel AutoDJs typically shuffle an uploaded folder on a schedule. That is not the same animal as rotation rules, clocks and dayparted programming — see rule-based rotation for the difference in practice.
• No listener-facing surfaces. A public page, an embeddable player, smart-speaker and directory listings, a branded app — all of those are things you would build or buy separately.

4. “Shoutcast hosting with AutoDJ”, decoded

It is one of the most-typed variants of the phrase, and reasonably so: an always-on station needs something playing when you are not. But AutoDJ means two very different products depending on where it lives.

If the plan is a station that runs 24/7 and sounds programmed rather than shuffled, the automation is the product and the stream server is plumbing. That is the inversion the last decade performed on this category.

5. Moving a Shoutcast station without losing listeners

The migration is less work than people fear, and the fear is usually about the wrong thing. Your encoder is portable. Your URL is the thing with roots.

1. 1Repoint the encoder. Nobex speaks the standard Icecast source protocol, so BUTT, Mixxx, SAM, RadioDJ, OBS, Virtual DJ or your hardware box connects with new host, port, mount and password — no new software. The one rule: your encoder’s codec and bitrate must match a configured mount, or the source is dropped after a few seconds.
2. 2Upload the library. The folder your panel AutoDJ shuffled becomes a real library with playlists and rotation rules behind it. This is the step where most stations discover they can finally program properly.
3. 3Take both new URLs. You get a plain MP3/Icecast stream — the direct replacement for your Shoutcast link, and the one hardware radios and directories want — plus an adaptive HLS stream for phones and browsers.
4. 4Re-issue the old link everywhere it lives. Directory listings, your website’s embedded player, smart-speaker entries, the link in your social bios, the bookmark you sent your mum. Make the list before you switch; it is always longer than you think.
5. 5Run both for a week. Keep the old server alive while the new URL propagates through directories, then retire it. Nothing about this needs to be dramatic.

6. Shoutcast hosting, asked and answered