Switch from Wowza to Shoutcast Net: A Step-by-Step Migration for Broadcasters

If you’re running a radio station, DJ stream, podcast network, church broadcast, school radio station, or live event stream, you’ve probably felt the pain of Wowza’s expensive per-hour/per-viewer billing and the complexity that comes with multi-protocol streaming stacks. This guide walks you through a practical migration to Shoutcast Net so you can keep your audio live, stable, and affordable with a flat-rate unlimited model.

You’ll learn how to copy your key stream settings (codec, bitrate, metadata), set up your new server, configure common encoders (BUTT, Mixxx, OBS), enable AutoDJ for 24/7 fallback, and switch your players with minimal downtime.

Ready to start? Launch a 7 days trial and migrate without breaking your on-air schedule.

What you’ll get on Shoutcast Net

  • $4/month starting price (flat-rate hosting)
  • Unlimited listeners (plan-dependent, no per-viewer surprises)
  • 99.9% uptime infrastructure
  • SSL streaming for modern browsers
  • AutoDJ for 24/7 playback and failover
  • Works great when you need to stream from any device to any device

Table of contents

Why switch from Wowza to Shoutcast Net?

Wowza is powerful, especially if you need any stream protocols to any stream protocols (RTMP, RTSP, WebRTC, SRT, etc) for complex video workflows. But for broadcasters focused on dependable audio streaming (radio, DJ sets, talk, worship services, school announcements, and live events), that power often comes with higher cost, more moving parts, and billing that can spike when audiences grow.

Cost predictability vs. per-hour/per-viewer billing

One of the most common reasons to migrate is budgeting. With Wowza, costs can scale quickly because you may be paying by usage (per-hour) and sometimes effectively per audience size (per-viewer outcomes depending on your workflow). Shoutcast Net is built around a flat-rate unlimited model designed for broadcasters who want to grow without worrying that a viral moment will trigger an invoice shock.

Built for stations: SSL, unlimited listeners, AutoDJ, and stability

Shoutcast Net is optimized for radio-style delivery: reliable continuous streaming, metadata, easy encoder connections, and listener-friendly playback. You also get SSL streaming for modern browsers and embeds, 99.9% uptime, and the ability to run AutoDJ as a 24/7 backbone or fallback when your live encoder drops.

Better listener experience for audio-first broadcasts

For audio broadcasters, “fast to play” matters. Shoutcast Net is tuned for stable delivery across devices so you can truly stream from any device to any device—studio PCs, laptops, mobile encoders, DJ software, and web players. If you also do live video elsewhere, you can still Restream to Facebook, Twitch, YouTube from your production tools while keeping your audio stream consistent and cost-controlled.

Shoutcast Net vs Wowza (quick comparison)

Feature Wowza (typical) Shoutcast Net
Pricing style Often per-hour/per-viewer usage-based Flat-rate unlimited model, starting at $4/month
Audio broadcaster focus General-purpose streaming stack Purpose-built for radio, DJs, podcasters
Listener scaling Can increase cost as usage grows Unlimited listeners (plan-dependent; no per-viewer surprises)
Web compatibility Depends on setup SSL streaming supported
Failover Requires custom workflow Built-in AutoDJ option
Latency goals Varies widely by protocol/workflow Optimized for broadcaster delivery; many setups target very low latency 3 sec (encoder/player dependent)

Pro Tip

If you only need Wowza because you’re juggling multiple ingest/egress formats, consider splitting responsibilities: keep your advanced video workflow where it belongs, but move your 24/7 audio station to Shoutcast Net for predictable cost, simpler operations, and built-in AutoDJ. Then you can still Restream to Facebook, Twitch, YouTube from OBS while your audio stream remains stable.

Before you begin: migration checklist (streams, mountpoints, encoder)

A smooth migration is mostly preparation. Before you change anything, capture the settings that define your station sound and delivery: codec, bitrate, sample rate, mountpoint/path, metadata, and your current player URLs. This section gives you a checklist you can complete in 10–20 minutes.

1) Inventory your existing streams

