The signal chain, end to end
OBS Studio has no Icecast entry in its Stream settings. The route runs through the recording side instead: the Custom Output (FFmpeg) recording type can write to a network address rather than a file, and FFmpeg understands the icecast:// scheme. The OBS project's own wiki describes this same Record-output method for other network protocols.
- Your microphone, music and desktop audio are mixed in OBS as usual.
- The Record output encodes that mix with FFmpeg, for example to MP3.
- FFmpeg opens a source connection to the Icecast server and mounts the stream at the path you give it.
- Listeners play the mount through the station's listen link.
Because the Record output carries the broadcast, you cannot make a local recording in the same OBS profile while it is on air. Record a backup copy somewhere else in the chain if you need one.
What to collect before you open OBS
You need five details from your Icecast server. On our SSL radio streaming service they come with your station's encoder settings; Platinum stations find them in the control panel's Radio section.
| Detail | What it is | Notes |
|---|---|---|
| Host | The server name your encoder connects to | On Platinum, use the nearest-server encoder address from the Radio section |
| Port | The port the server listens on for sources | Copy it; do not assume a default |
| Mount | The path that names your stream, starting with a slash | Avoid spaces and unusual characters; copy it exactly |
| Source user | Icecast's default source username is source | Use the one your panel gives if it differs |
| Source password | The password for encoders | Not your control panel login |
Then note the bitrate your plan carries. The service page lists 32 kbps on Free, 128 kbps on Premium and up to 320 kbps on Platinum. Set OBS to that figure or lower.
Settings to copy into OBS
- Open Settings, then Output, and set Output Mode to Advanced.
- Open the Recording tab and set Type to Custom Output (FFmpeg).
- Set FFmpeg Output Type to Output to URL.
- In File path or URL, enter your address in the form shown below.
- Set Container Format to mp3.
- Set Audio Encoder to libmp3lame and the Audio Bitrate to your plan's figure or lower. Tick the audio track that carries your programme mix.
- Click Apply, then OK. Press Start Recording to go on air and Stop Recording to leave.
icecast://source:YOUR-SOURCE-PASSWORD@your-server.example:PORT/your-mount
That layout follows FFmpeg's protocol documentation: icecast://[username[:password]@]server:port/mountpoint. If the password contains characters such as @, : or /, the address can be misread; use a source password made of letters and digits only.
The password sits in plain view in that field and in your OBS profile. Do not share screenshots of the Output settings or hand your profile folder to anyone, and change the source password if either has leaked.
Why MP3, and when to choose Ogg
FFmpeg's Icecast protocol announces the stream as audio/mpeg unless told otherwise, and its documentation says the content type must be set whenever the stream is something else. An MP3 container with libmp3lame matches that default, so no extra option is needed.
Icecast's own FAQ lists Ogg (Vorbis), Opus, FLAC and WebM as its officially supported formats and says MP3 and AAC may work without official support. For a hosted station, MP3 is the safe default unless your provider says otherwise. On a self-managed Icecast server with Ogg Vorbis, its basic setup guide asks for a mount ending in .ogg, and FFmpeg needs content_type set to match.
Checks before you go live
- OBS status bar shows the recording timer running, and it keeps running past the first minute.
- The audio meter for the track you ticked moves when you speak.
- On a second device, open the HTTPS listen link; your voice should come through a few seconds late.
- Your listener statistics show that second device tuned in right now.
- Talk for thirty seconds over music and listen for clipping; pull the master fader down if the meters hit red.
Run the whole list once on a test day, not five minutes before the show. On a self-managed Icecast server, the basic setup guide suggests confirming the source through the server's stats.xml page.
When it goes wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| Recording stops at once with an error | Wrong host, port, user or password | Retype each part; check for special characters in the password |
| Connects to an old self-hosted server only with errors | Icecast before 2.4.0 does not accept HTTP PUT | FFmpeg's legacy_icecast option exists for those servers; upgrading Icecast is the cleaner fix |
| An Ogg stream misbehaves in players | Content type left at audio/mpeg | Switch to MP3, or set content_type to the Ogg type |
| Meters move but the listen link stays silent | The programme mix is on a track the output does not send | Tick the right audio track in the Recording tab |
| Timer stops after a network drop | The connection was lost and did not resume | Press Start Recording again and recheck the listen link |
Still stuck? Open a ticket or chat from the support page with the address you typed, with the password replaced by stars.
Where this route is the wrong tool
The custom FFmpeg output is a general-purpose path, not a radio encoder. OBS's wiki does not describe reconnection for it, and it ties up the Record output. If your show is audio only, a dedicated encoder such as BUTT, Mixxx, SAM Broadcaster or RadioBOSS does the same job with fewer fields, and Premium and Platinum stations can also go live with the studio encoder that runs in the browser, nothing to install.
If you want pictures as well as sound, send OBS to a video channel over RTMP instead. Our live video streaming plays it as HLS in any browser, and OBS's ordinary Stream settings take the server and stream name.
Running it on our radio service
Every station starts on Icecast, and any encoder that speaks Icecast or SHOUTcast will do, OBS audio among them. Listeners hear it over HTTPS, so the player embeds on a secure website without mixed-content warnings. A free plan lets you prove the whole chain before you pay for more listeners or bitrate.
- On paid plans, AutoDJ keeps your uploaded tracks playing day and night, then steps aside the moment a live DJ connects.
- On Platinum, your encoder connects to the nearest of five cities, which forwards the broadcast to your station; passwords and DJ slots behave as before.
- Support runs day and night by live chat, where an assistant can check your account and hands you to a staff member on request.