Revive Old NAS and Office PCs Into a Jellyfin Media Server

Why your dusty NAS or office PC is perfect for Jellyfin

Repurposing an old NAS or office PC into a Jellyfin media server means turning outdated, idle hardware into a self-hosted streaming hub that stores your library, serves it to any device in your home, and keeps you independent from changing corporate streaming platforms and subscription models.

If you have a retired office desktop or aging NAS sitting in a cupboard, you already own the heart of a DIY home server. An office PC that feels sluggish for everyday work is still more than equipped to stream movies and handle transcoding for your family. Old NAS units that no longer receive the latest interface updates are not useless either; not getting the newest software does not make them obsolete, and you can extend NAS lifespan by turning them into backup nodes or container hosts. In both cases, you gain a 24/7 personal media server that gives you control over your collection and avoids “enshittified” streaming experiences. Self-hosted streaming means your library keeps working even if a company changes plans or policies.

Jellyfin is a free, open‑source media server that plays your library on any device in the house, transcodes on the fly, and never asks for a credit card. That makes it an appealing alternative if you are moving away from platforms that push more subscriptions and ads. The catch: you should be willing to use a bit of command line and basic configuration, but you do not need a rack of servers or a computer science degree.

Pick the right hardware and avoid the usual traps

Before installing a Jellyfin media server, you need to decide where it will live. For most people, the fastest route is to repurpose old NAS hardware or an old office PC rather than buying new gear. Many home media setups start with someone digging up an old desktop and using it as a DIY home server, which keeps machines out of landfills and frees your budget for storage drives. If your old PC has an Intel CPU from roughly the last decade, it likely includes Quick Sync hardware video encoding, turning it into a transcoding workhorse for multiple high‑resolution streams.

On the NAS side, an older box that no longer receives the latest interface updates still has value; you can repurpose old NAS units as secondary backup nodes, remote backup targets, or container hosts to extend NAS lifespan instead of discarding them. One quotable takeaway is: “Not getting the latest DSM updates doesn’t make your old NAS completely outdated.”

The most common mistakes are picking the wrong graphics hardware and enabling the wrong online services. For transcoding, you should avoid AMD graphics for Jellyfin because their encoders and driver support are weaker than Intel or NVIDIA for this purpose. On repurposed NAS systems, you should avoid services that connect back to the original vendor’s cloud when you are using unofficial software stacks, even though core tools like storage and file managers keep working fine. Staying within those limits keeps your setup stable and avoids frustrating bugs later.

Step‑by‑step: Turn old hardware into a Jellyfin media server

Here is the practical sequence I would talk a friend through when they want self-hosted streaming using Jellyfin on a recycled PC or repurposed NAS. The steps look long on paper, but in real life they are mostly “type a command, wait a moment, click next.” You only need basic command‑line comfort, such as running a few copy‑paste commands and editing a text file.

1. Prepare the machine: Wipe or free space on your old office PC or repurpose old NAS storage so you have a clean place for media and the server. Make sure the CPU supports the instruction sets required by modern software; decade‑old systems with suitable processors are fine.
2. Install a lean OS: For a dedicated Jellyfin media server, install a lightweight Linux distribution so more resources go to streaming and transcoding and graphics drivers are easier to handle. If you keep your old NAS OS, verify it still receives security updates or can run containers.
3. Install Docker and Docker Compose: On your chosen OS, install Docker and Docker Compose, since you will run the Jellyfin media server inside a container for easier updates and isolation.
4. Create a Jellyfin project folder: Make a dedicated folder on the machine to hold configuration, then create a docker-compose.yml file inside that folder to describe how Jellyfin should run.
5. Define the Jellyfin container: In docker-compose.yml, point to the official Jellyfin image, set network mode to host, and configure the container’s ports so the server will be reachable on your network.
6. Map your media and config storage: In the same compose file, map your local media folders and configuration folders into Docker volumes so Jellyfin can read your movies and shows and save its settings outside the container.
7. Set permissions and hardware access: Configure the container to run with the correct user and group IDs so it can access your files, and pass through your Intel GPU so hardware acceleration can handle the heavy transcoding work instead of the CPU.
8. Start the Jellyfin media server: Run the command docker compose up -d in that folder to launch Jellyfin in the background, giving you a running Jellyfin media server on your DIY home server or repurposed NAS host.
9. Run the Jellyfin setup wizard: In a browser on your network, open the server’s IP address on port 8096, follow the wizard to create an admin account, add libraries from the media folders you mounted, and confirm remote access settings.
10. Enable hardware transcoding: Log in to the Jellyfin dashboard as admin, go to Playback → Transcoding, choose the hardware acceleration method that matches your GPU, and tick hardware decoding boxes for the codecs you use so the GPU does the work instead of the CPU.

When this ordered list is done, you have a Jellyfin media server that plays your library on any device in the house, transcodes on the fly, and never requests a subscription. On top of media streaming, you can configure extra services on the same host, such as a VPN layer or backup sync containers, to turn it into a more complete DIY home server.

Go further: Old NAS as backup node and remote access hub

Once Jellyfin runs smoothly, you can extend NAS lifespan by giving older boxes new roles. A retired NAS that you no longer trust for main storage can still work as a secondary backup node, central dashboard, or remote access hub. Configuring it as a secondary backup node adds redundancy to your setup, especially if you use it as an offsite rig that pulls essential files from your main NAS for a classic 3‑2‑1 backup pipeline. You can configure Tailscale or WireGuard inside a container and schedule Rsync tasks to automate those backups inside tools built for that purpose.

Older NAS units also make surprisingly capable container hosts; you can stack dashboards, notification servers, DNS sinkholes, or proxy managers on them so you do not lose access when your experimental lab nodes go offline. On the other side, an old office PC repurposed as a Jellyfin media server can act as your self-hosted streaming center, while the NAS focuses on storage and backup. By keeping roles modular like this, you can upgrade one piece at a time and keep using older gear for years beyond the manufacturer’s preferred lifecycle.

The main gotcha is to treat these machines as infrastructure, not consumer appliances. Avoid enabling proprietary cloud hooks on unofficially supported NAS setups and keep firmware patched where available. Focus on simple, well‑understood tasks—media serving, backup, remote access—rather than chasing every new feature. That mindset keeps maintenance low and stability high.

Is it worth the effort?

Turning a forgotten PC or old NAS into a Jellyfin media server gives you a quiet 24/7 box that stores your library, streams it to every screen, and puts you back in control. You avoid subscription creep, feature removals, and policy changes from big streaming platforms while keeping hardware that would otherwise gather dust in service. Self-hosted streaming with Jellyfin means your movies and shows are available on your terms, with multiple user profiles and DVR features right from the start.

The trade‑off is that you need to be comfortable with a few command‑line commands and container concepts, and you need to pay attention to basic compatibility: favor Intel or NVIDIA graphics for transcoding, keep old NAS units away from unsupported cloud services, and verify security updates where possible. If you can live with those caveats, repurposing old NAS hardware and office PCs into a DIY home server is one of the most satisfying upgrades you can do without buying new gear.