If you want to put an Indian FM radio feed on YouTube, treat AzuraCast as the audio source rather than the complete YouTube output. AzuraCast exposes station audio through a mount point; a separate encoder adds a visual and sends the resulting audio-video stream to YouTube Live.
The practical handoff is straightforward once the roles are separate: identify the correct AzuraCast listener URL, give that URL to an encoder, add an image or live scene, then paste YouTube's server URL and stream key into the encoder. YouTube's official encoder help documents the destination and stream settings.
Understand the AzuraCast-to-YouTube relay
An AzuraCast station normally produces audio for listeners. Its station software can assemble scheduled tracks, live inputs and other audio sources, then expose the result through one or more listener-facing mount points. A mount point is the address an audio player uses to connect to a particular station output.
YouTube Live needs more than a radio audio URL. The encoder must publish a video stream containing both a video track and an audio track. A static station image is still a video source when it is placed inside a video scene. A camera view, studio shot, programme artwork or rotating image sequence can serve the same purpose.
The complete path therefore looks like this:
AzuraCast station audio → mount-point URL → separate encoder → visual scene plus audio → YouTube Live
This is not a native AzuraCast video-to-YouTube destination. Do not expect to paste a YouTube key into an AzuraCast station and have AzuraCast create the video broadcast by itself. The available AzuraCast documentation describes the station, Liquidsoap and mount-point layers, while YouTube documents the separate encoder handoff. The encoder is the component that joins the audio and visual sources.
That separation also helps when diagnosing a failure. If a local audio player cannot reach the mount point, the problem is on the AzuraCast or network side. If the encoder hears audio but YouTube shows no picture, inspect the video scene or encoder output. If YouTube receives a preview but the broadcast later stops, check YouTube's stream health, rights notices and the encoder's connection.
If the encoder runs on a computer or VPS, its network path must be able to reach the AzuraCast URL continuously. A mount point that works in your browser is not automatically confirmed from the encoder's host. Test it from the same machine or environment that will publish the YouTube stream.
Identify the station mount point and audio URL
Start in the AzuraCast station that contains the feed you intend to retransmit. Do not assume the first listener URL is the right one. A station may expose different mount points for different formats or bitrates, and a live input may not be present on every output.
The documented default URL follows this general pattern:
{HTTP/HTTPS}://{BASE_URL}.TLD/listen/{STATION_URL_STUB}/{MOUNT_POINT_URL}
Your actual address will use your AzuraCast domain, station URL stub and mount-point name. A custom mount URL can override the default pattern, so copy the listener URL shown by your installation rather than constructing a guess when the dashboard provides one. The AzuraCast mount-point documentation explains the fields and the listener-facing role of these outputs.
Check these details before moving to the encoder:
- Confirm that the mount point belongs to the intended station.
- Confirm that its current audio is the programme you want on YouTube.
- Note whether the URL uses HTTP or HTTPS.
- Check the audio format and bitrate exposed by that mount point.
- Open the URL in a player that can handle the format, not only in a web browser.
- Test the URL from the encoder host, including after any authentication or firewall rules are applied.
A browser may download an audio file, display an error, or do nothing useful while a media player can play the stream correctly. That does not prove that every encoder will accept it. Compatibility depends on the encoder's supported input methods and on the format delivered by the mount point. Review the chosen encoder's current documentation and perform a real test.
If the source is an actual terrestrial FM signal rather than an existing AzuraCast station output, AzuraCast cannot receive radio waves by magic. You would need an appropriate receiver and an audio capture path, then feed that audio into the station or directly into an encoder. The digital mount-point method is simpler when the station feed already exists inside AzuraCast.
Remember that adding outputs and transcodes can create additional Liquidsoap work. If you add a special mount point solely for YouTube, observe the station host rather than assuming the extra output is free. The AzuraCast scaling guidance is useful when a station has multiple outputs or more demanding processing.
Choose a separate encoder and visual source
Choose an encoder that can do all three jobs in one publishing path: ingest the AzuraCast audio stream, provide a video scene, and send the result to YouTube over RTMP or RTMPS. Not every encoder accepts a remote audio URL directly, so verify that specific input capability before designing the rest of the setup.
For a devotional, bhajan or regional radio channel, a static station image is often the least troublesome visual. Use artwork that you have permission to display, keep important text away from the edges, and make sure the image remains visible while the audio continues. A live studio camera can make the channel more informative, but it adds lighting, camera, local network and supervision requirements.
You can also use a slideshow or a simple scene containing the station name, current programme and contact details. If those elements are generated from another system, test what happens when that system is unavailable. A visual that freezes is usually easier to understand than a black screen, but it still needs monitoring.
The encoder should create a real video track even when the visual does not change. This is why a still image must be placed in a video scene rather than treated as an audio-only upload. The output resolution and frame rate should match what the encoder can sustain and what your connection can send continuously.
YouTube lists H.264, H.265/HEVC and AV1 as supported video codecs in its live encoder guidance. It also lists AAC and MP3 for audio. For a broadly compatible setup, follow the current YouTube guidance and the encoder's own documentation rather than selecting a codec simply because it is available in a menu.
YouTube recommends constant bitrate encoding and a keyframe interval of two seconds, with the interval not exceeding four seconds. For stereo audio, its guidance recommends a 44.1 kHz sample rate and 128 kbps audio bitrate. Video bitrate recommendations vary by codec, resolution and frame rate, so choose the relevant row in YouTube's current table instead of treating one video value as universal.
If the stream is mostly a still image, that does not remove the need for a stable video encode. It may reduce the visual complexity, but the encoder still has to maintain a continuous connection and valid timestamps. Test the exact scene and source combination that you intend to leave running overnight.
Create or select a YouTube Live stream
Open YouTube Studio and enter Live Control Room. Create a new stream or select an existing stream that is appropriate for the channel. YouTube's live streaming overview covers the general workflow and the distinction between preparing a stream and taking it live.
The important values for the encoder are the Stream URL, sometimes called the server URL, and the Stream key. Copy both from YouTube rather than typing them from memory. Some encoders present these as separate server and key fields; others provide a combined custom RTMP destination.
Treat the stream key as a password. Do not place it in a public screenshot, commit it to a public configuration file or send it through an unprotected chat. If it is exposed, reset or regenerate it in YouTube Studio and update the encoder.
Check the stream's visibility, title, description, category and scheduling choices before you start the encoder. These settings do not repair a bad audio input or a missing visual, but they prevent a technically sound broadcast from appearing with the wrong public information.
YouTube may require channel-level live streaming access or other account steps before the first broadcast. The current status is shown in YouTube Studio, so check there rather than relying on an older tutorial. A stream can be technically ready while the channel is still unable to publish it.
If the channel is intended for an Indian audience but may be viewed elsewhere, do not assume that the intended geography limits your rights obligations. Confirm that your agreements cover the way you plan to transmit and, if you retain a recording, archive the content on YouTube.
Enter the URL and key in the encoder
In the encoder, select the input method that matches the AzuraCast output. If it accepts a network audio URL, paste the mount-point URL into that field. If it requires a local media source, use the encoder's documented method for making the stream available locally. Do not replace the AzuraCast URL with the YouTube server URL: they belong to different sides of the relay.
A clear field map looks like this:
| Relay stage | Value to enter | Purpose |
|---|---|---|
| Audio input | AzuraCast mount-point listener URL | Supplies the radio programme audio |
| Video source | Station artwork, slideshow, camera or studio scene | Creates the video track required by YouTube |
| Publishing server | YouTube Stream URL | Tells the encoder where to send the broadcast |
| Publishing key | YouTube Stream key | Authenticates the encoder for that stream |
| Output settings | Codec, bitrate, sample rate and keyframe settings | Controls the encoded stream sent to YouTube |
Keep the source URL and publishing destination visibly separate in your notes. When troubleshooting, this avoids the common mistake of checking the YouTube key while the audio input is actually offline, or changing the AzuraCast URL when YouTube is rejecting the output.
Select the visual scene and confirm that its preview contains an image or camera frame. Confirm that the audio meter moves when the AzuraCast station is playing. Then start the encoder's connection without immediately assuming that the public YouTube page is live. First wait for YouTube to receive and analyse the stream.
If your encoder offers RTMPS as an option, prefer it where available, following YouTube's current guidance. Keep the output settings within the capacity of the uplink. A setting that works for a short test can still fail if the connection has variable upload performance or if another process competes for bandwidth.
For an always-on channel, write down the exact working configuration: mount URL, input format, scene, output codec, audio settings, keyframe interval and YouTube stream destination. Store the stream key separately and securely. This record turns a late-night restart into a repeatable procedure rather than a reconstruction exercise.
Preview and inspect stream health
Once the encoder is sending, return to Live Control Room and wait for the preview. Inspect both parts of the result. You should see the expected visual and hear the expected station audio. A preview with a moving picture but no audio is not ready, and an audio meter without a visible picture does not meet the audio-video requirement.
Use YouTube's stream health indicators to look for dropped frames, connection warnings and encoding problems. Do not judge stability only from the encoder's local status message. The encoder may report that it is connected while YouTube is receiving an unsuitable bitrate, damaged timestamps or an incomplete track.
Test representative content. If the station includes speech, music, jingles and silence, listen to each type. Check whether the audio remains intelligible when the source changes programme or reconnects. If the visual is a slideshow, allow it to change. If it is a camera, check the scene under the lighting conditions expected during the night.
For a scheduled stream, use the control in Live Control Room to go live after the preview is available, according to YouTube's current workflow. Do not assume that starting the encoder alone publishes the broadcast. When you finish, end the stream in YouTube Studio and stop the encoder so that the session closes cleanly.
A short test also gives you a chance to confirm that the station's name, artwork and programme information do not reveal material you did not intend to publish. Check the public watch page from a separate device or connection where possible. A local preview does not show every viewer-side problem.
If the process is likely to run continuously, add an independent check. The monitoring guide for 24/7 streams explains why a dashboard left open on the publishing computer is not enough. For a setup where you do not want to keep a computer running, StreamNeo can remove the need to keep managing a local relay for a prepared YouTube video, but it is not a replacement for the AzuraCast audio-to-video workflow described here.
Troubleshoot audio, visual and handoff issues
The encoder cannot open the AzuraCast URL
First test the mount point from the encoder host, not only from your own laptop. Confirm the scheme, domain, station stub and mount-point name. Then check whether the encoder supports the delivered format and whether any access control, firewall or certificate issue blocks the connection.
If the URL is reachable but the encoder still refuses it, try the encoder's documented network-input method and inspect its logs. Do not conclude that AzuraCast is down until another compatible player or diagnostic from the same host confirms the result. A custom mount URL can also mean that a guessed default address is simply wrong.
YouTube receives video but no audio
Check the encoder's audio meter first. If it is silent, the fault is between the mount point and the encoder input. If the meter moves but the YouTube preview is silent, inspect the output audio track, codec, channel configuration and sample rate.
Listen for a source that has connected but is not actually playing programme audio. A station can be available while the selected mount point carries silence, a backup source or a different format from the one you expected.
YouTube shows audio but the screen is black
Confirm that the scene contains an active visual source and that the source is included in the published output, not only in a local preview. A static image should remain loaded and visible after the encoder has been running for some time. Check for a disabled source, an unavailable file path or a camera that has gone to sleep.
This is also where the audio-to-video distinction matters. Radio audio alone cannot satisfy the required video track. Add a real image, slideshow, camera or other video source and verify that YouTube's preview displays it.
The stream connects, then drops
Compare the encoder logs with YouTube's stream health at the same time. A source reconnect, unstable upload path, overloaded encoder or unsuitable output setting can interrupt the handoff. If AzuraCast is doing extra transcodes or outputs, check its available capacity as well.
Keep the test simple while isolating the fault: one mount point, one visual, one encoder output and the documented YouTube destination. Once that path is stable, add rotation, overlays or additional station outputs one at a time. If your problem is specifically a bitrate warning, the YouTube bitrate troubleshooting guide provides a separate set of checks.
The audio is delayed or repeats
A relay can accumulate delay at more than one stage. Compare the source player with the encoder monitor and then with the YouTube preview. If the delay grows over time rather than remaining roughly steady, investigate buffering, reconnection behaviour and whether the encoder is trying to catch up after a network interruption.
Avoid making several changes at once. Record the source URL, output settings and the time at which the issue appears. That evidence is more useful than repeatedly restarting the station and losing the point at which the delay began.
The stream is interrupted by a rights notice
Check rights before transmitting. YouTube states in its live terms that the provider represents it has the necessary rights for worldwide exploitation of the live content on Google services, including music licensing rights and other relevant rights. YouTube also says that live streams are scanned for matches to third-party content, including another live broadcast, and a stream can be interrupted or terminated.
Permission to receive or retransmit an FM feed does not by itself establish permission for worldwide YouTube live streaming or YouTube archiving. Ask the broadcaster and relevant rights holders what your agreement covers, including music, recordings, compositions, advertising, spoken segments and the territories in which the stream may be watched. Check the current YouTube copyright guidance and obtain India-specific advice for your particular station and agreements rather than treating this workflow as a legal conclusion.
A repeatable overnight operating routine
Before leaving the relay unattended, use a short checklist:
- Play the selected mount point and confirm the expected programme.
- Confirm the encoder receives audio and displays the chosen visual.
- Confirm the YouTube server URL and stream key are current.
- Start the encoder and wait for the YouTube preview.
- Check audio, picture and stream health warnings.
- Verify the public title, thumbnail or artwork and visibility.
- Keep a secure copy of the working configuration without exposing the key.
- Arrange an alert or periodic check that is independent of the encoder window.
If the source station is also being maintained overnight, consider how it recovers after a source failure. The YouTube encoder may remain connected while receiving silence, or it may stop when the mount point disappears. Those are different failures and need different responses. A fallback visual does not fix a missing audio source, and an automatic encoder restart does not prove that AzuraCast has resumed the intended programme.
For power and connectivity planning, separate the station, encoder and monitoring responsibilities. The power-outage guide for YouTube internet radio streams covers why a single computer at the studio is a weak point. If you are building the relay on a Linux host, the systemd guide for an always-on FFmpeg YouTube stream may help with process supervision, but you still need to verify that your chosen encoder accepts the AzuraCast input and publishes a valid video stream.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Can AzuraCast send video directly to YouTube?
Do not treat AzuraCast as a built-in YouTube video encoder. Use AzuraCast for the station audio, then use a separate encoder to combine that audio with a visual and publish the video stream to YouTube Live.
Which AzuraCast URL should I give the encoder?
Use the listener URL for the station mount point that carries the programme you want to transmit. Copy the address shown by your AzuraCast installation, test it from the encoder host and confirm that the encoder supports its audio format.
Can I use only a station image?
Yes, a static image can be the visual source, provided the encoder places it in a continuous video scene and publishes a video track with the audio. Make sure you have permission to use the artwork and test that it remains visible after the encoder has been running.
Does permission to broadcast the FM feed cover YouTube?
Not necessarily. You must verify with the broadcaster and relevant rights holders that your permissions cover YouTube live transmission, music and recordings, worldwide viewing where applicable, and any archive created by YouTube. Check the current YouTube terms and copyright guidance for the particular content and territory.