A Synology NAS can send a selected live camera stream to YouTube through Surveillance Station’s Live Broadcast feature, provided your model and installed software support it. That is a different workflow from playing a playlist of prerecorded files: Synology’s documented feature does not establish that it loops stored video to YouTube.
If your source is a camera, start by checking Surveillance Station and camera compatibility. If your source is a video archive, you need a separate encoder or streaming application that can read those files and publish to YouTube. In either case, test the full path and recovery behaviour before treating it as an always-on channel.
Choose between a camera feed and prerecorded video
First decide what “24/7” means for your channel. A camera broadcast continually sends a live view from a camera, such as a shop floor, a temple courtyard or a fixed outdoor scene. A prerecorded channel plays one or more existing videos, perhaps a devotional programme, a local information loop or a sequence of study music. The fact that both may remain live on YouTube for long periods does not make their source and publishing workflows interchangeable.
For a camera, Surveillance Station is the relevant Synology path to investigate. Synology documents a Live Broadcast application that can send a selected camera stream to YouTube. The NAS manages the camera feed within the supported Surveillance Station setup; it is not simply opening a video from a shared folder and broadcasting it.
For prerecorded media, the NAS is initially a storage location. A separate encoder must open the media, create the live output and send it to YouTube. That encoder might run on a computer or another supported system, but you should not assume that a NAS media library feature is also a live encoder. Synology’s Video Station product information describes local video management and client playback, not a YouTube broadcast workflow; it also notes that Video Station is unavailable on DSM 7.2.2.
This distinction affects your purchase and setup decisions. If you already have a camera and a compatible NAS, investigate the documented camera workflow first. If you are building a loop from stored files, compare encoders by NAS file access, scheduling or looping, output format, and recovery behaviour. A useful starting point for the latter is this guide to streaming an episode archive with labels, because the challenge is organising and presenting stored media, not merely keeping a camera online.
What Surveillance Station Live Broadcast supports
Synology’s Knowledge Center describes Live Broadcast as a way to send live camera streams to YouTube. The documented flow is camera-based: enable the Live Broadcast application, configure its status and YouTube RTMP path and key, then select the camera and stream profile. Synology specifies H.264 video support for this feature. Read the Live Broadcast help page against the version installed on your NAS before following menu labels literally.
The help page is version 8 documentation, and available functions depend on your model, DSM release, Surveillance Station package and camera. Synology’s Surveillance Station specifications for DSM 7.4 list RTMP over TCP among supported tunnel formats and state that Live Broadcast sends camera streams to YouTube. That is useful confirmation of the feature’s role, but it is not evidence that every NAS has the same package availability or capacity.
Check the compatibility chain before making assumptions. Confirm the exact NAS model and DSM version; confirm that Surveillance Station and Live Broadcast are available for that model and version; and check that the camera can be added to Surveillance Station and provide an appropriate H.264 stream profile. If the camera is not on the compatibility list, investigate the exact model and protocol support rather than assuming a generic IP-camera label is enough.
There is an important boundary here: the reviewed Synology documentation describes live camera streams. It does not establish native playlist looping or broadcast of prerecorded files through Live Broadcast. A NAS may store, index or play videos for other devices without being able to publish those videos as a continuous YouTube live stream. Keep those functions separate when planning the channel.
Prepare YouTube Live and the RTMP details
Before configuring Synology or another encoder, make sure your YouTube channel is able to start a live stream and that you understand the YouTube Studio controls. YouTube’s live streaming encoder guide describes encoder setup, stream health and recommended settings. Create or select the stream in YouTube Studio and locate the ingest details it provides. Treat the stream key as a credential: do not post it in screenshots, shared notes or public support requests.
Synology’s documented Live Broadcast path asks for a YouTube RTMP path and stream key. Enter the ingest address and key as YouTube supplies them, without adding punctuation, spaces or a second key. The exact field names can change with package versions, so follow the installed Synology interface and current help rather than relying on a screenshot from another release.
YouTube recommends RTMPS, an encrypted extension of RTMP, for general live ingestion. However, the cited Synology help specifies RTMP path and key; do not assume every version of Synology Live Broadcast accepts an RTMPS endpoint. For that direct camera workflow, use the options the installed feature actually supports. If you use a separate encoder for stored video, choose RTMPS when that encoder and the YouTube ingest configuration support it. The distinction between the protocols is covered in more detail in RTMP and RTMPS explained.
Set output quality in relation to the source and the internet connection, rather than choosing the highest available resolution. YouTube’s encoder guide gives settings by resolution, frame rate and codec; use the matching row for your output. For example, its table lists a recommended H.264 bitrate of 4 Mbps for 240p–720p at 30 fps. That is a reference for that specific combination, not a universal setting for every stream. YouTube advises testing upload speed and monitoring stream health, because available upstream bandwidth and other traffic can affect delivery.
For a separate encoder workflow, YouTube also documents HLS ingest for compatible encoders. Its HLS ingest guidance explains that HLS has higher latency than RTMP because it sends video in segments, and that it requires a compatible encoder and specific segment and playlist settings. HLS is not a shortcut for enabling a Synology feature that does not document it.
Set up a camera broadcast from Synology
Begin with the installed package and camera, not with a generic checklist of menu names. Update or verify DSM and Surveillance Station as appropriate for your own device, then confirm that Live Broadcast is present and enabled. Synology’s version-specific help should be your reference for the interface; if the option is absent, check model and package support before troubleshooting YouTube credentials.
Once the feature is enabled, set its status to on and supply the YouTube RTMP path and stream key in the relevant fields. Select the intended camera and a stream profile that uses H.264. If you have several cameras, identify the exact one to publish and confirm its field of view, audio and privacy implications before starting the broadcast. The selected camera profile determines what leaves the NAS; a recording profile used for local surveillance may not be the right output profile for a public channel.
Start with a private or otherwise limited test where your channel controls permit it. Verify that the correct camera appears in the YouTube preview, the image is stable, the audio is present only if intended, and YouTube reports a healthy incoming signal. Check the result from another device or network rather than only from the local NAS interface. This makes it easier to spot a wrong camera, unintended overlays, poor framing or an audio problem before you share the public stream.
A camera path may suit a live scene, but it is not necessarily the simplest way to run a channel built from edited programmes or ambience tracks. For a prerecorded format, an encoder must open the NAS files and send an encoded feed independently. The guide to keeping a rain-sounds stream from stopping overnight is relevant when you are thinking about playback continuity, but do not treat any playback setup as guaranteed to run without interruption.
For stored video, use an encoder that can read the NAS
A prerecorded workflow has at least two distinct parts: media access and live publishing. The encoder needs permission and a dependable path to the files on the NAS, then it needs to decode or otherwise process those files and create a YouTube-compatible live output. The NAS’s ability to host a shared folder does not by itself prove that a particular encoder can read it, that the files will play continuously, or that it can recover from interruptions.
Before choosing an implementation, check whether the encoder runs on your intended hardware and operating system, can read the NAS path in the way you plan to mount or access it, and supports the codecs and audio format in your media. Then verify that it can loop or schedule a playlist if that is essential to your programme. A single long file, a rotation of short clips and a timetable of different programmes are different playback requirements; test the exact one you intend to use.
The encoder also needs an output YouTube accepts. Check its codec and protocol settings against YouTube’s current encoder guidance, and choose RTMPS if it is supported by both sides of the workflow. If your software offers HLS instead, confirm that it is compatible with YouTube’s HLS ingest requirements and account for the higher latency. Do not infer protocol support from the fact that the encoder can publish to some other platform.
Where the encoder runs matters. Running it on a desktop means that desktop, its power and its network connection are part of the broadcast path. Running it on a NAS is only an option if the exact software is supported on the model and can perform the required decoding and encoding work; this article does not establish a particular NAS-native package as a verified recommendation. If you want the computer switched off, a cloud-based route can remove the need to keep a home PC running, but it changes how files are uploaded and managed. Compare the operational trade-offs in this overview of cloud services for always-on YouTube streams rather than assuming one arrangement suits every channel.
A practical preflight is to copy a representative media file into the intended NAS folder, grant the encoder the same access it will have during normal operation, and run a test for longer than a brief preview. Include the change from one file to the next if you expect a playlist. Confirm that the picture and audio remain in sync, the sequence advances as intended, and a renamed or temporarily unavailable file does not leave the encoder in an unknown state. Record the specific software version and file path so you can reproduce the test after a change.
Check continuous playback and reconnection behaviour
Neither Synology’s camera feature documentation nor YouTube’s ingest recommendations promise uninterrupted operation. YouTube recommends testing with representative audio and motion, monitoring stream health, and using encoder settings such as constant bitrate (CBR) and an appropriate keyframe interval. These are operating practices, not a guarantee that a particular network, camera, NAS or encoder will remain live continuously.
Test the failure modes that matter to your channel. For a camera workflow, observe what happens if the camera becomes unreachable, the NAS restarts, the router loses its connection or the internet link drops. For a stored-video workflow, test a file transition, an unavailable media path, an encoder restart and a network interruption. Note whether the broadcast resumes by itself, requires a manual action, or produces a new live session that needs attention in YouTube Studio. Behaviour can vary by package and encoder, so verify rather than assume.
Plan for monitoring as well as recovery. Decide who will notice an offline stream, where they will check its state, and how they will regain access to the NAS, encoder and YouTube account. Keep a safe record of configuration details, but store the stream key securely and rotate it if it is exposed. If you need to diagnose packet loss or intermittent network trouble, use a focused checklist such as how to fix packet loss in live streaming, then retest the full route rather than concluding that a single successful preview settles the matter.
A useful test log can be simple: date and time, source type, NAS and package versions, encoder settings, YouTube health status, and what happened after an interruption. This helps distinguish a playback issue from an ingest or network issue. It also gives you a basis for deciding whether the setup is dependable enough for the role you expect it to play, without claiming a particular uptime in advance.
Test the stream and troubleshoot the path
Test each link in the chain in order: source, NAS or encoder, network, YouTube ingest, and viewer playback. For a camera, confirm that Surveillance Station can show the selected camera before you troubleshoot YouTube. For stored media, confirm the encoder can open the exact file from the NAS path and play through it before you investigate ingest. This narrows the fault to a particular stage.
If YouTube receives no signal, first check that the stream is live or configured correctly in YouTube Studio, then verify the ingest path and key character by character. Confirm that the selected profile uses H.264 for Synology Live Broadcast. For a separate encoder, compare the encoder’s protocol, video codec, frame rate, bitrate and keyframe settings with YouTube’s current guidance. Do not switch RTMP to RTMPS or HLS merely as a guess; establish that the source feature or encoder supports the endpoint you are trying.
If the preview is choppy or YouTube reports a weak stream, compare the chosen output with the available upload capacity and other network use. Lowering the output quality may make the stream easier to sustain, but it also changes the viewer experience; test a realistic setting rather than selecting a value from a generic article. Watch YouTube’s stream health while the scene has the motion and audio that will occur in normal use. A static image can conceal problems that appear with movement or more complex sound.
If the stream starts but stops later, inspect the source and publisher separately. Check whether the camera is still available, whether the NAS or encoder reports a fault, and whether the internet connection remained up. For prerecorded media, test the file boundary and permissions again; a successful first file does not prove the playlist will advance. After any adjustment, repeat the test long enough to include the event that caused the failure and verify the viewer-facing result.
Decide whether this is the right operating arrangement
A camera-to-YouTube path can be straightforward when the camera, Surveillance Station feature and NAS are compatible and the channel is meant to show a live scene. It is less appropriate when your actual programme is an edited playlist, where the separate encoder and its playback logic are central. Make the source decision before buying a camera or building a media library around an assumption about what the NAS can publish.
The NAS can remain useful even if it is not the broadcaster. It may hold the original files while another encoder reads them; alternatively, an always-on cloud workflow may be preferable if you do not want a home computer to stay powered. The trade-off is that the encoder then has to access the media and be managed somewhere else. Compare file access, control, monitoring and recovery requirements, not just whether an option is described as continuous.
If the exact Synology model and software version are unknown, pause before following detailed menu instructions or purchasing hardware. Check Synology’s current compatibility information and the documentation for the installed package, then confirm the camera model if you are using one. If your aim is prerecorded playback, verify the encoder against your NAS, media and YouTube requirements 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 Synology Surveillance Station stream a playlist of videos to YouTube?
The documented Live Broadcast feature is for sending a selected live camera stream to YouTube. The reviewed Synology documentation does not establish native playlist looping or prerecorded-media broadcast through that feature. Use a separately verified encoder for stored video.
Does a Synology NAS need to stay on during a camera broadcast?
The camera workflow depends on the NAS and its supported Surveillance Station setup being available to send the stream. Synology’s documentation does not establish uninterrupted operation, so test what happens after a NAS restart, network loss or camera interruption. Plan how you will notice and respond if the stream stops.
Should I use RTMP, RTMPS or HLS?
Synology’s cited Live Broadcast help asks for an RTMP path and key, while YouTube recommends RTMPS for general encoder ingestion. Do not assume the Synology feature accepts an RTMPS endpoint in every version. HLS is for compatible encoders configured to meet YouTube’s HLS requirements, and YouTube notes its higher latency than RTMP.
What information should I check before setting this up?
Write down your NAS model, DSM version, Surveillance Station version and camera model, and decide whether your source is a live camera or stored media. For stored video, identify the encoder and test its NAS access, playlist behaviour, output settings and recovery response. Check current Synology and YouTube documentation before treating any configuration as supported.