A home media server without a degree in networking
One old laptop, one external drive and an evening gets you most of the way. The two things that determine whether it feels fast or frustrating are both decided before you install anything.
A media server does one straightforward job: it takes files sitting on a drive somewhere in your house, organises them with artwork and descriptions, and serves them to your TV, phone or laptop through an app that behaves like a streaming service. Your own files, your own catalogue, no licence checks.
It is genuinely useful for digitised discs, camera footage and family video, music libraries too large for phone storage, and anything you bought DRM-free and want to watch on the TV without plugging anything in. It's a tidy solution to a real problem, and the setup is much less daunting than its reputation.
The software
Three options dominate, and they're more similar than different.
| Option | Character | Suits |
|---|---|---|
| Plex | Most polished; broadest client app support; some features behind a paid tier; relies on a Plex account | People who want it to work without tinkering |
| Jellyfin | Free and open source, no account, no paid tier; apps are less refined in places | People who'd rather not depend on a company |
| Emby | Between the two; some features paid | People who want a middle path |
Any of them will work. If you've no strong opinion, start with Jellyfin because it costs nothing and locks you into nothing; move to Plex if you find yourself fighting a client app.
The hardware
An old laptop is a fine server. So is a mini PC or a desktop you've stopped using. The specification that matters is not the one people assume.
Storage
An external USB drive is a perfectly reasonable start. Video is large — a DVD-quality film is a few gigabytes, a Blu-ray-quality one can be twenty or more — so buy more capacity than you think you need.
Understand what this is: a single drive is storage, not backup. Drives fail, and the ones with your entire ripped collection fail at the worst time. If the contents are irreplaceable, you need a second copy somewhere. A two-bay NAS with mirroring is the neat answer later; a second external drive you copy to monthly is the cheap answer now.
Processor: the bit that actually decides everything
Here's the crux, and it's worth understanding before you buy anything.
When a client can play a file exactly as it is, the server just sends the bytes across. This is direct play, it costs almost no processing power, and a very modest machine handles several streams at once.
When the client can't handle the file — wrong codec, wrong container, subtitles that must be burned in, or not enough bandwidth for the full-quality version — the server has to decode and re-encode it on the fly. This is transcoding, and it is enormously more demanding. A single 4K transcode will flatten a CPU that handles ten direct plays without noticing.
Which means the specification question isn't "how fast is the processor" but "will it need to transcode, and can it do that in hardware?" Modern Intel chips include Quick Sync, a dedicated video encoding block that handles transcodes far more efficiently than the general-purpose cores. An older Intel machine with Quick Sync will comfortably outperform a newer one without it for this specific job. AMD and Nvidia have equivalents. Check for hardware acceleration support before buying anything.
The other half of the answer is to avoid transcoding in the first place: pick client devices that can play your files natively. A current streaming stick, smart TV app or games console handles the common formats directly, and then server load stops mattering.
Getting the files organised
Media servers identify content by matching filenames against online databases. Sloppy names produce a library full of wrong artwork and missing descriptions, and fixing it later is tedious. Follow the naming convention in your chosen server's documentation from the start.
The general shape is consistent across all three:
Films/
The Third Man (1949)/
The Third Man (1949).mkv
TV/
Some Series/
Season 01/
Some Series - S01E01.mkv
Year in brackets for films, S01E01 for episodes, one folder per title. Get this right and matching is nearly automatic.
Network
Wire the server. Not optional if you can avoid it. The server is pushing large continuous streams and Wi-Fi variance causes buffering that looks like a server problem but isn't. Clients can be wireless; the server should be wired.
Give it a fixed address. Set a static IP or a DHCP reservation in your router, so the server doesn't move when it reboots and break every client at once.
The second place people come unstuck: remote access
Watching at home is easy. Watching from elsewhere is where things get fiddly, and where people make security mistakes.
The common advice is to forward a port on your router to the server. It works, and it also publishes your media server to the entire internet, where it will be found by automated scanning within hours. If you do it, the server must be kept updated and every account on it needs a strong password. A media server with a weak password exposed to the internet is a genuine risk, not a theoretical one.
Better options, roughly in order:
- A mesh VPN (Tailscale, ZeroTier and similar) creates a private network between your devices without exposing anything publicly. Setup is much easier than traditional VPN configuration, and this is the option to try first.
- Plex's own relay handles remote access without port forwarding, at reduced quality.
- A reverse proxy with HTTPS if you're comfortable with that and want a proper hostname.
- Download before you leave. Unglamorous and entirely effective for a flight.
Realistic expectations
It won't be as seamless as a commercial streaming app — those have enormous engineering behind them. Client apps vary in quality, artwork matching occasionally needs manual correction, and something will break after an update.
What you get in return is a library that answers to you: no titles disappearing when a licence lapses, no quality caps, no account required. For a collection you've built deliberately, that's usually the trade worth making.
Start small. One old machine, one drive, twenty films, a wired connection. Get that working end to end before you buy a NAS.