One weekend Project
Building a home media stack
A media server is often the service that wins over the rest of the household. Done well, it plays everything instantly on every screen. Done badly, it stutters, transcodes everything and breaks when a vendor changes its terms. This project builds the first kind.
- IntermediateDifficulty
- 1 weekendTime
- Host + NASGPU or video engine helps
- $0 and upMostly drives
Legal content only
This project is for media you have the right to keep: discs you own and have copied for personal use where the law allows, family videos, recordings of free broadcasts and media distributed without restrictions. We do not cover acquiring content you do not have rights to.
The pieces
- Media server. Indexes the library, fetches artwork and descriptions, tracks what everyone has watched and streams to clients.
- Client apps on televisions, streaming sticks, phones and browsers. In practice these decide whether the household is happy.
- Storage on the NAS, shared with the server using the Shared Storage for Containers pattern.
- Optional extras: a request portal where family members ask for titles you own on disc, an audiobook and podcast server, a subtitle manager, a tool that checks files for corruption and incompatible formats, and live television from a network tuner and antenna.
Choosing a media server
There are capable open-source servers and polished commercial ones. Two lessons from recent years should shape your choice:
- Terms change. During 2025 and 2026, commercial media servers moved remote streaming behind paid plans and raised lifetime license prices sharply. Open-source servers cannot be withdrawn from you in the same way.
- Clients matter more than servers. A server is only as good as its app on your television. Test on the actual devices your household uses.
From the Bench
The best way we have found to choose is to run two servers side by side, each in its own container, pointed at the same read-only library. A week of the household using both settles the question faster than any comparison chart.
Organizing the library
- Use one folder per type, such as movies, shows, music, audiobooks and home video, each in its own dataset or folder.
- Name files and folders consistently with title and year, and episodes with season and episode numbers. Servers identify media from names; good names mean correct artwork and no duplicates.
- Give every container the same path for the library so moves and links work. See Shared Storage for Containers.
- Mount the library read-only for the server. Only the import process needs write access.
When archiving discs, keep a lossless or high-quality copy if storage allows, and an efficient copy for streaming if not. A full-quality disc copy of 40 to 50 GB can often be re-encoded to well under 10 GB with little visible loss, at the cost of hours of processing.
Transcoding and hardware
Transcoding converts a file on the fly when a client cannot play it directly or the connection is too slow. It is the most demanding thing a media server does.
- Aim for direct play. Formats and clients that play files as they are need almost no CPU. Most stutter problems at home are transcoding problems.
- Use hardware transcoding. The video engine built into many modern processors, or a modest graphics card, can transcode several streams at a few watts. Software transcoding of high-resolution video can saturate a strong CPU with a single stream.
- Pass the video device through to the container or VM that runs the server.
Watching away from home
Reach the server through your mesh VPN rather than publishing it; see Mesh VPN Remote Access. Expect your home upload speed to be the limit. A high-bitrate film that plays perfectly on the living room television may stutter on a phone across town. Lower the remote quality setting, let hardware transcoding reduce the bitrate, or download the episode to the device before you leave.
Media servers can also expose a surprising amount if published directly to the internet, and several have had serious vulnerabilities. Keep yours private.
Network placement
Televisions and streaming sticks often discover media servers using broadcast and multicast traffic that does not cross VLANs. The simplest working design puts the server where the televisions can reach it, or adds explicit firewall rules for the server's port. See VLANs and Segmentation.
Backups
- Back up the server's configuration and database nightly. Watch history, user accounts and collections are tedious to recreate.
- Treat disc copies as the replaceable tier. They can be re-made from the discs, so a second local copy may be enough.
- Treat family video as irreplaceable, with full 3-2-1 protection. See Backup Strategy.
Verify
- Every television and phone in the house plays a film, a show and music without transcoding where possible.
- The server's dashboard shows which streams transcode and why.
- A remote stream over the mesh VPN plays at a sensible quality on mobile data.
- Deleting and recreating the server container keeps watch history, because its configuration was backed up and restored.