Jellyfin on NAS: Setup Guide

Jellyfin is a fully open-source, subscription-free media server. It provides core local media-library and streaming functions without requiring Plex Pass, although feature and client parity with Plex is not complete. without a Plex Pass requirement, without a cloud account requirement, and without Jellyfin tracking or a central Jellyfin cloud service; metadata providers, Chromecast and other optional integrations can still contact third-party services.. Hardware transcoding (converting video in real time so it plays on devices that can't handle the original file) is free, multi-user support is built in, and the entire codebase is open source. This guide covers deploying Jellyfin on a NAS (network-attached storage device) via Docker (software that runs applications in isolated containers), configuring your media library, enabling hardware transcoding (Intel VAAPI for Celeron-based NAS), and connecting client apps on TVs, phones, and browsers.

Jellyfin vs Plex: When to Choose Jellyfin

Choose Jellyfin over Plex when:

• You want hardware transcoding without paying for Plex Pass
• You want no Plex account requirement. Jellyfin works fully offline and local with no cloud dependency
• You want fully open-source software with no telemetry
• You are running multiple NAS devices and want per-server control without a Plex Home subscription

Plex may still be preferable if:

• You have existing Plex libraries and metadata you don't want to rebuild
• You rely heavily on Plex's integrated mobile sync and offline downloads; Jellyfin allows media downloads, but its documentation says syncing and transcoding downloads are currently unavailable.
• Your household uses Roku or older Fire TV devices that have better Plex app support than Jellyfin

For new deployments on Intel NAS hardware where hardware transcoding is a priority, Jellyfin is the better value proposition. Comparable core local-streaming functionality at zero ongoing software cost, but not complete feature or client parity with Plex.

Step 1: Deploy Jellyfin via Docker

Create a Docker Compose file for Jellyfin. On Synology (one of the leading NAS brands), create it at /volume1/docker/jellyfin/docker-compose.yml; on QNAP (another established NAS brand) at /share/docker/jellyfin/docker-compose.yml:

version: '3.8'
services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: jellyfin
    network_mode: host
    environment:
      - JELLYFIN_PublishedServerUrl=http://[NAS-IP]:8096
    volumes:
      - ./config:/config
      - ./cache:/cache
      - /volume1/media:/media:ro   # adjust path to your media folder
    devices:
      - /dev/dri:/dev/dri           # required for VAAPI hardware transcoding
    restart: unless-stopped

The /dev/dri device mount enables Intel VAAPI hardware transcoding. This is the key difference from a basic Docker deployment. Replace /volume1/media with the path to your media folder on the NAS.

Deploy with docker compose up -d. Once the container has finished starting, Jellyfin should be accessible at http://[NAS-IP]:8096.

Step 2: Add Media Libraries

On first launch, Jellyfin's setup wizard walks through library creation:

1. Choose a display language and create an admin account
2. Click Add Media Library and select the type (Movies, TV Shows, Music, etc.)
3. Click the + button to add a folder path. Navigate to /media/ (the container path mapped from your NAS media folder) and select the appropriate subfolder (e.g. /media/Movies, /media/TV)
4. Choose your metadata language and preferred metadata sources. TMDb is bundled; TheTVDB requires installing and enabling the official TheTVDB plugin.
5. Click OK then Next. Jellyfin begins scanning and downloading metadata

File naming conventions: Jellyfin follows the same conventions as Plex. Movies: Movie Title (Year)/Movie Title (Year).mkv. TV Shows: Show Name/Season 01/Show Name S01E01.mkv. Correctly named files match metadata automatically.

Step 3: Enable Hardware Transcoding (VAAPI)

Hardware transcoding converts video formats or resolutions on-the-fly when a client cannot play the file directly. On Intel NAS hardware, VAAPI offloads supported video-processing stages to the Intel GPU and can substantially reduce CPU usage, but it does not eliminate CPU work entirely.:

1. In Jellyfin, go to Administration → Playback
2. Under Hardware Acceleration, select Video Acceleration API (VAAPI)
3. The VAAPI device path should auto-detect as /dev/dri/renderD128
4. Enable Allow hardware-accelerated H.264 encoding, H.265 encoding, and AV1 decoding (if supported by your GPU)
5. Save settings

Verify hardware transcoding: start a stream that requires transcoding. In Administration → Dashboard → Active Sessions, the stream should show the codec with a hardware icon next to it. If it shows software transcode, check that the /dev/dri device mount is correctly configured in your Compose file.

Step 4: Client Setup

Jellyfin clients are available on all major platforms:

• Web browser: Access directly at http://[NAS-IP]:8096. No client install required for local streaming. For remote access via browser, configure HTTPS
• Apple TV / tvOS: Jellyfin app available on the App Store
• Android TV: Official Jellyfin app on Google Play
• iOS / Android mobile: Official Jellyfin app on both stores
• Infuse (iOS/tvOS/macOS): Third-party client with excellent Apple TV integration. Many users prefer Infuse's interface for Apple TV Jellyfin playback
• Swiftfin (iOS): Native SwiftUI Jellyfin client, polished and actively maintained
• Kodi plugin: JellyCon plugin for Kodi integration

On first launch of any client, enter your Jellyfin server URL. On the local network, use http://[NAS-IP]:8096. For remote access, set up HTTPS via NGINX Proxy Manager or a Cloudflare Tunnel.

🇦🇺 Australian Buyers: Hardware and Hosting Notes

Best NAS for Jellyfin in Australia (March 2026):

• QNAP TS-464 (~$989): Intel Celeron N5095 with VAAPI. The TS-464 has Intel UHD Graphics and supports hardware-accelerated transcoding, but simultaneous-stream capacity varies with source and target codecs, HDR tone-mapping, subtitles, output settings and other NAS workloads. PCIe slot for 10GbE if streaming to multiple devices on fast storage
• The DS423+ uses an Intel Celeron J4125 and officially supports 2GB plus a 4GB expansion module, for 6GB total. It is discontinued and has been superseded by the current DS425+.

Both models can serve multiple Direct Play clients, but practical capacity depends on aggregate media bitrate, network and storage throughput, and other NAS workloads. Hardware transcoding is free on Jellyfin. No Plex Pass equivalent required. This makes an Intel NAS significantly more valuable for Jellyfin than for Plex where the same hardware requires a Plex Pass subscription for hardware transcoding.

Remote access and NBN: Jellyfin remote streaming requires your NBN upload bandwidth. Remote-streaming capacity depends on each stream's actual or configured bitrate and other upload traffic. NBN upload speed varies by plan and access technology; the former 100/20 FTTP/HFC tier was uplifted to 500/50 in September 2025. Required upload bandwidth depends on the 4K stream's actual or configured bitrate and concurrent internet use. Suitable upload speeds are available on several current NBN tiers and are not limited to NBN 1000.