Many broadcasters run more than one output: a high-quality stream for apps and a lower-bitrate stream for mobile. List each stream you currently publish on Wowza.

  • Stream name/label (e.g., “Main 128k”, “HQ 320k”, “Talk 64k”)
  • Codec (MP3 or AAC/AAC+)
  • Bitrate (64/96/128/192/320 kbps)
  • Sample rate (44.1 kHz or 48 kHz)
  • Channels (mono/stereo)
  • Mountpoint/path (if applicable)
  • Metadata source (encoder, automation, external script)
  • Current listener peak (so you choose the right plan)
  • Where it’s embedded (website pages, mobile app, smart speaker skill, TuneIn-like directories)

2) Confirm your encoder workflow

Identify how you go live today. Common setups include:

  • BUTT (simple, reliable “push-to-server”)
  • Mixxx (DJ software with built-in broadcasting)
  • OBS (often used for video; can send audio-only too)
  • Radio automation (SAM Broadcaster, RadioBOSS, StationPlaylist, etc.)
  • Remote contributors (mobile encoders, virtual mixers)

3) Decide your cutover method (no downtime vs quick switch)

You have two clean migration approaches:

  • Parallel run (recommended): run Shoutcast Net alongside Wowza, test everything, then update players and DNS at the final moment.
  • Direct cutover: stop Wowza ingest, point encoder to Shoutcast Net, then update players. Faster, but higher risk if a setting was missed.

4) Know what you’re moving (and what you’re not)

If you were using Wowza for complex protocol translation—any stream protocols to any stream protocols (RTMP, RTSP, WebRTC, SRT, etc)—note those workflows separately. Shoutcast Net is designed for broadcaster-friendly delivery and station operations. Many stations keep their video pipeline in OBS/RTMP while running a dedicated, stable Shoutcast audio stream for listeners.

Pro Tip

Before you touch your public players, do a private test: open the new Shoutcast Net stream URL on your phone (cellular) and on a desktop browser. If both start quickly and metadata updates correctly, your cutover will be easy—and you’ll be closer to that very low latency 3 sec feel (encoder/player settings determine the final delay).

Step 1: Start your Shoutcast Net server (7-day free trial)

First, create your new streaming server on Shoutcast Net. You can start with a 7 days trial so you can configure, test, and run a parallel stream before you switch your audience over.

Action: choose a plan that matches your station

If you’re migrating from Wowza because usage-based billing is getting out of hand, this is where Shoutcast Net shines. Plans start at $4/month and are designed for broadcasters who want predictable monthly cost, not per-hour/per-viewer surprises.

Pick the plan based on your expected listener concurrency and quality needs. If you’re unsure, choose a plan that covers your current peak and gives you room to grow—because on Shoutcast Net, growth doesn’t mean multiplying usage charges.

Useful links: Shoutcast hosting, Shop plans

Action: capture your new server credentials

Once your server is active, note the essentials (you’ll use these in Step 3):

  • Server hostname (e.g., stream.yourdomain.com or provided host)
  • Port (commonly 8000 or your assigned port)
  • Password (source/encoder password)
  • Stream type (Shoutcast/Icecast-compatible output options)
  • SSL (HTTPS) stream URL for secure web playback

Action: decide on your primary format

Most stations choose one of these:

  • MP3 (maximum compatibility, great for “press play” anywhere)
  • AAC/AAC+ (more efficient at lower bitrates; popular for mobile)

If your audience is broad and you want “it just works,” MP3 at 128 kbps is a classic. If you’re optimizing bandwidth, AAC+ at 48–64 kbps can sound surprisingly good.

Pro Tip

If you’re migrating a church or school station that relies on embedded web players, prioritize SSL streaming from day one. Modern browsers increasingly block or warn on mixed content, and HTTPS playback helps ensure listeners can start instantly across devices—helping you stream from any device to any device without support emails.

Step 2: Copy your Wowza stream settings (bitrate, codec, listeners)

Now you’ll translate what you already have on Wowza into a clean Shoutcast Net configuration. The goal is to keep the listener experience consistent: same quality, same metadata behavior, and a familiar player URL structure where possible.

Action: copy quality settings (codec/bitrate/sample rate)

From your Wowza application/stream configuration, note the output encoding details. Then match them on your encoder for Shoutcast Net:

  • Codec: MP3 or AAC
  • Bitrate: keep the same as your current “main” stream to avoid listener complaints
  • Sample rate: 44.1 kHz is standard for music; 48 kHz common for video/OBS workflows
  • Stereo/mono: music in stereo; talk can be mono to save bandwidth

Action: map your “mountpoints” and URLs

