Running your own internet radio station is more accessible than ever. With the right VPS specs needed to self-host a radio server, you can broadcast to listeners worldwide for a fraction of what commercial hosting charges. I have helped dozens of community stations and hobbyists set up their own streams, and the difference between a smooth 24/7 broadcast and a frustrating mess almost always comes down to picking the right VPS configuration from the start.
In this guide, I will walk you through exactly what hardware you need, how to calculate bandwidth for your listener count, and how to install AzuraCast, the most popular self-hosted radio platform. I will also cover the legal side of internet radio, which most guides completely ignore. By the end, you will know whether a 1GB VPS can handle your project or whether you need to scale up to dedicated resources.
Table of Contents
- What VPS Specs Are Needed to Self-Host a Radio Server
- Understanding the Key Components of a Radio VPS
- Minimum vs Recommended VPS Requirements Compared
- How to Calculate Bandwidth for Radio Streaming
- How to Install AzuraCast on Your VPS
- Setting Up AutoDJ and Live Broadcasting
- Self-Hosted vs Commercial Radio Hosting
- Legal Considerations for Internet Radio
- Frequently Asked Questions About VPS Radio Servers
- Getting Started With Your Radio Server
What VPS Specs Are Needed to Self-Host a Radio Server
The short answer: a minimum of 1 CPU core, 1GB RAM, and 20GB storage works for a small hobby station with up to 50 listeners. For a community radio serving 100 to 500 simultaneous listeners, you need 2 CPU cores, 2GB RAM, 50GB SSD storage, and at least 5TB monthly bandwidth. Professional stations broadcasting to thousands of listeners typically require 4+ cores, 8GB RAM, and 10TB+ bandwidth.
| Station Type | CPU | RAM | Storage | Bandwidth | Listeners |
|---|---|---|---|---|---|
| Hobby / Personal | 1 core | 1 GB | 20 GB SSD | 2 TB/month | Up to 50 |
| Small Community | 2 cores | 2 GB | 50 GB SSD | 5 TB/month | 50 – 200 |
| Active Community | 2 cores | 4 GB | 80 GB SSD | 8 TB/month | 200 – 500 |
| Professional | 4 cores | 8 GB | 160 GB NVMe | 15+ TB/month | 500 – 2,000 |
| Multi-Station Hub | 8 cores | 16 GB | 320 GB NVMe | 25+ TB/month | 2,000+ |
VPS specs by listener count for self-hosted radio servers in 2026
These numbers come from real-world deployments documented on the AzuraCast GitHub discussions and the official AzuraCast requirements page. The official recommendation is 4 CPU cores and 4GB RAM for production use, but I have run stable streams on 2GB instances serving 100 concurrent listeners with 128kbps MP3 streams.
Bandwidth is the spec most beginners underestimate. Each listener consumes the full bitrate of your stream continuously while connected. A 128kbps stream means 128 kilobits per second for every active listener, every second. We will break down the exact math in a dedicated section below.
Understanding the Key Components of a Radio VPS
Before we dive deeper into specifications, let me clarify the terminology you will encounter. These definitions will help you make informed decisions when comparing VPS providers and radio software.
VPS (Virtual Private Server) is a virtualized slice of a physical server that gives you dedicated CPU, RAM, and storage. Unlike shared hosting, you have root access and can install any software, including radio streaming applications.
AzuraCast is the leading open-source self-hosted radio management platform. It combines Icecast (or Shoutcast), Liquidsoap, and a web dashboard so you can run your entire station through a single interface. Most VPS specs needed to self-host a radio server assume you are running AzuraCast.
Icecast and Shoutcast are the two main streaming server protocols. Icecast is open-source and supports OGG, MP3, and AAC. Shoutcast is more limited but has wider compatibility with older players. AzuraCast supports both, with Icecast being the default.
Liquidsoap is the audio routing engine underneath AutoDJ. It handles playlist rotation, crossfading between tracks, live DJ integration, and stream encoding. You typically never interact with Liquidsoap directly when using AzuraCast.
AutoDJ is the automation mode that plays your pre-loaded music library when no live DJ is connected. It keeps your station broadcasting 24/7 even when nobody is at the controls.
Minimum vs Recommended VPS Requirements Compared
Let me break down each specification so you understand exactly why each matters for radio streaming. The difference between minimum and recommended specs is mostly about headroom for growth.
CPU Cores and Clock Speed
CPU handles audio encoding and stream processing. Modern AzuraCast installations use Liquidsoap to encode audio on the fly, which is CPU-intensive. A single modern core can typically handle 100 to 200 listeners at 128kbps MP3, but this depends heavily on the processor generation.
For a hobby station, 1 core is fine. For anything beyond 100 listeners, invest in 2+ cores with a base clock of 2.5GHz or higher. Overpowered single-core performance matters more than core count for small stations.
RAM Requirements
RAM holds the active playlist, listener analytics, and Docker containers. AzuraCast itself uses around 600MB to 800MB at idle, plus additional memory for each running station and connected listener’s metadata.
The 1GB minimum is tight. The 2GB sweet spot is what most community stations use. If you plan to run other services on the same VPS (like a website or Nextcloud), budget 4GB or more.
Storage Type and Size
SSD beats HDD every time for radio servers because of faster file reads during playback. NVMe is ideal but not strictly required. Plan for at least 50GB to accommodate a reasonable music library plus operating system and Docker images.
A typical MP3 file is 8 to 12MB. A 320GB VPS holds roughly 30,000 to 40,000 tracks, which is more than enough for most stations. Lossless FLAC files are 4 to 5 times larger, so adjust accordingly.
Bandwidth and Port Configuration
Bandwidth is the data transferred between your VPS and listeners. Most VPS providers advertise monthly bandwidth allowances. Exceeding these limits results in throttling or overage fees.
Open the following ports on your VPS firewall: 80 (HTTP), 443 (HTTPS), and 8000 (default AzuraCast stream port). Some providers like Oracle’s free tier block port 8000 by default, which is a common frustration mentioned in the Reddit selfhosted community.
How to Calculate Bandwidth for Radio Streaming
Here is the formula that every radio admin should know: monthly bandwidth = bitrate x listeners x seconds per month, divided by 8 to convert bits to bytes. A 128kbps stream running continuously for one listener uses about 41GB of data per month.
Let me put real numbers to this. If you have 100 listeners on a 128kbps MP3 stream running 24/7, your monthly bandwidth consumption is approximately 4.1TB. Bump to 256kbps for higher quality audio, and that jumps to 8.2TB per month for the same 100 listeners.
Quick Bandwidth Calculator Examples
- 50 listeners, 128kbps, 24/7 = 2 TB/month
- 100 listeners, 128kbps, 24/7 = 4.1 TB/month
- 200 listeners, 192kbps, 24/7 = 12.3 TB/month
- 500 listeners, 256kbps, 24/7 = 41 TB/month
Most low-cost VPS providers offer 1 to 5TB monthly bandwidth, which works for hobby and small community stations. If you plan to scale beyond 200 listeners, look for providers that offer 10TB+ or unmetered bandwidth, such as OVH, Hetzner, or BandwagonHost.
One trick to reduce bandwidth: use a CDN. Services like Cloudflare Stream can front your stream and dramatically reduce direct bandwidth on your VPS. However, this adds complexity and cost, so it only makes sense above 500 concurrent listeners.
How to Install AzuraCast on Your VPS
The fastest way to get a self-hosted radio server running is the Docker installation, which AzuraCast officially supports. I will walk you through both the Docker and non-Docker methods.
Step 1: Prepare Your VPS
Choose a VPS running Ubuntu 22.04 or Debian 12. These are the best-supported operating systems for AzuraCast. Make sure your server has at least 2GB RAM and Docker-compatible virtualization enabled (most providers handle this automatically).
Connect to your server via SSH as root: ssh root@your-server-ip. Update your system packages first with apt update && apt upgrade -y.
Step 2: Install Docker and Docker Compose
AzuraCast requires Docker. Install it with the official convenience script: curl -fsSL https://get.docker.com | sh. Then install Docker Compose separately, as AzuraCast uses its own Compose version.
Verify the installation by running docker --version. You should see a version number of 20.10 or higher.
Step 3: Install AzuraCast
Run the official AzuraCast installation command: curl -L https://azuracast.com/install.sh | bash. The script installs all necessary components, including AzuraCast, Liquidsoap, Icecast, and the web interface. The installer takes 5 to 10 minutes to complete.
For non-Docker installation, the script offers a --no-docker flag, but this requires manual setup of all dependencies. The Docker method is strongly recommended for beginners and is what 95% of the community uses.
Step 4: Initial Setup Wizard
Once installation completes, open your browser and navigate to http://your-server-ip. The setup wizard walks you through creating your admin account and configuring your first station. Set a strong password and enable two-factor authentication immediately.
Default ports: AzuraCast uses port 80 for the main dashboard, 443 for HTTPS, and 8000 for the actual audio stream. If you reverse proxy through Nginx, you can map these to standard ports.
Setting Up AutoDJ and Live Broadcasting
Once AzuraCast is running, you have two broadcasting modes: AutoDJ for automated playback and Live DJ for real-time streaming. Most stations use both, switching between them based on scheduling.
Configuring AutoDJ
AutoDJ lets you upload music files and create intelligent playlists that rotate around the clock. Upload your MP3 files through the web interface under the Media menu, then create playlists with weighted rotation. Tracks with higher weight play more frequently.
Enable crossfading between tracks for a professional sound. The default crossfade duration of 2 seconds works well for most genres. Enable “fade in” and “fade out” on each track to prevent audio pops.
Live DJ Streaming
Live DJs broadcast using Icecast source clients like BUTT (Broadcast Using This Tool) or Mixxx. Configure a mount point in AzuraCast, share the credentials with your DJ, and they can stream from anywhere with an internet connection.
Set a “disconnect after silence” timeout of 5 to 10 seconds so AutoDJ takes over automatically if the DJ disconnects unexpectedly. This prevents dead air during your broadcast.
Playlist Management Tips
Schedule playlists by time of day for variety. Many stations run energetic music in the morning and ambient tracks at night. Use the scheduler under Playlists to assign different rotations to different time slots.
Enable request lines so listeners can request songs from your library. Set a cooldown period of 30 to 60 minutes so the same song is not requested repeatedly.
Self-Hosted vs Commercial Radio Hosting
Before committing to a VPS, you should understand the trade-offs between self-hosting and using a commercial radio hosting service like Live365, Radio.co, or Shoutcast’s own platform.
Cost Comparison
A self-hosted VPS with 2 CPU cores, 2GB RAM, and 5TB bandwidth typically costs $10 to $20 per month. Commercial hosting starts at $15 to $30 per month for similar listener capacity, but limits you to their platform and features.
Self-hosting is cheaper at scale. Once you exceed 500 listeners, commercial hosting costs skyrocket to $100+ per month, while your VPS costs stay relatively flat. The break-even point is around 200 listeners for most providers.
Control and Customization
Self-hosting gives you complete control over every aspect of your station. You own your data, can install custom plugins, and are not subject to platform changes or shutdowns. Commercial platforms restrict customization but offer easier setup.
If you are not comfortable with Linux command lines and Docker, commercial hosting is the better choice. If you want full control and have basic sysadmin skills, self-hosting wins on every metric except convenience.
Reliability and Uptime
Commercial hosts typically offer 99.9% uptime guarantees with redundant infrastructure. Self-hosted VPS uptime depends on your provider. Tier 1 providers like DigitalOcean, Vultr, and Hetzner offer comparable reliability.
Set up uptime monitoring with a free service like UptimeRobot. Configure alerts so you know within minutes if your stream goes down.
Legal Considerations for Internet Radio
This is the section almost every other guide skips, and it is the one that can get your station shut down. Internet radio is heavily regulated, and the rules vary by country. I am not a lawyer, but here is what you need to know based on community experience.
Music Licensing and Royalties
Playing copyrighted music without a license is illegal in most jurisdictions and exposes you to DMCA takedowns and lawsuits. In the US, you need licenses from SoundExchange (for digital performance royalties) and ASCAP, BMI, or SESAC (for songwriter royalties).
Commercial stations purchase blanket licenses through organizations like the Radio Music License Committee. Hobby stations often overlook this, but technically the same rules apply. Royalty-free music, Creative Commons tracks, or public domain recordings are safer alternatives for non-commercial use.
Country-Specific Rules
In the UK, you need a PRS for Music license and an MCPS license. In the EU, rules vary by country but generally require collection society registration. Some countries like Canada have specific low-power streaming exemptions for small community stations.
Research your local laws before going live. The cost of proper licensing is far less than the cost of defending a copyright infringement claim.
Operator Identification Requirements
Many jurisdictions require you to publish the station owner’s name, contact information, and licensing authority on your stream page. AzuraCast makes this easy through the station profile settings. Add your information under Station Settings > Public Profile.
Keep records of your music library and licenses for at least 3 years. If a dispute arises, you need to prove you had the right to broadcast each track.
Frequently Asked Questions About VPS Radio Servers
Can you self host a VPS for a radio server?
Yes, you can self-host a VPS to run a radio server. Choose a VPS with at least 1 CPU core, 1GB RAM, 20GB SSD storage, and 2TB monthly bandwidth for a small station. Install AzuraCast using Docker, configure your music library, and start broadcasting. The VPS gives you root access to install any radio software including Icecast, Shoutcast, or AzuraCast.
What are the hardware requirements for a VPS radio server?
For a hobby station serving up to 50 listeners, you need 1 CPU core, 1GB RAM, 20GB SSD, and 2TB bandwidth. A small community station with 50 to 200 listeners requires 2 CPU cores, 2GB RAM, 50GB SSD, and 5TB bandwidth. Professional stations with 500+ listeners need 4+ cores, 8GB RAM, NVMe storage, and 15TB+ monthly bandwidth. CPU speed matters more than core count for audio encoding.
Is it legal to make your own internet radio station?
Yes, it is legal to make your own internet radio station in most countries, but you must license the music you play. In the US, you need licenses from SoundExchange for performer royalties and ASCAP, BMI, or SESAC for songwriter royalties. EU and UK broadcasters require similar collection society licenses. Royalty-free music and Creative Commons tracks are legal alternatives for non-commercial stations. Always research your local laws before going live.
What equipment do I need to broadcast online radio?
To broadcast online radio you need a VPS with the specs listed above, a domain name (optional but recommended), radio streaming software like AzuraCast, a music library, and an SSL certificate for HTTPS. For live DJ broadcasting, you also need broadcasting software like BUTT or Mixxx, a quality microphone, and audio interface. The VPS itself is the most expensive component, with costs ranging from $5 to $20 per month for most hobby stations.
Getting Started With Your Radio Server
You now have everything you need to choose the right VPS specs needed to self-host a radio server. Start by calculating your expected listener count, then multiply by your target bitrate to determine bandwidth needs. A 2-core, 2GB RAM VPS with 5TB bandwidth is the sweet spot for most stations launching in 2026.
My recommendation for your first deployment: pick a provider with hourly billing like Vultr or DigitalOcean, deploy the smallest plan that meets your listener targets, and test before committing to a longer contract. Install AzuraCast using the Docker method, configure AutoDJ with a small initial playlist, and broadcast for a few weeks before scaling up.
Once you have a stable stream, focus on the legal side. License your music properly, publish your operator information, and set up monitoring so you know the moment your stream goes down. The technical setup is the easy part. Building a legitimate, sustainable radio station takes ongoing attention to both technology and compliance.
Your VPS specs needed to self-host a radio server depend on your goals, but the rules in this guide apply whether you are running a hobby station for 50 friends or a community broadcaster serving thousands. Start small, monitor your actual usage, and scale up only when the data tells you to. Good luck with your station.