A Synology NAS can hold your property-tour video while an encoder reads it, repeats it and sends the resulting live feed to YouTube. The NAS is the file store in this arrangement; the encoder does the live-streaming work, and the exact implementation depends on your NAS model, software and chosen playback method.
There is no verified, model-independent Synology recipe for looping a prerecorded file continuously. Treat Surveillance Station’s documented Live Broadcast feature separately: it broadcasts a selected camera, not a prerecorded tour loop. Before relying on any setup overnight, confirm that its encoder can loop your file and test the complete path.
Map the NAS-to-encoder-to-YouTube workflow
Think of the setup as three jobs. The NAS stores the finished tour file. An encoder reads that file and produces a live video-and-audio feed. YouTube receives that feed at the server URL using the stream key created in Live Control Room. The encoder might run on a separate computer that can access the NAS share, or it might run in a compatible environment on the NAS itself. Those are architectural possibilities, not proof that a particular Synology model or application will loop a file reliably.
The distinction matters because file storage and video playout place different demands on a device. A NAS can serve a file successfully without having a suitable encoder application, adequate processing capacity for a chosen encoding mode, or a playback function that restarts at the end of the file. The computer-based option adds a machine to maintain, but it can separate video encoding from storage. A NAS-based option may reduce the number of devices, but depends on the exact model, DSM version and supported software.
Before choosing, write down the source format, resolution, frame rate and audio requirements. Then check which encoder implementations explicitly support those inputs, looping a local or network-hosted prerecorded file, sending YouTube Live and restarting after a failure. Do not assume that a feature called “live broadcast” means file playout. If you are still comparing arrangements, planning infrastructure for a 24/7 channel can help you account for storage, encoding, connectivity and monitoring as separate responsibilities.
The path also depends on your internet connection. The encoder sends the outgoing stream continuously, even though it reads the source file from the NAS only as playback requires. If the NAS share becomes unavailable, the encoder may lose its source; if the internet connection fails, YouTube stops receiving a healthy feed even if the file remains available locally. Decide which device needs a wired connection, what happens after a restart, and how you will notice a failure.
Store and locate the property-tour video on the NAS
Finish and review the tour before treating it as a playout asset. Check that the video starts where you intend, ends cleanly, has the correct property details, and contains no temporary edit screens or private information. A loop repeats everything in the file, including an awkward pause or an outdated price card, so a small defect becomes a recurring part of the broadcast.
Place the approved file in a clearly named shared folder rather than relying on a temporary export directory. Use a name that identifies the property and version, and keep a separate working copy if your editing process may overwrite the finished file. The encoder must be able to read the exact path or network share you give it. On a separate computer, that means the share has to be mounted or otherwise accessible under the account the encoder runs as; on a NAS-hosted implementation, it means the application needs access to that location. Confirm access after a reboot, not just while you are logged in interactively.
Avoid changing or replacing the source file during a live session until you know how the encoder handles it. Some playout workflows open a file at the start and do not follow later changes; others may fail if the file is moved or renamed. Keep the source stable during a test, and have a deliberate process for updating the tour when a listing changes. If the tour is no longer accurate, stop or replace the stream rather than continuing to show old information.
A NAS share is not automatically a second copy of the video. Keep an independent backup of the finished file and of any project assets you would need to make a correction. This is especially useful if the tour is the only approved version and the original camera footage is elsewhere. Check that the backup can be opened before deleting an older export.
Network throughput within your home or office is one consideration, but do not confuse it with the internet upload capacity needed by YouTube. The encoder reads from the NAS over your local network and sends the encoded stream over your internet connection. A file that plays smoothly on a laptop does not by itself demonstrate that the internet connection can sustain a live feed for long periods.
Choose where the encoder runs
Start with the file-looping requirement, not the device you already own. The implementation must explicitly support repeating a prerecorded file and delivering a YouTube Live feed. Confirm whether it reads a network share, which codecs and audio formats it accepts, whether it can use the desired transport protocol, and what happens when the source ends, the share disconnects or the host restarts.
| Arrangement | What it does | What to verify before depending on it |
|---|---|---|
| Separate computer reading a NAS share | The computer runs the encoder and reads the tour from the NAS over your network. | The share remains accessible to the encoder account; the computer can encode the selected format; looping and restart behaviour work as expected. |
| Encoder in a compatible NAS software environment | The NAS stores the file and may also host the encoder, if the exact model and software support the required application. | Model and DSM compatibility, application support, file access, encoding capability, and how the process starts and recovers. |
| Camera broadcast through Surveillance Station | A selected camera source is sent to YouTube using the documented camera-broadcast feature. | Whether the source is actually a camera stream and whether that meets your use case; it does not establish prerecorded-file looping. |
A separate computer may be the more straightforward choice if a supported encoder already runs on it and you can keep it powered, connected and monitored. It also gives you a place to inspect logs or restart playback, but it introduces another machine whose updates, sleep settings and power supply matter. If that computer is switched off at night, the NAS alone will not keep the stream running.
A NAS-hosted encoder can appear simpler, but do not install a container or application based on a general guide that omits your model and DSM version. Synology’s Container Manager availability page is model-dependent. Check the current compatibility details, then verify that the specific encoder supports file looping and YouTube output. The availability of a package or container environment is not evidence that it supplies a dependable 24/7 playout configuration.
If you choose a computer, an always-on arrangement still needs restart planning. For example, check whether the operating system sleeps, whether the encoder launches after login or reboot, and whether it reconnects when the network returns. A walkthrough on keeping an ASMR stream running after Windows restarts covers the general restart problem; adapt the checks to the encoder and machine you actually use. Do not assume the steps for one application prove another can recover correctly.
Configure YouTube’s server URL and stream key
First confirm that the channel can go live. YouTube says a channel must be verified and must not have had live-streaming restrictions in the prior 90 days; enabling live streaming for the first time may take up to 24 hours. Check YouTube’s current live-streaming eligibility guidance before scheduling a property tour around a first broadcast.
In Live Control Room, create or select the stream and obtain its server URL and stream key. Enter both in the encoder’s YouTube destination settings. The URL tells the encoder where to send the feed; the key identifies the stream. YouTube’s encoder setup instructions explain where these values fit in the workflow. Interface labels can change, so use the current Live Control Room rather than an old screenshot as your authority.
Treat the stream key like a password. Do not put it in a public screenshot, shared document or tour file, and do not send it to someone who only needs to watch the channel. If it is exposed, replace or reset it in YouTube and update the encoder. A reusable key is convenient for an ongoing channel but makes secure storage and access control more important; a one-time key can suit a single event but may require a new configuration. The practical choice depends on how you manage credentials and how often the encoder needs to be reconfigured. For a closer explanation, see reusable and one-time YouTube stream keys.
Use a transport and encoding mode supported by both YouTube and your selected encoder. YouTube recommends RTMPS for encrypted transport and documents H.264, H.265 and AV1 recommendations, but the usable options depend on the encoder and workflow. Its live encoder settings guidance gives mode-specific recommendations. Match guidance to your chosen codec, resolution and frame rate rather than copying a figure without its context.
For example, YouTube lists 10 Mbps as its recommended H.264 bitrate for 1080p30. That is a recommendation for that specific combination, not a universal minimum or a promise that your connection can sustain it. YouTube’s streaming tips recommend 20% upload-bandwidth headroom above the stream bitrate. Test the actual upload path at the encoder’s intended setting and leave room for normal variation; if the connection struggles, lower the stream settings or improve the connection before relying on it. A bitrate and video-setting comparison can help you think through source and output settings, but use YouTube’s current guidance for the final configuration.
Test the file, loop and stream before going live
Run a test that exercises the whole chain, not just local playback. Use an unlisted stream or another suitable test arrangement, check YouTube’s preview, and watch the broadcast from a separate device. Confirm that the picture is correct, the audio is present and at a sensible level, and the tour remains legible on a phone as well as a desktop display.
Let the file reach its end and confirm that the encoder starts it again in the intended way. Check the transition: some tours can tolerate a short pause or fade, while others should appear seamless. Confirm whether the opening slate repeats, whether audio cuts cleanly, and whether the encoder continues sending a feed between repetitions. A player that loops locally is not enough; the YouTube preview should show the same expected behaviour.
During the test, inspect YouTube’s stream-health information and the encoder’s own status. Look for dropped frames, audio/video mismatch, an unexpectedly low-quality image or intermittent connection warnings. If you see a problem, change one variable at a time—such as bitrate, resolution or frame rate—and repeat the test. This gives you a clearer indication of which change helped than altering several settings at once.
Test failure recovery deliberately. If practical, stop and restart the encoder, restart the host machine, and briefly interrupt access to the NAS share in a controlled test. See whether the encoder resumes the correct file and whether YouTube receives a healthy feed again. Do not run a disruptive test during a public broadcast. Write down the recovery steps, including where the stream key is stored and who can restart the encoder, so someone else can respond if you are unavailable.
Finally, check the channel’s archive expectations. YouTube says streams under 12 hours are automatically archived. Do not assume a longer-running loop will be preserved as one complete replay; plan how you will handle recording and archive continuity, and verify the behaviour in your own workflow. A 24/7 live channel and a usable archive are related but separate requirements.
Plan for the parts that fail overnight
A 24/7 stream is an operating process, not just a successful first connection. The video might be sound while the NAS share becomes unreachable, or the file may continue to play while the computer loses its internet connection. Decide who will receive alerts, how they will check the stream, and what action they can take without exposing the stream key.
Make a short runbook for routine checks and common failures. Record the tour file’s approved path, the encoder’s start procedure, the YouTube destination configuration location, and the steps for confirming a healthy preview. Keep secrets out of the runbook itself; note where authorised operators can retrieve them securely. Include a procedure for replacing a tour when property information changes, and a way to confirm that the new version is the one currently being broadcast.
Consider power and connectivity as separate dependencies. A battery backup may give equipment time to handle a short interruption, but it does not replace a stable internet connection or guarantee that an encoder recovers. Likewise, a fast internet plan does not help if the host computer sleeps or the NAS share is unavailable. Test your own chain and avoid claiming uninterrupted operation until you have evidence from your setup over the conditions that matter to you.
You may decide the file should live on the NAS while an always-on computer handles encoding, or find a compatible NAS-hosted method after checking the exact model. If the persistent task of keeping a local host awake, connected and supervised is the part that causes trouble, StreamNeo can remove that specific computer-running burden for a prepared video: it takes an uploaded file and runs a YouTube stream without your computer needing to stay on. It is YouTube-only, and it does not validate a Synology NAS encoder configuration or change the need to prepare and check the tour and channel.
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 I loop a property-tour file directly from any Synology NAS?
No model-independent, tested configuration is established here. Check the exact NAS model and DSM version, then verify that your chosen encoder explicitly supports reading the file and repeating it while sending to YouTube Live. Test the loop and its recovery behaviour before relying on it.
Is Surveillance Station Live Broadcast the same as a prerecorded tour loop?
No. Synology documents Live Broadcast as selecting a camera source for broadcast to YouTube. That feature does not establish that Surveillance Station will play and repeat a prerecorded property-tour file.
Should the encoder run on the NAS or a separate computer?
Either arrangement may be considered, but suitability depends on supported software, file access, encoding capability and recovery behaviour. A separate computer can be easier to assess if it already supports the encoder, while NAS-hosted software depends on model and DSM compatibility. Choose only after confirming the specific implementation and testing it.
Will YouTube archive an always-on tour loop as one video?
YouTube says streams under 12 hours are automatically archived, so do not assume a longer-running broadcast will become one complete replay. Check the current YouTube guidance and test your archive workflow separately from the live loop.