A home media server securely streams video content from a desktop to a TV, laptop, and phone.
A spare PC can become a personal streaming server in an afternoon. Whether it works well depends on a few details that are easy to miss: how your files are encoded, which devices will play them, what your upload bandwidth is, and how you reach the server from outside your home.

TechRepublic's Liz Ticong covered this on November 16, 2026. She looked at Plex, Jellyfin and Emby as ways to turn a dusty computer or NAS into a home streaming hub. The pitch is sound, but the details need tightening, especially the licensing claims. Here is how the setup works and where the fine print sits.

A home media server securely streams video content from a desktop to a TV, laptop, and phone. What a personal media server does​

The server stores and indexes your media. A client app, smart TV or browser asks for playback from another device. TechRepublic describes the software scanning your chosen folders and building a catalog with posters and descriptions. The original files stay on storage you control.

These tools don't supply a catalog the way Netflix or Disney+ do. You bring your own files, and you need the rights to use them. A media server doesn't guarantee access to anything you don't already have.

Jellyfin's documentation says the software is self-hosted and can run without an internet connection. Online metadata providers won't work offline. Treat the networking details below as Jellyfin defaults, not rules for every product.

Direct play vs. transcoding​

"Just stream the file" skips the part that decides whether an old PC copes. Jellyfin's codec documentation describes three outcomes:

  • Direct play: the container, video, audio and subtitles are all compatible with the client. This is the goal because it costs the server almost nothing.
  • Direct stream (remux): the audio, container or subtitles aren't supported, so the server rewraps or converts those parts.
  • Video transcoding: the video codec itself isn't supported. Burned-in subtitles can also force this. Jellyfin calls burning in subtitles the most intensive method, because the server decodes and re-encodes the video at once.

Jellyfin's codec table covers recent client software and operating system versions. Legacy versions may differ. Two Windows-specific notes from that table:

  • HEVC playback in browsers on Windows needs the HEVC video extension from the Microsoft Store.
  • Dolby Vision on Windows works only in Edge, and it needs the Dolby Vision add-on from the Store.

Will your old PC cope?​

Jellyfin's hardware guidance is the most detailed source available. It offers a broad guide, not a minimum requirement, and it is not a spec for Plex or Emby.

  • Storage: a 100 GB SSD for the OS, Jellyfin files and transcoding cache, on top of your media storage. Jellyfin suggests adding more on Windows 11 or with many large files.
  • Memory: at least 8 GB for an average deployment. It suggests more on Windows 11 because the OS is heavier.
  • Network: Gigabit Ethernet or faster. Wi-Fi and powerline aren't recommended.
  • Upload bandwidth: at least 20 Mbps for remote access. Below 100 Mbps of total upload, Jellyfin suggests capping it at 70% of your upload speed so the rest of your household's internet isn't starved.
  • GPU: Jellyfin says a server with no GPU isn't recommended, because video transcoding on the CPU is very demanding. HDR-to-SDR tone-mapping makes it worse.

Hardware acceleration matters here. Jellyfin supports Intel Quick Sync, NVIDIA NVDEC/NVENC, AMD AMF, VA-API on Linux, Apple Video Toolbox on macOS, and Rockchip RKMPP on Linux. Some pipeline stages can fall back to software, which raises CPU load and slows transcoding. Jellyfin also recommends its own jellyfin-ffmpeg build, because other FFmpeg binaries give only partial acceleration.

Two cautions from the same guide:

  • Raspberry Pi and other single-board computers: most are too slow for an acceptable experience.
  • Prebuilt NAS appliances: they often have low-end processors and awkward software environments.

If your "old computer" is a mid-2010s desktop with Intel integrated graphics, it may do fine. If it's a low-power Atom box, you may be disappointed.

The platform comparison, with corrections​

TechRepublic's table gets the broad strokes right. Several cells are too vague to rely on when you're choosing.

Plex​

Local playback of your own media on the same network is part of the free experience. The remote-video rule is more specific than "generally requires a paid pass." Plex's support documentation says that since April 29, 2025, remote video playback from a Plex Media Server in affected apps needs one of three things:

  • the server admin has an active Plex Pass, which also covers other users streaming from that server;
  • the viewer's own account has an active Plex Pass; or
  • the viewer's account has an active Remote Watch Pass.

