{"id":3398,"date":"2026-09-26T08:58:21","date_gmt":"2026-09-26T08:58:21","guid":{"rendered":"https:\/\/www.ucartz.com\/blog\/?p=3398"},"modified":"2026-09-26T08:58:23","modified_gmt":"2026-09-26T08:58:23","slug":"how-to-run-a-24-7-radio-station-with-azuracast","status":"publish","type":"post","link":"https:\/\/www.ucartz.com\/blog\/how-to-run-a-24-7-radio-station-with-azuracast\/","title":{"rendered":"How to Run a 24\/7 Radio Station With AzuraCast"},"content":{"rendered":"\n

Starting an internet radio station used to mean sitting at a computer for hours, manually queuing up songs, and hoping nothing crashed while you slept. AzuraCast changes that equation entirely. With the right setup, your station can broadcast continuously, day and night, without anyone touching a keyboard. The real work isn’t in babysitting the stream. It’s in getting the foundation right: your music library, your playlists, and the automated systems that keep everything moving.<\/p>\n\n\n\n

If you’ve logged into your AzuraCast radio hosting<\/a> dashboard and seen sections like Media, Playlists, Broadcasting, and AutoDJ, you already have everything you need. What matters now is understanding how these pieces fit together.<\/p>\n\n\n\n

Start by Confirming Your Station Is Actually Running<\/h2>\n\n\n\n

Before touching anything else, open your station dashboard and look at what’s active. You’re checking for a few specific things:<\/p>\n\n\n\n

The Broadcasting Service, usually Icecast, should show as Running. This is the piece of software that actually pushes your audio out to listeners across the internet. Without it, nothing you upload or schedule will ever reach an audience.<\/p>\n\n\n\n

The AutoDJ Service, typically powered by Liquidsoap, should also show as Running. This is the automation layer, the part that decides what plays next without human input.<\/p>\n\n\n\n

You’ll also see a Local Stream address, something like a .mp3 URL tied to your station, and a link to your station’s Public Page.<\/p>\n\n\n\n

If both the Broadcasting Service and AutoDJ Service are running, your infrastructure is ready. That’s the hard part done. Everything from here is about content and configuration.<\/p>\n\n\n\n

One important habit to build early: if your station shows as Offline, resist the urge to immediately start troubleshooting your playlists. Check the AutoDJ service status first. A huge percentage of “why isn’t my station playing” problems trace back to AutoDJ simply not running, not to anything wrong with your music files.<\/p>\n\n\n\n

Building Your Music Library<\/h2>\n\n\n\n

Once you’ve confirmed the technical side is functioning, move to Media, then Music Files, and start uploading.<\/p>\n\n\n\n

This step sounds obvious, but it’s where a lot of new station owners undersell themselves. A handful of tracks might feel like enough to get started, but for a genuinely 24\/7 station, a small library becomes a problem fast. Listeners notice repetition quickly, and hearing the same twenty songs on a loop within an hour will drive people away just as fast as dead air would.<\/p>\n\n\n\n

Think in terms of a reasonably sized catalog, not a starter pack. This doesn’t mean you need thousands of tracks on day one, but the more variety you build in early, the less maintenance you’ll need later.<\/p>\n\n\n\n

It also helps to organize your uploads as you go rather than dumping everything into one folder. Common categories worth separating include:<\/p>\n\n\n\n

Music, as your core catalog
Commercials, for any sponsored or promotional audio
Station IDs, the short clips that identify your station by name
Jingles, for transitions and branding moments
Promos, for upcoming shows or features
Special programs, for anything outside your regular rotation<\/p>\n\n\n\n

There’s no single correct structure here. The right organization depends entirely on the sound and identity you’re building for your station. A talk-heavy station will organize very differently from a music-only stream.<\/p>\n\n\n\n

\"playlist<\/figure>\n\n\n\n

Creating and Populating Playlists<\/h2>\n\n\n\n

With your media uploaded, head over to Playlists. This is where your station’s actual programming takes shape.<\/p>\n\n\n\n

Start with something simple, a Main Rotation playlist that will carry the bulk of your airtime. From there, add the tracks you want AutoDJ to pull from.<\/p>\n\n\n\n

Depending on how much control you want over the listening experience, you can branch out into additional playlists such as Morning Music, Evening Music, Weekend Mix, News segments, or Station Promos. These separate playlists let you shape different moods or content types throughout the day rather than treating your entire catalog as one undifferentiated pool that plays in random order.<\/p>\n\n\n\n

This distinction matters more than it might seem at first. A station that just shuffles everything all day tends to feel unstructured, almost accidental. A station with deliberate playlists for different times or moods feels programmed, more like something a human curated, even though the actual playback is fully automated.<\/p>\n\n\n\n

After creating a playlist, the next step is adding the relevant files to it. This is genuinely where your station starts to have a personality. A main rotation playlist might hold anywhere from 100 to 500 songs, giving AutoDJ enough material to draw from continuously without repeating too often. The larger and better curated this pool is, the more natural your station will sound to a listener tuning in at any random hour.<\/p>\n\n\n\n

Don’t Forget to Activate the Playlist<\/h2>\n\n\n\n

Here’s a step that trips people up constantly: creating a playlist is not the same as making it live.<\/p>\n\n\n\n

After you’ve built out your playlist and added songs, you need to confirm it’s actually enabled and set to participate in your station’s AutoDJ rotation. It’s entirely possible to build a perfectly good playlist, populate it with dozens of tracks, and still have your station play nothing, simply because that playlist was never switched on.<\/p>\n\n\n\n

If your station is technically online, AutoDJ is running, Icecast is running, but no sound is actually coming through, this is one of the very first things to check. An inactive playlist means AutoDJ has nowhere to pull content from, even if the media itself exists in your library.<\/p>\n\n\n\n

Letting AutoDJ Do Its Job<\/h2>\n\n\n\n

Once your playlists are built and activated, the heavy lifting shifts entirely to AutoDJ. This is the part of the system that makes a true 24\/7 station possible in the first place.<\/p>\n\n\n\n

Liquidsoap, the software behind AzuraCast’s AutoDJ feature, handles the automated selection and playback of your content. Once everything upstream is configured correctly, it will continue running indefinitely, choosing tracks from your active playlists and streaming them out without requiring anyone to press play.<\/p>\n\n\n\n

This is the entire point of the setup. You’re not leaving a laptop open with a music player running in the background. You’re not manually starting each track every few minutes. The server itself carries the responsibility, which means your station keeps broadcasting whether you’re asleep, working another job, or simply away from your computer entirely.<\/p>\n\n\n\n

\"autoDJ<\/figure>\n\n\n\n

Testing Your Stream Before You Go Live<\/h2>\n\n\n\n

Before telling anyone to tune in, test everything yourself.<\/p>\n\n\n\n

Your dashboard will provide a local stream URL, something along the lines of a link ending in radio.mp3. Open this in a compatible audio player, or simply use your station’s public page, and listen critically.<\/p>\n\n\n\n

A few things worth confirming during this test:<\/p>\n\n\n\n

Audio is actually playing when you open the stream
Songs transition automatically without needing intervention
There are no unexpected long stretches of silence
Metadata, like song titles and artist names, is displaying correctly
The stream stays connected rather than dropping intermittently<\/p>\n\n\n\n

Your dashboard’s Now Playing section is a useful reference point here too, since it shows what AzuraCast currently believes is airing. Comparing that against what you’re actually hearing is a quick sanity check.<\/p>\n\n\n\n

Reviewing Your Public Radio Page<\/h2>\n\n\n\n

AzuraCast automatically generates a public-facing page for your station, accessible through the Public Pages section of your dashboard. This is the simplest way for listeners to access your stream without needing to hunt down a raw URL.<\/p>\n\n\n\n

Before sharing this page with anyone, open it yourself and walk through it as if you were a first-time listener. Check that the station name displays correctly, that the embedded player actually functions, and that current song information is showing up as expected. Confirm the station isn’t mistakenly displaying as offline, and take a moment to review your branding, since this page is often the first impression a new listener gets of your station.<\/p>\n\n\n\n

\"azuracast<\/figure>\n\n\n\n

Adding Scheduling for More Control<\/h2>\n\n\n\n

A single rotating playlist is enough to keep a station running around the clock, but scheduling opens up a more deliberate listening experience.<\/p>\n\n\n\n

A common structure might look something like:<\/p>\n\n\n\n

Morning playlist from 6am to 10am
Main rotation from 10am to 2pm
Afternoon playlist from 2pm to 6pm
Evening programming from 6pm to 10pm
Overnight playlist from 10pm to 6am<\/p>\n\n\n\n

This kind of time-based structure gives your station a rhythm that feels intentional rather than random, even though it’s all still fully automated behind the scenes.<\/p>\n\n\n\n

\"scheduling<\/figure>\n\n\n\n

Ongoing Monitoring<\/h2>\n\n\n\n

Getting your station live isn’t the finish line. Once everything is running, it’s worth checking in periodically rather than assuming it will stay perfect indefinitely.<\/p>\n\n\n\n

Your dashboard offers several sections built for exactly this. The Overview page shows current listeners, playback status, and general station health. Reports give you a broader picture of listening activity over time. Logs are invaluable when something behaves unexpectedly, often revealing the root cause faster than manual troubleshooting would. And the Public Pages section lets you confirm, at a glance, that listeners can actually reach your station without issue.<\/p>\n\n\n\n

If your station suddenly stops playing, Logs should be the first place you look.<\/p>\n\n\n\n

Troubleshooting an Offline Station<\/h2>\n\n\n\n

If your dashboard shows your station as Offline, work through the possibilities in order rather than jumping straight to conclusions.<\/p>\n\n\n\n

Check whether AutoDJ is running. Check whether the Broadcasting Service is running. Confirm your playlist actually contains playable audio. Confirm that playlist is enabled. Try opening the stream URL directly. Look through your Logs for any visible errors. And check whether AutoDJ is actively selecting and playing a track at that moment.<\/p>\n\n\n\n

A common mistake is assuming the fix is simply uploading more music. In most cases, the real issue lies somewhere in configuration, whether that’s an inactive playlist, a stopped service, or a broken connection, not a lack of content.<\/p>\n\n\n\n

The Basic Workflow, Start to Finish<\/h2>\n\n\n\n

Running a 24\/7 AzuraCast station follows a simple sequence: upload your music, create a playlist, add songs to it, enable the playlist, let AutoDJ take over, and let Icecast deliver the stream to listeners.<\/p>\n\n\n\n

If your dashboard already shows Liquidsoap AutoDJ running and Icecast Broadcasting running, your core infrastructure is already in place. From there, your remaining work is really about curation, organization, and making sure every piece stays properly connected.<\/p>\n\n\n\n

Final Checklist<\/h2>\n\n\n\n

Before calling your station “24\/7 ready,” verify:<\/p>\n\n\n\n