Owncast can carry an audio-led live stream sent from encoder software over RTMP. Whether the music in that stream may be rebroadcast is a separate question: YouTube’s terms restrict public streaming of music from its service outside permitted cases, and a YouTube Music subscription is not a broadcast licence.
If you want to run a music radio stream, treat the destination, the encoder and the music source as separate parts of the plan. Owncast gives you a self-hosted destination to configure, but you remain responsible for the host, the network, ongoing operation and permissions for the music you transmit.
Technical ability is not permission
Owncast is a self-hosted live streaming server that accepts a broadcast from encoder software such as OBS. In practical terms, you install and configure Owncast on a host, point your encoder at its RTMP endpoint and send audio, with or without a video element. That answers whether it can carry an audio-led broadcast: technically, it can.
It does not answer whether you may rebroadcast a particular source. An encoder can package and send sound without knowing whether the operator has permission to transmit it publicly. The server’s ability to receive that stream does not change the terms attached to the source music, copyright permissions or the rules that apply where you and your listeners are.
That distinction matters if by “YouTube Music radio stream” you mean playing tracks from YouTube Music and sending what you hear to an audience. YouTube’s Terms of Service give publicly streaming music from the service as an example of use outside personal, non-commercial use. The relevant paid-service terms also describe paid-service access as personal and non-commercial and restrict public presentations, subject to the terms’ stated copyright exception. Paying for access should not be presented as permission to rebroadcast.
This is not a ruling on every possible rights arrangement or local legal exception. It is a reason to check the current official terms and your actual permissions before putting a music source on a public stream. The technical setup is useful only after that source question has been answered.
How an audio-led stream reaches Owncast
The signal path is straightforward: your audio source goes into broadcasting software, the software encodes the stream, and the encoded broadcast is sent to Owncast over RTMP. Owncast then provides the destination for viewers. OBS is one example of encoder software documented as compatible by Owncast; exact control names vary between applications.
A manual installation involves setting up Owncast on a supported host and installing ffmpeg. Owncast’s installation documentation uses web port 8080 and RTMP port 1935 as defaults. Those are configuration defaults, not universal values: your host, firewall or chosen configuration may require different arrangements. The web interface and the RTMP ingest endpoint both need to be reachable in the way your setup expects.
Once the server is available, configure the encoder with the Owncast RTMP address, the /live path and the stream key. The stream key identifies the broadcast destination, so do not publish it in a screenshot, public post or setup guide. Change the default administrator password and stream key immediately after first login, as the installation instructions advise. Treat example credentials in any documentation as examples, not as credentials to reuse.
The encoder sends a continuous signal only while its source, software, network and host cooperate. If the computer producing the stream sleeps, loses its connection or stops encoding, the server cannot conjure up the missing programme. That is one operational difference from an always-on arrangement where the playout does not depend on your personal computer staying on. For a YouTube-focused alternative, see how a cloud playout service can run a church sermon channel; it addresses a different destination and does not resolve music rights.
Formats for compatibility
Owncast recommends H.264 video and AAC audio for broad compatibility. For an audio-led station, AAC is the pertinent audio recommendation. If you are also sending a visual layer—perhaps artwork, a still image or a simple animated background—H.264 is the corresponding video choice in the documented combination.
Compatibility is not the same as quality, and neither codec changes permissions. The source audio itself may already be compressed, so encoding it again cannot restore detail that is absent from the source. A sensible test is to use the actual programme material and intended encoder settings, then listen on the same sorts of devices your audience is likely to use.
Owncast supports Raspberry Pi arm64 and arm7 builds in its manual installation documentation, while ARMv6 is unsupported. This does not establish that a particular board will manage every audience size or configuration. If you are choosing a small self-hosted computer, check the current installation guidance for supported architecture and test your own stream rather than assuming a hardware label guarantees capacity.
For a 24/7 setup, include the whole chain in your compatibility check: the operating system, Owncast build, ffmpeg installation, encoder output and player used by listeners. Keep the test simple at first. Confirm that audio is present, that the stream remains stable over a meaningful run and that a listener outside your local network can reach it. A successful preview on the machine running the encoder does not demonstrate that the public route or firewall is configured correctly.
Choosing an audio bitrate
Owncast lists 96, 128, 192, 256 and 320 kbps as example audio bitrate levels, and notes that a music-focused stream may call for a higher choice. These are configuration examples, not a quality guarantee and not a requirement to choose the largest number. Match the setting to the source material, the listener experience you need and the capacity of the upload connection.
| Example audio bitrate | Practical consideration |
|---|---|
| 96 kbps | A lower data rate can reduce network demand; listen carefully for artefacts in music. |
| 128 kbps | A common point to test when balancing data use and music playback. |
| 192 kbps | Uses more data than the lower examples; check that your source and connection justify it. |
| 256 kbps | A higher-rate option to evaluate with the actual encoder, source and audience route. |
| 320 kbps | The highest example in Owncast’s list; it does not guarantee a listener will hear a meaningful improvement. |
The figures are bitrates, not monthly bills or listener counts. More bitrate means more data carried per second, so the outbound capacity needed from the host rises as the stream rate rises and as more people listen. The exact load depends on the number of concurrent listeners and other stream settings; do not choose a setting by copying someone else’s number without accounting for your connection.
Start with a setting your source can support and your network can sustain, then listen for problems and monitor the stream during a test. If a change improves the sound on the devices you care about without stressing delivery, it may be worthwhile. If the original material is low quality, increasing the encoded bitrate will not make it high fidelity. For longer continuous content, the source programme matters as much as the encoder setting; this guide to building a continuous lofi radio playlist is useful for thinking about programme continuity, though its platform focus is YouTube.
YouTube Music and public rebroadcast restrictions
YouTube’s Terms of Service say users may use the service to view or listen to content for personal, non-commercial use and identify publicly streaming music from the service among examples outside that use. The paid-service terms likewise frame access as personal and non-commercial and restrict public presentations, with an exception stated for uses that would not constitute copyright infringement. Read the current wording directly: a paid subscription should not be treated as a blanket right to transmit music to the public.
This distinction applies whether the destination is Owncast, YouTube Live or another service. Changing the receiver of an audio signal does not change the terms governing how you obtained or may use the music. Nor does an audio-only presentation, a static image, a radio-style label or a small audience automatically settle the permission question.
The same separation applies in the opposite direction. A stream may be technically configured correctly and still encounter a rights or terms issue because of its source. Conversely, having music permissions does not guarantee that your encoder, network or host will deliver a stable stream. Treat technical testing and rights review as separate checkpoints rather than using one as evidence for the other.
If your actual plan is to use YouTube Music as the source, pause before building the encoder workflow around it. Check the relevant current terms and obtain advice or permissions appropriate to your use where needed. Do not assume that an individual subscription, a public playlist or the fact that a track can be played in an app makes it available for public rebroadcast.
Check rights and source permissions
Before choosing music, establish who controls the material and what uses are authorised. For original music, confirm who owns or controls the recording and composition and whether all collaborators have agreed to the intended public transmission. For licensed music, read the licence for the exact rights granted, including whether it covers a continuous public stream, the territories where listeners may access it and any commercial context. A licence for personal listening, downloads or use in a single video may not cover a live radio-style broadcast.
Keep the evidence in a place you can find later: written permission, the licence terms, the tracks covered, the permitted use and any limits or dates specified by the rights holder. If a distributor, label, publisher or collecting society is involved, make sure you understand which rights each party controls. The answer may vary by jurisdiction and by whether the stream is monetised, so avoid assuming that a permission for one use covers all others.
YouTube’s terms and Owncast’s technical documentation answer different questions. Owncast describes how to send a broadcast to its server; YouTube describes restrictions on use of its service. Neither document substitutes for a licence from a rights holder where one is needed. If you are uncertain, check the current official terms and get qualified advice for your circumstances rather than relying on a forum post or a successful test stream.
This is also why source choice belongs before playlist automation. Build a programme from tracks you created, tracks with permissions that expressly match the planned use, or other sources you have verified. If you are thinking instead about continuous YouTube programming, see the practical considerations in using a YouTube playlist as a 24/7 livestream source; the page’s subject does not alter the need to verify source rights.
When Owncast fits a music stream
Owncast is a plausible fit when you want to operate your own streaming destination, can manage a host and network configuration, and have a source you are authorised to transmit. You control the setup choices and can send a compatible RTMP broadcast from encoder software. That control also means you take on the work: installation, firewall reachability, configuration, monitoring, recovery from failures and capacity planning.
It may be a poor fit if you do not want to maintain a server or troubleshoot networking. A self-hosted service is not a hands-off radio station: if the host reboots, the internet connection fails or the encoder process stops, somebody must notice and restore the chain. A managed playout arrangement may suit you better if your main requirement is a continuous stream without keeping your own computer active, but you should compare its destination, controls, costs and source rules carefully. No hosting choice grants rights to music.
For operators whose specific goal is a 24/7 YouTube channel rather than an independent Owncast destination, the workflow may be different. StreamNeo can remove the need to keep your own computer running for an uploaded video that you are authorised to stream, but it does not make YouTube Music available for rebroadcast or replace source permissions. Keep that use case separate from a live encoder-to-Owncast setup.
A small test is a useful operating decision before committing to a larger audience. Verify the end-to-end signal, inspect the server and encoder logs when something drops, and ask someone on a different connection to listen. Document the restart steps and who is responsible for them. For YouTube-specific reliability questions, this walkthrough on a stream stopping when your computer is turned off can help clarify why a local computer-dependent workflow behaves differently; it is not an Owncast setup guide.
The right choice is therefore conditional. If self-hosting and control suit you, and the source is cleared for the intended public transmission, Owncast can technically carry an audio-led RTMP programme. If your plan depends on replaying music from YouTube Music to a public audience, do not take Owncast’s compatibility as permission; resolve the terms and rights question first.
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 Owncast stream audio without video?
Owncast can receive an audio-led RTMP broadcast from encoder software. Configure the encoder to send audio in a compatible format such as AAC; any video layer is a separate part of the stream configuration. Test playback from a listener’s device before relying on it.
Can I use a YouTube Music subscription as my radio licence?
Do not treat a subscription as broadcast permission. YouTube’s terms describe personal, non-commercial use and restrict public presentations or streaming music from the service outside stated permitted cases. Check the current terms and obtain the permissions needed for your specific use.
Does a higher bitrate always sound better?
No. A higher bitrate uses more data and cannot restore detail missing from the source. Owncast’s listed values are examples, so test a suitable setting with your actual programme, connection and playback devices.
What do I need to keep an Owncast stream running?
You need a configured Owncast host, reachable web and RTMP routes, encoder software and a stable source and network. You also need to monitor the setup and restore it when something fails. Self-hosting puts that operational responsibility with you.