Affected apps include Android, iOS, PlayStation, Plex for Windows/Mac/Linux, Roku, supported smart TVs, the web app and Xbox. Plex says more apps will enforce the rule over time. Music in Plexamp and photos in Plex Photos aren't restricted.

You also have to enable Remote Access on the server to reach it from another network. Plex counts any connection that can't be detected as local as "remote." Its documentation lists VPNs, multiple subnets, containers without host networking, and privacy settings that block local connections as common causes. So a VPN-based setup can accidentally trip the paywall.

Jellyfin​

Jellyfin is free and open source, and you configure remote access yourself. Its networking documentation lists four external access options:

  • forwarding ports directly to the internet, which it marks "not recommended";
  • a reverse proxy;
  • a VPN; and
  • a VPS acting as a reverse proxy to your home network.

TechRepublic's VPN suggestion is reasonable, but it isn't the only sensible design. Jellyfin says opening a port directly to the internet is insecure and not recommended. It also warns that reverse proxy external access settings only work if known proxies are set up correctly. Jellyfin's hardware guide adds that the server isn't designed to be exposed directly to the internet and should sit behind a properly configured firewall.

The Jellyfin networking page says global remote access settings live under Networking and Remote Access Settings. Per-user permissions are under Users, then Edit User, with an option to allow remote connections. Disabling remote access for accounts that only watch at home is a cheap hardening step.

Emby​

"Some app playback requires payment" hides a lot of variation. Emby's feature matrix shows the following.

AreaFreePaid
Library browsing, organization and metadataYesYes
Users, user management, parental controlsYesYes
Windows, Linux and Mac appsOne-minute limited playbackFull playback with Premiere
iOS and AndroidLimited playbackFull playback via App Unlock or Premiere
Roku, Apple TV, LG and Samsung smart TVsFull playbackPremiere adds extras such as Live TV
Android TV and Fire TVFull playback on up to 5 TV devicesPremiere removes the limit
Xbox and PS4One-minute limited playbackFull playback with Premiere

Hardware-accelerated transcoding and HDR tone mapping are Premiere features, with an exception: Nvidia Shield and WD NAS devices don't need Premiere for hardware acceleration. Premiere is tied to the server by an installed key, and the connected server's status governs access.

Your target device decides the cost. An Emby setup that streams to a Roku is free, but the same library on a Windows desktop app costs money for full playback.

A sensible way to start​

TechRepublic's advice to start small is the right call. Here is one way to turn it into a checklist:

  1. Put a small sample of your real files on the server. Include different codecs, an HDR file and something with subtitles.
  2. Play each one on every device you care about. Check the server dashboard to see whether it's direct playing or transcoding.
  3. If transcoding is common, look at hardware acceleration before buying anything else.
  4. Keep remote access off until you need it. When you do, choose a VPN or a correctly configured reverse proxy over a raw port forward.
  5. Check your upload speed against the 20 Mbps guideline if you plan to watch away from home.
  6. Re-check the licensing for your particular clients before committing. Both Plex's remote rules and Emby's per-app playback entitlements vary by device.

Backups and upkeep​

A media server isn't a backup system. TechRepublic is right that irreplaceable material, like family recordings, should be copied elsewhere in case a drive fails. Costs such as electricity, drive capacity and your own admin time are real, but neither the article nor the documentation reviewed here puts a number on them.

Some readers will find this isn't worth the effort. If you mostly watch subscription catalogs, a home server adds little. If you have a large personal library and a spare machine, it's a useful home-lab project that teaches storage, networking and security along the way.

Bottom line​

Plex, Jellyfin and Emby all let you stream your own files from your own hardware. The practical difference is in the details: Plex's remote video pass dates from April 2025, Emby's free tier depends on the client, and Jellyfin leaves remote security to you. Test with your own files and devices before you migrate anything.

 

References

  1. Your Movies, Your Server: How Personal Streaming Libraries Work - TechRepublic TechRepublic 2026-11-16T14:47:44+00:00
  2. Requirements for Remote Playback of Personal Media | Plex Support support.plex.tv
  3. Hardware Selection | Jellyfin jellyfin.org