Wowza setups often use application names and stream files; Icecast-style setups use mountpoints (like /live or /stream). Shoutcast Net will provide stream URLs you can embed directly into players and apps.

If your existing website/app expects a specific path, plan your cutover so you can either:

  • Update the embed URL everywhere (best long-term), or
  • Use a redirect/proxy on your domain to keep legacy URLs working (useful when you can’t update an app quickly)

Action: confirm metadata behavior

Listeners expect “Now Playing” to update quickly. Verify where metadata is coming from:

  • Encoder metadata (common with DJ software and BUTT)
  • Automation metadata (RadioBOSS/SAM/StationPlaylist)
  • External metadata scripts (less common; note any dependencies)

In Shoutcast Net, metadata typically flows cleanly from your encoder. The key is to ensure your encoder is configured to send song titles and your station name.

Action: size for audience growth (without Wowza billing surprises)

On Wowza, a bigger audience can mean a bigger bill. On Shoutcast Net, you choose a plan that fits your expected concurrency and enjoy predictable cost. This is especially helpful for live events (sports, graduations, concerts) where listener spikes are normal.

Migration notes template (copy/paste)
- Current Wowza stream label:
- Codec:
- Bitrate:
- Sample rate:
- Stereo/Mono:
- Current public player URL:
- Where embedded (pages/apps):
- Peak listeners (last 30 days):
- Metadata source:
- Special notes (DSP, processing, delays, ads):

Pro Tip

If you’re currently using Wowza mainly to “convert” between formats—any stream protocols to any stream protocols (RTMP, RTSP, WebRTC, SRT, etc)—you can simplify: keep your production ingest in the tool that makes sense (often OBS/RTMP), then publish a dedicated Shoutcast audio stream for broad compatibility. It’s a cleaner path to unlimited listeners without usage-based cost spikes.

Step 3: Configure your encoder (BUTT/Mixxx/OBS) and test

With your Shoutcast Net server active and your Wowza settings documented, it’s time to connect your encoder and go live in a controlled test. The goal is to verify audio quality, stability, metadata, and playback on multiple devices.

Action: connect using BUTT (recommended for simplicity)

BUTT (Broadcast Using This Tool) is popular because it’s lightweight and reliable. Create a new server profile using your Shoutcast Net details:

  • Address: your Shoutcast Net hostname
  • Port: your assigned port
  • Password: your source password
  • Codec/Bitrate: match what you copied from Wowza
  • Metadata: enable “send song name” / “ICY metadata” if available
Example encoder values (typical music station)
Codec: MP3
Bitrate: 128 kbps
Sample Rate: 44.1 kHz
Channels: Stereo
Metadata: Enabled (Now Playing)

Action: connect using Mixxx (DJ streaming)

In Mixxx, open Preferences → Live Broadcasting and enter your Shoutcast Net server details. Choose the same bitrate/format you used on Wowza to maintain consistency for your audience.

If you’re a DJ doing transitions and mic work, do a 10-minute test recording locally while broadcasting—then listen back to confirm your levels and processing are right.

Action: connect using OBS (events and hybrid video workflows)

OBS is often used for events and worship streams. If you’re sending video to a platform, you can still run a dedicated audio stream in parallel so radio listeners get a stable experience. Many broadcasters use OBS to Restream to Facebook, Twitch, YouTube while Shoutcast Net powers the audio-only station feed.

For best results, treat Shoutcast as your “radio output” and keep your OBS output for video destinations. This separation improves reliability and avoids tying your audio station’s cost to video usage patterns.

Action: test playback and latency

Open your Shoutcast Net stream on:

  • Mobile on cellular (real-world listener conditions)
  • Desktop browser (check SSL playback)
  • Car audio/Bluetooth (common for radio audiences)
  • A second device to confirm metadata updates while you change tracks

If your setup supports it, tune encoder buffering and player buffering for a responsive experience that can feel like very low latency 3 sec. Final latency depends on encoder settings, network conditions, and player buffering, but Shoutcast Net is designed for broadcaster-friendly responsiveness.

Pro Tip

Do a “drop test” before you migrate the public: stop your encoder for 15 seconds and reconnect. If you plan to use AutoDJ (next step), this is the moment to verify your station won’t go silent during real-world internet hiccups—especially important for churches, schools, and live event streamers.

Step 4: Enable AutoDJ for 24/7 playback and failover

