Self-hosting your media remains a pipe dream for most tech enthusiasts because the one-time hardware cost to escape subscription hell seems too steep.

In fact, cloud storage providers and streaming services that killed off cable TV are counting on your laziness to pay the seemingly small $2 to $10 fee every month, instead of building your own NAS or HTPC, only because those options are effort and investment-intensive in comparison. However, cord-cutting is no longer the dream it once was, because half the time I find shows I want to watch are geo-restricted, and when I finally land on something watch-worthy, I'm bombarded with ads.

The natural enthusiast's response is digital sovereignty. We have turned to self-hosting a Plex, Jellyfin, or Emby media server, under the guise of saving money. The pitch is incredibly seductive because you won't have to pay a dime for Blu-ray again, and you'll also have total control over what you download and watch. However, I’m here to tell you that the pitch is a lie.

Self-hosting your media is absolutely worth doing, but if you think it’s going to save you money, your ambition is misplaced. Once you experience an uncompressed 4K Blu-ray rip, you can never go back to the heavily compressed, blocky mess of standard streaming, and chasing that quality is where your bank account starts hemorrhaging money.

20TB is never enough

But how far will you go?

When I first started out, an old laptop serving HTPC duty with an external hard drive hooked up to it felt sufficient. Soon, I discovered the massive gulf between streaming-quality video and archival-quality. Netflix 4K typically streams at a 15-16Mbps bitrate, but a 4K Blu-ray Remux of a disc with lossless audio will easily burst over 80Mbps. Suddenly, a single movie eats up 60GB to 80GB of space, and before you know it, the 4TB external drive connected to the laptop is full.

Sure, I can buy more drives or choose which movies I'd want to keep in the original, uncompressed resolution. With the drive clutter increasing rapidly, I finally folded and brought home a four-bay NAS. Here, though, running ZFS or a RAID array means buying 40TB of expensive NAS-grade hard drives, which gives me 20TB of usable, protected space. Sure, it's a far cry from the 4TB I started out with, but I'm still paying double for the peace of mind.

The only viable solution that came to mind at this time was to leave my media server drives without redundancy. Instead, to save space, I just set a smaller disk allocation for other files and services that would benefit from the RAID array.

Infrastructure costs and the maintenance toll

Yes, there are more costs than meet the eye

The hidden costs of self-hosting rarely stop at the media server. The compression I alluded to earlier helps streaming services like Disney+ and HBO Max work flawlessly over patchy mobile data and on unsteady home Wi-Fi, all funneled through a generic ISP-issued router. When you start pushing 80Mbps steady streams across your local network, especially to multiple screens, gigabit bottlenecks rear their ugly head. To circumvent this, you'll need 2.5GbE or 10GbE between the router, media server, and client.

This became painfully obvious in my own setup. My house is built with solid bricks, cement, and masonry. There is no drywall and absolutely no buffer space behind the walls to fish cables through. I already had legacy telephone and coax lines threaded through the masonry, and the sheer logistical nightmare of running fresh CAT6e cabling throughout the house to support a massive home server was an insurmountable bottleneck. I had to invest heavily in premium, high-throughput routers to pick up the slack.

The media server also ends up shouldering transcoding duties if your media client has an underpowered network interface or limited codec support. This either crushes your CPU or forces you to buy a subscription like Plex Pass and a dedicated GPU for hardware acceleration. I could circumvent this by using a mini PC hooked up to the TV or projector via HDMI in my living room. However, that's a wildly overpowered solution that is another purchase just to make the "free" media server function properly. Whether it's an NVIDIA Shield Pro or an ultra-compact mini PC, the client-side tax is unavoidable.

Lastly, there's maintenance that costs you time more than money — the one thing that's truly ours to spend. Articles rarely frame time as a literal expense, but if you spend five hours a month fixing a corrupted Docker container or trying to figure out why remote access suddenly dropped after a router update, that's time a Netflix subscription would've saved you. You are the IT department, and minimizing system downtime is your responsibility.

Self-hosting is a luxurious hobby, not a cheaper way out

Suggesting someone spin up a new Portainer instance for Jellyfin on their NAS is very different from suggesting they drop a Netflix subscription for an FOSS media library they'll have to set up, maintain, and manage. There's a small fraction of streaming renewers for whom the ever-growing cost of cutting the cable is the final straw, but for others, flying blind into something only a hobbyist would enjoy is foolhardy. Moreover, the upfront hardware cost likely exceeds a year's worth of streaming in the average household, and maintenance also costs time and money. Sometimes, a streaming service subscription might be worthwhile.