Run Your Own Jellyfin Media Server in Minutes

// Before you start

What you need

A Windows, Mac, or Linux computer with at least 4 GB RAM
Some media files already on your computer (movies, TV shows, music)
About 15 minutes and a stable internet connection
Administrator / sudo access on your machine

Step 1 of 6

Download the Jellyfin installer for your OS

3 min

Jellyfin publishes ready-to-run installers on their official downloads page. You do not need to build anything from source. Go to https://jellyfin.org/downloads/server and grab the installer for your operating system. On Windows this is an .exe file. On Mac it is a .dmg. On Ubuntu/Debian Linux you will use the terminal commands below instead.

Terminal · mac

$ # Ubuntu / Debian Linux only — skip if you are on Windows or Mac:

$ curl -fsSL https://repo.jellyfin.org/install-debuntu.sh | sudo bash

What you should see

On Linux you should see lines like 'Adding Jellyfin repository' and 'Setting up jellyfin' ending without errors. On Windows/Mac, the installer wizard opens.

This might happen

curl: command not found on a fresh Linux system

Run: sudo apt-get install -y curl then retry the command above.

Step 2 of 6

Install FFmpeg (required for video transcoding)

2 min

Jellyfin uses FFmpeg to convert video on the fly so it plays on any device. Without it, many files will refuse to play. The Debian/Ubuntu script above usually installs it automatically. If you are on Windows, the Jellyfin Windows installer bundles FFmpeg for you. On Mac, use the Homebrew command below.

Terminal · mac

$ # Mac only (requires Homebrew — get it at https://brew.sh):

$ brew install ffmpeg

$ # Ubuntu / Debian — confirm it is already present:

$ ffmpeg -version

What you should see

You should see a version line starting with 'ffmpeg version 6...' or similar. Any version line means it is installed.

This might happen

brew: command not found on Mac

Install Homebrew first by pasting the one-liner from https://brew.sh into Terminal, then re-run the brew install command.

Step 3 of 6

Start the Jellyfin service

1 min

On Linux the installer registers Jellyfin as a background service. You just need to start it. On Windows and Mac, the installer adds Jellyfin to your system tray or Start Menu — simply launch it from there and skip the command below.

Terminal · mac

$ # Linux only:

$ sudo systemctl enable --now jellyfin

$ # Confirm it is running:

$ sudo systemctl status jellyfin

What you should see

You should see a green 'active (running)' line in the status output. On Windows/Mac you will see a Jellyfin icon appear in the system tray.

This might happen

Status shows 'failed' or 'inactive' on Linux

Check logs with: sudo journalctl -u jellyfin -n 50 Look for a port conflict on 8096 — another app may be using it.

Step 4 of 6

Open the web interface and run the setup wizard

5 min

Jellyfin's entire interface lives in your browser. Open the URL below. A first-run wizard will walk you through creating an admin account and pointing Jellyfin at your media folders. You do not need to touch any config files.

Terminal · mac

$ # Open this URL in any browser on the same machine:

$ http://localhost:8096

What you should see

A Jellyfin welcome screen appears asking you to choose a language and create an admin username and password.

This might happen

Browser shows 'This site can't be reached'

Wait 30 seconds and refresh — Jellyfin can take a moment to start. If it still fails, confirm the service is running (Step 3) and that your firewall is not blocking port 8096.

Step 5 of 6

Add your media library

3 min

During the wizard (or later via Dashboard → Libraries → Add Media Library) you tell Jellyfin where your files live. Pick a content type (Movies, TV Shows, Music, etc.), then browse to the folder on your hard drive that contains those files. Jellyfin will scan the folder, download artwork and metadata from the internet, and build your library automatically.

Terminal · mac

$ # No command needed — use the browser wizard at:

$ http://localhost:8096/web/index.html#!/wizardlibrary.html

$ # Or after setup, go to:

$ http://localhost:8096/web/index.html#!/dashboard

What you should see

After adding a folder and clicking Next, Jellyfin starts a background scan. You will see your media appear with posters and descriptions within a few minutes.

This might happen

Jellyfin cannot see your media folder

On Linux, the jellyfin service user needs read permission on your folder. Run: sudo chmod -R a+rX /path/to/your/media

Step 6 of 6

Install a Jellyfin app to watch on other devices

2 min

Jellyfin has free apps for Android, iPhone, Apple TV, Roku, Fire TV, Android TV, and more. Search 'Jellyfin' in your device's app store. When the app asks for a server address, enter your computer's local IP address and port 8096, for example http://192.168.1.50:8096. You can find your local IP by running the command below.

Terminal · mac

$ # Find your local IP address:

$ # Windows:

$ ipconfig

$ # Mac / Linux:

$ ip route get 1 | awk '{print $7}' || ifconfig | grep 'inet '

What you should see

You will see a line containing your local IP address, something like 192.168.1.50. Enter that into the Jellyfin app as your server address.

This might happen

App cannot connect to the server from another device

Make sure both devices are on the same Wi-Fi network. Also check that your computer's firewall allows inbound connections on port 8096.

// Status

cooked. baked. worked.

A fully working personal media server running on your computer, accessible in any browser at http://localhost:8096 and via free Jellyfin apps on your TV, phone, or tablet — with no subscription or account required.

// the honest bit

The honest part

This guide covers local network streaming only. Accessing Jellyfin from outside your home requires port forwarding or a VPN — that is a separate networking task not covered here. Hardware video transcoding (for smoother playback on slow devices) needs extra GPU configuration. Very large libraries (10,000+ items) can take hours to scan on first run. Jellyfin is excellent free software but it is community-maintained, so occasional rough edges exist.