A NAS can store the children’s videos, but it does not create or broadcast a channel by itself. You need virtual-channel software to read the library and build a schedule, then a compatible playback client to receive that scheduled output.
A practical setup is therefore NAS library, channel generator, playback client, and, if required, a separate YouTube streaming path. Keep those jobs separate and you can test each part instead of assuming that one device will do everything.
How a NAS-based virtual channel works
Think of the NAS as a well-organised cupboard rather than a television station. It stores the video files and makes them available over your home network. The channel application reads those files, decides what plays next, and presents the result through a virtual tuner or playlist. A television app, media-server client, or IPTV player then plays the channel.
This is different from opening a video file in a media player. A channel has an order, timing, transitions, and a playback endpoint that another application can discover. If you want a channel that resembles a children’s television station, you might arrange short cartoons, longer films, educational programmes, and interstitials into a repeating schedule rather than asking a child to choose each title.
Tunarr documents channels built from Plex or Jellyfin media and offers a virtual HDHomeRun route or generated M3U files. ErsatzTV Legacy documents a similar workflow with local libraries and integrations with Plex, Jellyfin, and Emby. Read the Tunarr documentation and ErsatzTV introduction before choosing a path, because the exact library and client combination matters.
There are several separate places where a failure can occur:
- The NAS may not expose the folder to the channel software.
- The library import may identify the files incorrectly.
- The channel schedule may contain a title that the client cannot decode.
- The client may not support the chosen tuner or M3U route.
- A child account may still expose other live channels or libraries.
This separation is useful. If the channel is empty, inspect the library connection. If it stops between programmes, inspect the stream mode and client. If the wrong titles appear, inspect the collection and account permissions rather than replacing the NAS.
Make the NAS library accessible
Start with the existing library. Do not buy new hardware simply because a guide assumes a particular NAS model. First establish where the video files live, which device will run the channel software, and how that device will reach the files.
A local-library setup usually means the channel software reads a directory that is mounted or otherwise accessible on the host where it runs. A media-server setup means the software imports a library exposed by Plex, Jellyfin, or Emby. ErsatzTV’s documentation distinguishes local sources from media-server integrations and describes support for different media types depending on the source. Check its media documentation against your planned arrangement.
Make a small test folder before importing the whole collection. Put in a few files that represent the real library: a short episode, a longer film, a file with subtitles, and a file with the audio arrangement you expect to use. This gives you a manageable test set and avoids waiting for a full scan before finding a permissions problem.
Check these points on the host running the channel software:
- The NAS is reachable when the software starts, not only when you manually browse to it.
- The software’s account can read the files and folders.
- File names and folder names do not depend on a drive letter that exists only on your own computer.
- The network path remains available after a NAS restart or a brief network interruption.
- The files can be opened by the media server or channel software without an additional manual login.
Read access is normally enough for playback. Avoid granting write access unless the application genuinely needs it. A read-only media share reduces the chance that a mistaken scan, clean-up action, or account compromise alters the collection.
If your library is already in Jellyfin, use the server’s existing organisation rather than creating a second copy of every file. Jellyfin documents Live TV integrations including M3U and HDHomeRun sources in its Live TV documentation, but that does not mean Jellyfin alone turns an ordinary folder into a scheduled virtual channel. The channel generator remains a separate part of the workflow.
Choose the channel software
Choose based on the library source, output route, scheduling controls, and playback device you actually have. The most useful comparison is not which application sounds more complete, but which one can complete your particular path from NAS file to living-room screen.
| Option | Library path documented by the project | Delivery routes to investigate | Useful fit | Main check before committing |
|---|---|---|---|---|
| Tunarr | Plex or Jellyfin media | Virtual HDHomeRun tuner or M3U | You already manage titles in Plex or Jellyfin and want a channel schedule | Confirm the target player accepts the selected route and files |
| ErsatzTV Legacy | Local, Plex, Jellyfin, or Emby libraries | Client and stream modes documented by the project | You need local-folder access or more source choices | Check the project’s current status, installation notes, and client behaviour |
| Jellyfin with a virtual-channel generator | Jellyfin library plus an external channel generator | M3U or HDHomeRun through Live TV | Jellyfin is already your main media-server client | Verify the generator and Jellyfin integration end to end |
| Plex with a virtual tuner | Plex library plus a virtual tuner source | Live TV or tuner workflow | Plex is already installed on the household devices | Do not confuse virtual channels with antenna reception or DVR recording |
Tunarr’s documented model is straightforward when your media is already in Plex or Jellyfin: configure the source, create programming, schedule it, then expose the result as a virtual tuner or M3U playlist. It is not a NAS broadcast function. The NAS remains the place where the underlying files are stored.
ErsatzTV Legacy is worth considering when local folders are important or when your media is spread across the documented Plex, Jellyfin, and Emby integrations. The project calls this product and documentation “Legacy”, so review the current project status and installation guidance before making it the foundation of a long-lived household setup.
The stream mode also affects the result. ErsatzTV documents HLS Segmenter and MPEG-TS as primary modes. HLS Segmenter transcodes and is described as performing best around programme boundaries, while MPEG-TS is a light wrapper for clients that expect an HDHomeRun tuner. HLS Direct avoids transcoding but has fewer features and can produce client problems at programme boundaries. There is no universal setting that suits every NAS, host, file, and television.
A low-power NAS may be perfectly adequate as storage while being a poor place to perform continuous transcoding. That does not prove that every channel needs transcoding. It means you should test the chosen files and client combination, and determine whether the channel software runs on the NAS, another home computer, or a dedicated host.
Import and organise children’s videos
Create the safety boundary before you create the schedule. Put only parent-reviewed titles in a dedicated folder, collection, or library. Do not rely on a title’s filename, rating field, or the assumption that a media-server restriction will apply to a virtual live channel.
A useful structure might separate:
- Preschool programmes
- Older children’s programmes
- Films suitable for a shared family room
- Short educational clips
- Calm background content
- Breaks, station identifications, or locally created announcements
The categories should reflect how your household uses the channel, not what the software happens to call a genre. If a child watches independently, keep the channel collection narrower than the collection used by adults. A single accidentally imported film can undermine an otherwise careful setup.
After importing, inspect the metadata. Confirm that episodes belong to the correct series, that a film has not been treated as an episode, and that duplicate files have not created repeated entries. Play representative files directly through the intended media-server or channel software before adding them to a schedule.
Pay particular attention to:
- Audio tracks, especially files with commentary or multiple languages
- Subtitle defaults and whether subtitles can be disabled on the client
- Content with black frames, long credits, or unusual aspect ratios
- Files with variable frame rates or codecs not supported by the target device
- Very short clips that may expose transition problems
Parental controls need separate testing. Plex states in its parental-controls documentation that restrictions for managed users apply to movie and television libraries and video on demand, but do not apply to Live TV content or channels. That limitation is relevant even if Plex is only one part of your setup. Curate the source collection, limit access where the playback platform allows it, and test the actual child profile on the actual screen.
Use content that you are authorised to access and stream. A household channel made from files you have permission to use is a different situation from sharing the channel with other households or making it public. The software documentation does not settle copyright, licensing, territorial restrictions, or the rules for your particular titles, so check the relevant official guidance before distributing it beyond the intended audience.
Build the schedule
Create one simple channel first. A schedule that plays reliably is more useful than several channels with untested collections. Give the channel a clear name, add a small set of known-good programmes, and run it long enough to observe more than one transition.
A practical children’s schedule can mix different programme lengths without pretending that every hour must be identical. For example, you might place a short educational episode before a longer programme, then return to a collection of shorter episodes. If the application supports fixed programming blocks, use them to make the sequence predictable for adults while keeping the individual titles varied.
Decide what should happen when the collection ends. Some systems can repeat a playlist or collection. Others depend on a schedule that has been populated far enough into the future. Confirm the behaviour in the application rather than assuming that an empty queue will loop safely.
Add a small number of transitions deliberately. A short break between programmes may make the channel easier to follow, but it also gives you another type of file to test. If you create your own interstitials, keep the language and imagery suitable for every child who can access the channel.
Before exposing the channel to the family, check:
- The first programme starts correctly.
- The next programme is selected in the intended order.
- Repeated episodes are intentional rather than caused by duplicate imports.
- The channel continues after a short item and after a long item.
- The schedule behaves as expected after the channel application is restarted.
- The time zone and clock on the host match the household’s expectations.
Tunarr documents channel configuration and scheduling, while ErsatzTV’s quick-start workflow places media, collections, channels, schedules, and clients in a deliberate sequence. Follow that sequence rather than trying to configure the client before you know which output the channel will expose.
If the eventual destination is YouTube, treat that as a separate publishing decision. Read whether YouTube allows 24/7 streams made from prerecorded videos and review YouTube’s current policies and channel requirements before sending a feed. A family channel inside your home network and a public livestream have different audience, rights, moderation, and reliability concerns.
Connect a compatible playback client
The playback client is the device or application that receives the virtual channel. It might be a media-server client, a television app, an IPTV player that accepts M3U, or a system that can discover an HDHomeRun-style tuner. The channel software’s output options do not automatically mean that every television supports them.
There are two common routes in the documented workflows:
- Virtual tuner: The channel generator presents channels through an HDHomeRun-like interface. A compatible media server or client discovers that tuner and displays the channel through its Live TV area.
- M3U playlist: The channel generator provides a playlist URL or file. A compatible IPTV or media application imports it and plays the channel entries.
Choose the route that matches the client already in your home. If the television’s app handles Jellyfin well but does not import M3U playlists, the tuner route may be worth testing. If your chosen player has dependable M3U support but no virtual-tuner support, do not configure the tuner route simply because it sounds more like television.
A playback device such as an Amazon Fire TV product may be a possible client because Jellyfin lists Amazon among its client platforms, but that does not verify a particular model, app version, codec, or Tunarr/ErsatzTV combination. Confirm support for the exact device and application before buying anything.
Keep an adult-controlled account available. A child-facing profile should open the intended channel without exposing the whole library, administrative settings, or unrelated live sources. The exact controls differ by platform, so test what the child can see rather than relying on the name of a profile type.
If the aim is to send the finished channel to YouTube, the playback client is not necessarily the same as the publishing device. A computer or cloud-based workflow must receive the channel, encode or pass it through as appropriate, and send it to YouTube. For readers who want to avoid leaving a household computer running overnight, StreamNeo removes that particular operational burden by taking a prepared video and running the YouTube broadcast from the cloud after you provide the stream key. It does not replace the NAS library, channel curation, or checks on rights and child suitability.
For a different YouTube workflow using a single computer and a folder, see this guide to streaming a video folder with FFmpeg on a Raspberry Pi 5. It is a separate approach from a virtual tuner and should not be treated as proof that the NAS itself can broadcast the channel.
Test the channel across your network
Test from the room and device where the child will actually watch. A channel that plays on the host computer may fail on a television because of codec support, buffering, subtitles, audio selection, or the client’s handling of programme boundaries.
Begin with the host. Play the first file, skip or wait for the transition, and confirm that the next item starts. Then test from another device on the same network. If possible, test both a wired connection and the household’s usual wireless connection, because the route from the NAS to the client may differ.
Use a written test sheet rather than relying on a quick glance. Record the file, client, result, and any delay or error. Test at least:
- Channel discovery or playlist import
- Start-up after the client has been closed
- A transition between two different files
- Subtitles and audio-track selection
- A file with a long duration and one with a short duration
- Channel changes if more than one channel exists
- Playback after the NAS has briefly disconnected and returned
- Playback using the child account
- What remains visible when the child tries to leave the intended channel
If a programme stops at its boundary, compare the stream mode and the client. HLS Direct may reduce transcoding work but can have boundary issues with some clients. HLS Segmenter may be more suitable for certain transitions but can increase processing work. Test the actual combination instead of choosing based on a general rule.
If playback buffers, identify where the bottleneck occurs. The NAS may be reading efficiently while the channel host struggles to transcode. The host may be fine while the wireless path is weak. The client may simply lack support for the file format. A short test file encoded like the real collection can help isolate the problem without changing the whole library.
Once local playback is stable, decide whether you need a public YouTube channel. If you do, prepare a separate operational checklist covering the stream key, account access, content rights, moderation, and recovery after an interruption. For a broader comparison of unattended publishing approaches, the workflow-based comparison of cloud services for YouTube live streaming may help you frame the decision, but verify every current vendor detail on the vendor’s own site.
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 the NAS create the 24/7 channel on its own?
No. The NAS supplies the files, while virtual-channel software creates the scheduled output and a compatible playback client receives it. Some NAS devices may be capable of running additional software, but that does not change the separate roles or prove that a particular NAS can handle your files and stream mode.
Should I choose Tunarr or ErsatzTV Legacy?
Choose according to your documented library source and the client route you can test. Tunarr is aimed at Plex and Jellyfin media with virtual-tuner and M3U options, while ErsatzTV Legacy documents local, Plex, Jellyfin, and Emby sources. Neither should be treated as a universal winner without testing your NAS, files, host, network, and playback client.
Will a child profile automatically hide unsuitable live-channel content?
Do not assume that it will. Plex explicitly documents that its parental restrictions do not apply to Live TV content or channels, so curate the source library and test the child account on the final client. Keep an adult-controlled account available for changing collections, schedules, and permissions.
Can I send the NAS channel to YouTube?
Potentially, but the NAS is still only the media source in this design. You need a publishing workflow that receives the channel output and sends it to YouTube, along with permission to use the content and a review of current YouTube requirements. Test the complete path before treating it as an unattended public broadcast.