How to Set Max Listener Slots on a SHOUTcast Server (August 2026)

If you run a SHOUTcast server, the max listener slots setting controls how many people can tune in to your stream at the same time. Set it too low and listeners get a “server full” message. Set it too high and your server chokes under bandwidth pressure. I have walked through this exact setting on dozens of SHOUTcast DNAS installs, and the truth is most guides skip the technical details that actually matter.

In this guide, I will show you how to set max listener slots on a SHOUTcast server using two methods: the web-based setup wizard and the sc_serv.conf file. You will also learn the bandwidth math behind the number, default limits, and what to do when your slots fill up.

What Are Listener Slots on a SHOUTcast Server?

Listener slots are the maximum number of concurrent (simultaneous) connections your SHOUTcast DNAS server will accept at one time. Each slot represents one active audio stream being delivered to one listener’s player or browser.

The official SHOUTcast documentation calls this the MaxListeners parameter. When all slots are taken, any new connection attempt is rejected until a slot frees up. That is the moment your audience hears the dreaded “server is currently full” message in Winamp, VLC, or their browser.

Listener slots protect your server from being overwhelmed and help you control bandwidth costs. On shared hosting, they also tie directly to your monthly plan tier.

Default and Maximum Limits You Should Know

Out of the box, SHOUTcast DNAS sets a default MaxListeners value of 32. That number comes up over and over on Reddit’s r/pirateradio and r/selfhosted communities, and it frustrates anyone trying to grow an audience past a small circle of friends.

The hard ceiling depends on your build. The official SHOUTcast DNAS GUI caps the field at 512, but the sc_serv.conf file accepts much higher values. Forum testing suggests the real-world practical maximum sits around 1024 before socket and resource exhaustion starts causing dropouts.

Here is the quick reference table I use when planning a deployment:

• Default: 32 listeners

• GUI maximum: 512 listeners

• Config file maximum: up to 1024 (practical)

• Home internet typical ceiling: 4 to 15 listeners

How to Set Max Listener Slots via the SHOUTcast Setup Wizard

The setup wizard is the friendliest way to set max listener slots on a SHOUTcast server, especially if you are new to DNAS. When you first launch sc_serv.exe (Windows) or sc_serv (Linux), your browser opens to http://your-server-ip:8000.

Follow these steps to change the max listeners through the wizard:

1. Open http://your-server-ip:8000 in your browser.

2. Click the Setup link at the top right of the page.

3. Enter your admin password when prompted (this is the password you set during initial install).

4. Scroll to the Maximum Listeners field on the configuration form.

5. Type your desired number (for example, 100 for a small station, 500 for a busy one).

6. Click Apply Settings at the bottom of the page.

7. Restart the SHOUTcast DNAS service for the change to take full effect.

The wizard writes your new value into sc_serv.conf automatically. I recommend noting the number you chose in a separate file so you do not forget it later when you revisit the config.

What Happens After You Click Apply

SHOUTcast does not require a full restart in every build, but I have found a clean restart prevents edge cases where the old listener count shows up in the /7.html status page. Give the server about 10 seconds after restarting before testing with a listener client.

How to Set MaxListeners via the sc_serv.conf File?

Editing the config file directly is the method most technical users prefer. It gives you full control past the 512 GUI cap and lets you script deployments. This is also the only method that works if you are managing SHOUTcast over SSH without a desktop.

Here is how to set max listener slots on a SHOUTcast server through the config file:

1. Stop the SHOUTcast DNAS service: ./sc_serv /tmp/sc_serv.conf or via your service manager.

2. Open sc_serv.conf in your editor of choice (nano, vim, Notepad++).

3. Find the line that reads MaxListeners=32.

4. Replace the number with your desired value, for example MaxListeners=250.

5. Save the file.

6. Restart SHOUTcast DNAS with the updated config.

7. Verify the change by visiting http://your-server-ip:8000/7.html and checking the Stream Max listeners field.

