A live indicator only tells you that a connection has started; it does not prove that YouTube is receiving decodable video. Check the OBS source, Owncast playback and YouTube Live Control Room preview separately to find where the picture disappears.
For a local-file loop, OBS is the playout source and Owncast is the receiver. You select and loop the video in OBS, then send its output to Owncast over RTMP. The reviewed documentation does not support importing or looping a video directly from a YouTube page through Owncast.
What Owncast receives and what it does not loop
Owncast receives a live broadcast from encoder software such as OBS. It processes the incoming stream into video segments for its viewers; it is not the application that selects a file from your computer or repeats that file. In this workflow, OBS supplies the video and controls whether it repeats.
That distinction matters when a dashboard says “live” but a player is black. A connection can be established while the selected source is blank, the encoder is not producing compatible video, or Owncast is having trouble processing its input. If you are also sending a feed to YouTube, that is a separate destination and connection to check. One live status does not establish that both services are receiving the same usable picture.
Owncast identifies H.264 video and AAC audio as formats for which it assures transcoding and playback compatibility. It recommends a two-second keyframe interval rather than leaving the interval on auto. These are practical starting points, not a guarantee that every encoder, server and network will work at a particular resolution or bitrate. Owncast’s broadcasting guide explains the stream settings and endpoint.
If the question is whether a YouTube-hosted clip can be selected inside Owncast and looped there, the answer is no in the workflow covered here. Use a local video file as an OBS source, or use another source you are entitled and able to broadcast. A YouTube page is not a local media file, and pasting its page address into Owncast does not turn it into an OBS playout source.
Prepare a local video file in OBS
First choose a video file stored on the computer running OBS. Confirm that it opens and plays outside the live setup, and check that its picture and audio are the ones you intend to broadcast. If it has a long black opening, a silent track, or an unexpected aspect ratio, those problems will be visible in the stream too.
Keep the file at a stable location while OBS is running. A removable drive that disconnects, a renamed file, or a moved folder can leave the Media Source unable to read its input. For an overnight channel, use a file path that will remain available after a restart and avoid relying on a temporary download folder.
Before connecting to Owncast, inspect the scene in OBS. The preview should show the file, and the audio mixer should react if the clip has sound. If the preview is already black, there is no reason to troubleshoot Owncast or YouTube yet: correct the source or scene first. If you need repeatable video playout rather than a single clip, the setup choices in OBS playlist source versus VLC for looping videos are useful to consider.
For a first test, use a short, representative file and watch a complete pass. Confirm that the last frame and the return to the beginning behave as expected. This catches a source that works initially but does not restart cleanly before you leave it unattended.
Add a Media Source to a scene
In OBS, select the scene that will carry the broadcast. Add a Media Source, give it a recognisable name such as “Main loop”, then choose the local file. The name is for your own scene management; it has no effect on the stream sent to Owncast.
With the source selected, check that it is visible in the scene preview and is not covered by another source. A Media Source can be present in the Sources list but hidden, placed below an opaque image, or cropped outside the canvas. Those are OBS composition issues, not evidence that Owncast has failed.
Check the source properties before going live. The file path should point to the intended media, and any playback options should suit the file. If the picture appears but the audio does not, inspect the source’s audio behaviour and OBS’s mixer before changing the Owncast destination. Keep the scene simple until the basic file plays correctly; add logos, overlays or text after you have verified the picture path.
If OBS shows video but the receiving Owncast page does not, then move downstream through the checks below. If you are making a YouTube channel from recorded lessons, a separate guide to restarting an OBS playlist after its last video covers a playlist-specific case. A single Media Source loop and a playlist are different OBS arrangements, so do not assume a playlist setting controls this file source.
Enable Loop for the file
Open the Media Source properties and enable its loop option. This tells OBS to restart that file when playback reaches the end. It does not tell Owncast to find or repeat the file, and it does not make a YouTube page an input source.
Test the loop while watching the OBS preview. Let the clip reach its end and check that playback begins again. If it stops instead, reopen the source properties and check that the intended file is still selected and the loop option is enabled. Also confirm that the source is active in the scene; a disabled or hidden source will not provide a picture just because looping is selected.
A clean transition depends partly on the media itself. A file whose final frame differs sharply from its opening frame may visibly jump on every repeat. That is not a streaming fault, but it may be distracting in an ambience or devotional channel. For a long-running bhajan loop, review the start and end of the recording and make sure your use of the music is permitted; checking music distributor whitelisting before 24/7 streaming is relevant when a distributor manages the rights on your channel.
Do not judge the loop only from a brief preview. Watch at least one full pass and the restart, then keep OBS running long enough to notice whether the source unexpectedly goes offline. This verifies the local playout behaviour, not the quality of Owncast transcoding or YouTube ingest, which must be checked at their own points.
Send OBS output to Owncast over RTMP
In Owncast, obtain the broadcast destination and stream key for your instance. Owncast accepts RTMP on TCP port 1935 by default, and the key is used with the /live/ path. The port can be configured differently, so use the port your installation actually exposes. A typical endpoint is rtmp://yourserver:1935/live with the key entered separately in OBS; if the encoder has no separate key field, Owncast documents putting the key after the path.
Enter the Owncast endpoint and key in OBS’s streaming settings, then start streaming. Treat these credentials as separate from YouTube’s. YouTube provides its own stream URL and key in Live Control Room; a valid Owncast destination does not fill in or validate the YouTube destination. YouTube’s stream settings help describes the YouTube stream key and settings.
Check the output routing actually configured in OBS. If you have more than one output or are using a plugin or relay, establish which destination receives the current scene. A status saying that OBS is connected to Owncast does not show that a separate YouTube output is active. Conversely, YouTube may be receiving a different source than the one shown on the Owncast page.
If the stream connects and then drops immediately, confirm the server address, port, /live path and matching key. Owncast’s troubleshooting guide includes adjacent diagnostic questions about video-related errors in logs and broadcasting software disconnecting after start. Do not repeatedly rotate settings at random: change one item, reconnect, and note whether the observed symptom changes.
For compatibility, configure H.264 video, AAC audio and a two-second keyframe interval. Owncast publishes example settings, including 1920×1080 at 30 fps with 4500 kbps and 1280×720 at 30 fps with 3000 kbps. These are Owncast examples, not universal YouTube requirements or a promise that your server and upload connection can sustain them. Begin at a level your system can manage and consult the bitrate and dropped-frames checklist if OBS reports network or encoding strain.
Verify the Owncast viewer stream
After OBS starts, open the Owncast viewer page and confirm that the picture appears and moves. A connected broadcaster is only the first checkpoint: Owncast also has to process the incoming stream and provide playable output. Check sound separately, since a visible picture does not establish that the audio path is correct.
If the viewer page is black or fails while OBS preview is good, inspect Owncast’s application log and, if the server log does not explain the failure, data/logs/transcoder.log around the time it happened. Look for transcoder startup or output errors. Owncast’s hardware encoding notes also caution that seeing an encoder in an FFmpeg listing does not prove that the required driver and hardware configuration works; its version suggestion is guidance, not a hard minimum for every installation.
A historical issue report describes a stream that connected before HLS output errors appeared. It illustrates why a connection and successful video processing are separate checks; it is not a diagnosis of your installation. Do not infer that you need new hardware from a black frame alone. Start with the logs, the selected OBS encoder and format, and whether a lower-complexity test stream changes the result.
If Owncast plays the file correctly but YouTube remains black, the source and Owncast path have at least produced a playable picture. Focus next on YouTube’s ingest destination, stream selection and the routing in OBS. This comparison narrows the investigation, but it is not a guaranteed root-cause test: each platform’s preview and player can fail for different reasons.
Separate a local file from a YouTube-hosted source
A local-file workflow means OBS reads a file from storage and sends the encoded live output to Owncast. Owncast receives that broadcast; it does not select, download or loop the file for you. The reviewed documentation does not support importing or looping a video directly from a YouTube page through Owncast, so do not treat a page URL as an equivalent Media Source.
If you intend to show a YouTube stream on YouTube through your own encoder, first establish that you have an appropriate source and the rights to rebroadcast it. Do not build a 24/7 workflow around extracting playback from a web page. For a devotional or study channel, prepare the media file you are authorised to use, add it to OBS, and test its loop locally before configuring the live destination.
When YouTube itself is the destination, use the exact stream URL and key shown for the intended event in Live Control Room. The YouTube preview is the checkpoint before you make a scheduled stream live. YouTube recommends RTMPS for encrypted ingest; if the preview never arrives and OBS reports a connection or SSL error, verify the selected protocol and URL, and check whether the encoder supports RTMPS. YouTube notes that port 443 may help with some SSL errors in its live streaming troubleshooting guidance.
Compare the point where video first disappears: OBS preview, Owncast viewer, YouTube Live Control Room preview, or only the published YouTube player. Also note whether Owncast’s transcoder reports errors and whether YouTube appears to receive the configured feed. This gives you a more useful record than “live but black” when you revisit settings or ask someone to inspect the logs.
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
Owncast says live, but the Owncast viewer is black. What should I check first?
Check that OBS preview shows the file, the Media Source is visible, and its path still points to the intended file. Then verify H.264 video, AAC audio and the Owncast destination settings. If OBS looks right but the viewer remains black, inspect Owncast’s logs and data/logs/transcoder.log for errors at the time of the test.
Owncast plays video, but YouTube’s preview is black. Is Owncast the problem?
Not necessarily. Verify that OBS is sending an output to YouTube, not only to Owncast, and confirm that YouTube’s URL and key match the intended stream in Live Control Room. If the YouTube preview is absent alongside a connection or SSL error, check the ingest protocol and RTMPS support before changing a working Owncast setup.
Can I loop a video directly from a YouTube page through Owncast?
The workflow described here does not support importing or looping a video from a YouTube page through Owncast. For a local loop, add a file stored on your computer as an OBS Media Source and enable Loop there. Owncast receives OBS’s broadcast; it does not choose or repeat the file.
Which stream settings should I try for Owncast?
Use H.264 video, AAC audio and a two-second keyframe interval as a compatibility starting point. Choose resolution and bitrate according to the processing capacity of your Owncast installation and the upload connection available to OBS. Owncast’s published examples are reference configurations, not a guarantee that a particular setup will work unchanged.