A major upgrade when moving away from a complex Wowza workflow is adding AutoDJ—a built-in way to keep your station playing 24/7 and automatically cover dead air when your live source disconnects. For radio DJs, podcasters, churches, and schools, this is the difference between “sometimes silent” and “always on-air.”

Action: activate AutoDJ and upload content

Enable AutoDJ on your Shoutcast Net service, then upload:

  • Station IDs and sweepers
  • Music library (royalty-cleared where required)
  • Sermons/lectures (church and education content)
  • Pre-produced shows/podcasts for scheduled playback

Action: configure playlists and rotation

Organize content into playlists (e.g., “Daytime Hits,” “Overnight Chill,” “Talk Segments,” “Worship Sets”). A clean rotation plan keeps your station sounding professional even when nobody is live.

Action: set AutoDJ as fallback (failover)

Once enabled, configure your station behavior so that:

  • When your live encoder is connected, the live show takes priority.
  • When your encoder disconnects, AutoDJ immediately resumes playback so listeners never hear silence.

This is especially valuable for remote DJs, campus stations with rotating student hosts, and churches streaming from unreliable venue internet.

Action: validate metadata and “Now Playing” with AutoDJ

Check that titles update correctly during AutoDJ playback and that your station name/branding displays consistently. Proper metadata makes your stream look professional in players and directories.

Pro Tip

If you’re replacing Wowza because of cost, AutoDJ also reduces operational overhead: fewer “someone must be live” moments and fewer emergency fixes. Pair that with Shoutcast Net’s 99.9% uptime and predictable pricing, and you get a station that scales without the per-hour/per-viewer stress.

Step 5: Update your website/app players and go live

This final step is the actual cutover: swapping your public player URLs from Wowza to Shoutcast Net. If you ran parallel streams, this is typically a quick update with minimal risk. If you’re doing a direct cutover, schedule it for a low-traffic time and have AutoDJ enabled as a safety net.

Action: update your website player embed

Wherever your website references the old Wowza URL, replace it with your Shoutcast Net stream URL (prefer the SSL version if available). Common places to check:

  • Homepage player
  • Listen Live page
  • Sticky footer player
  • Mobile menu links
  • Embedded players inside blog posts or event pages

Action: update apps, directories, and smart links

If you have a mobile app, a station directory listing, or links shared on social profiles, update those destinations too. Many stations miss at least one place where the old URL is stored.

  • Mobile app stream URL (iOS/Android)
  • Directory listings (where you submitted your station)
  • Link-in-bio pages and QR codes
  • Automation/remote DJ docs (so hosts connect to the new server)

Action: consider DNS or branded stream URLs

For a more professional presence, many stations use a branded subdomain (example: stream.yourstation.com) pointing to their Shoutcast Net service. This makes future changes easier because you can keep the same public URL even if you change infrastructure later.

Action: run a go-live checklist

  • Playback works on mobile + desktop, including HTTPS/SSL
  • Metadata updates correctly (live encoder + AutoDJ)
  • AutoDJ fallback kicks in when live disconnects
  • Peak listener handling matches your plan expectations
  • Public comms: post “new stream link” only if needed; ideally the switch is invisible

If you also need Icecast compatibility

Some broadcasters maintain Icecast-style tooling or players. If that’s your environment, review icecast hosting options and choose the approach that best fits your software stack—while still benefiting from Shoutcast Net’s broadcaster-first hosting and predictable pricing.

Pro Tip

Do your cutover in two phases: (1) update your website player first and watch analytics, then (2) update apps/directories. This reduces risk and gives you fast feedback. With Shoutcast Net’s flat-rate unlimited model, you can promote confidently—no more worrying that a spike in listeners will trigger Wowza-style per-hour/per-viewer costs.

Next steps

If you haven’t started yet, spin up your server and test alongside Wowza. You’ll get predictable pricing, modern SSL playback, and features like AutoDJ that keep you on-air even when your encoder drops.

Common migration outcomes

  • Lower monthly cost vs usage-based Wowza billing
  • Fewer outages thanks to AutoDJ failover and broadcaster-focused setup
  • Happier listeners with reliable playback and SSL compatibility
  • Easier growth—promote without fearing per-hour/per-viewer spikes

When you’re ready, migrate with confidence—and build a station that can truly stream from any device to any device while keeping operations simple and costs predictable.