If your file does not have a MaxListeners line, add one in the server configuration block. The line must use the equals sign with no spaces around it, and the value must be a whole positive integer.

Sample sc_serv.conf Snippet

; SHOUTcast DNAS configuration
portbase=8000
adminpassword=your_admin_password
password=your_source_password
MaxListeners=250
streampath=/stream

That MaxListeners=250 line is the single change you need for the config file method. Everything else in this snippet is the standard minimum setup for a working stream.

Bandwidth and Listener Slots: The Formula You Need

Here is the formula competitors leave out. Your required upload bandwidth equals your bitrate multiplied by your max listeners, with a safety margin:

Required Mbps = (Bitrate in kbps × MaxListeners) / 1000 × 1.2

The 1.2 multiplier adds a 20% buffer so your stream stays smooth under burst conditions. For a 128 kbps MP3 stream at 100 listeners, you need roughly 15.4 Mbps of steady upload. That is why home connections cap out around 4 to 15 listeners before they choke.

If you stream in AAC+ at 64 kbps, the math looks much friendlier. 100 listeners at 64 kbps only needs about 7.7 Mbps, which makes hosted servers and high-quality home fiber viable for medium-sized stations.

Quick Bandwidth Cheat Sheet

• 64 kbps × 100 listeners = 7.7 Mbps upload

• 128 kbps × 100 listeners = 15.4 Mbps upload

• 192 kbps × 250 listeners = 57.6 Mbps upload

• 320 kbps × 500 listeners = 192 Mbps upload (hosted only)

If your max listener count exceeds your available bandwidth, you will see buffering, dropouts, and connection refusals long before you actually run out of slots.

Choosing the Right Number of Slots for Your Station

The right number of slots depends on three things: your audience size, your bitrate, and your budget. Most independent stations start between 50 and 100 slots and never need to grow. Anything above 500 almost always means you should be paying for a hosted SHOUTcast plan.

Here is the rule of thumb I share with our team’s clients: pick the listener count that matches 1.5x your average concurrent audience. That headroom absorbs traffic spikes during live shows without forcing you to overpay for bandwidth you rarely use.

If you do not know your current audience yet, start with 50. You can always raise the MaxListeners value later, and the change takes effect on the next SHOUTcast restart.

Home Server vs Hosted SHOUTcast Server

Home servers work great for 1 to 15 listeners, especially on cable or fiber with symmetric upload. Beyond that, you are competing with your own household for bandwidth every time someone streams Netflix.

Hosted SHOUTcast servers (like the plans we offer at Free Stream Hosting) give you dedicated bandwidth, public IP addresses, and listener counts from 50 up to several thousand. For any station expecting more than 25 concurrent listeners, hosting is the safer choice.

Troubleshooting Full Listener Slot Issues

Even with the right max listener count configured, slots fill up. Here is the troubleshooting checklist I use when a station is reporting “server full” errors:

1. Check the live status page at /7.html to confirm your current listener count matches your MaxListeners value.

2. Confirm the config file change took effect by restarting the SHOUTcast service, not just reloading the page.

3. Verify your upload bandwidth can actually sustain your bitrate multiplied by listener count.

4. Look for stuck connections by checking the server log for repeated connection attempts from the same IP.

5. Test with a second source client to rule out a single encoder blocking other listeners.

6. Increase MaxListeners by 25% if you regularly hit the cap during peak shows.

If your slots are filling up consistently, the fix is rarely “add more slots.” The fix is usually better bitrate selection or a hosted plan with more bandwidth. Adding slots to an underpowered server just pushes the failure one step further down the chain.

Frequently Asked Questions

Conclusion

Setting max listener slots on a SHOUTcast server comes down to one parameter, MaxListeners, controlled through the setup wizard or sc_serv.conf. Match the value to your audience size, your bitrate, and your upload bandwidth, and restart the service after every change. Done that way, your station will handle growth without ever showing the dreaded “server full” message again.