How to Use Jellyfin: The Beginner's Guide (First Server, Libraries, First Stream on Any TV, and Remote Access)

CodexFuse Team · 2026-10-29T13:01:13.753Z · 14 min read

Learning how to use Jellyfin takes about an hour, and by the end of that hour you have your own private streaming service: your movies, TV shows, and music organized into a Netflix-style library that plays on your TV, phone, and browser. Jellyfin is a free, open-source media server, so nothing costs anything, there is no subscription, and no vendor account is required to run it (MakeUseOf, June 2026).

This guide walks the whole path in order: pick the install method that fits your hardware, run the setup wizard, name your folders so the scanner actually matches your files, watch on a TV or phone, turn on hardware transcoding, and open it up for watching away from home. The most popular install route for a dedicated server is Docker — if you have never touched containers, our Docker beginner guide gets you to the first working container in one sitting.

What Is Jellyfin?

Jellyfin is a free, open-source media server you install on your own computer or server; it scans the media folders you point it at, downloads covers, descriptions, and metadata for each title, and streams everything to apps and browsers on your devices. It plays movies, TV shows, music, photos, and even live TV with DVR, with no subscription, no cloud, and no telemetry you cannot control. The first release shipped on December 8, 2018 (MakeUseOf, June 2026), and the project has grown steadily since as the no-paywall alternative to Plex and Emby.

The core idea is simple: instead of uploading your collection to someone else's cloud or re-buying it through a subscription, you keep the files and Jellyfin gives them a polished streaming interface.

What Do You Need Before You Install Jellyfin?

You need a computer you can leave on (or at least on when you watch), enough storage for your media, and your files organized into separate top-level folders for movies, TV shows, music, and home videos. That is the whole list. An old desktop, a mini PC, a Mac mini, a NAS, or even a VPS all work.

Hardware choice matters most when you plan to transcode — convert video on the fly for a device that cannot play the original. A low-power Intel machine with Quick Sync (like an N100 mini PC) is the sweet spot: per MakeUseOf's testing notes, Intel Quick Sync on an N100 can handle three or four simultaneous 4K HEVC streams while sipping power. If you add a real NVIDIA card with NVENC, that rises to six, twelve, or more streams for a big household.

Steer clear of AMD graphics for this job if you can, because their encoders and driver support trail Intel and NVIDIA for media work (MakeUseOf, June 2026). And wire the server over Ethernet whenever possible — Wi-Fi works for playback devices, but the server itself is happier on a cable.

Which Install Method Should You Pick?

Pick the method that matches your machine; the server software is identical in all of them. Docker is the cleanest route on Linux and servers, native apps are simplest on Mac and Windows, and NAS boxes have their own package route.

Running Jellyfin on a VPS or a remote server works well too — our what is VPS hosting guide explains when a rented server beats hardware at home. Just remember the storage warning: a movie collection will burst a small system SSD, so plan for extra disk from the start.

How Do You Install Jellyfin on Linux With Docker?

Install Docker and Docker Compose first, then make a project folder, point Jellyfin at your media, and start it with one command. MakeUseOf's June 2026 walkthrough and ServerKüche's fresh Docker guide agree on the shape of it.

1. Create a project folder and the folders Jellyfin will use for its config and cache, e.g. ~/jellyfin/{config,cache}. Create them before the first start so they belong to your user, not root.
2. Write a docker-compose.yml using the official image: map ./config to /config, ./cache to /cache, and mount your media folder read-only (e.g. /mnt/media:/media:ro) so Jellyfin can never alter your originals.
3. Set the container user to your own UID/GID (usually 1000:1000) so Jellyfin can read the files, and pass through your GPU device if you want hardware transcoding.
4. Run docker compose up -d. On the first start, watch the log until you see the "Startup complete" message.
5. Open http://SERVER-IP:8096 in a browser. Jellyfin listens on port 8096 by default.

One trap that catches Docker beginners: inside the setup wizard you will type the container path (/media/filme), not the host path (/mnt/media/filme). The directory picker in the wizard only shows container paths, so use those.

How Do You Install Jellyfin on a Mac?

Download the current macOS DMG from the Jellyfin downloads page (pick the Apple silicon or Intel build), drag Jellyfin into Applications, and launch it. Then click the Jellyfin icon in the menu bar and select Launch; if the setup page does not open by itself, go to http://localhost:8096.

The native macOS app is usually simpler than Docker on a Mac, and it gives the server a direct path to macOS media frameworks (Zeera Wireless, Mac mini guide 2026). Store the server database and transcode cache on the internal SSD for fast artwork loading, keep the media library on a large external drive or NAS, and give the Mac mini a reserved local IP in your router.

What Happens in the Jellyfin Setup Wizard?

The first time you open the web interface, a wizard walks you through six screens, and it takes about five minutes. Here is exactly what each screen asks, based on ServerKüche's step-by-step walkthrough of the current wizard (Jellyfin 12.2):

1. Language. Pick your preferred display language.
2. Server name. This is the name clients will show in their app lists. The field is pre-filled with the container hostname (a random hex string like 89a5c9ac3424), so give it a speaking name like "Living Room" instead.
3. Administrator account. Create your admin username and a long, unique password. ServerKüche flags this explicitly: if the login page is reachable from the internet, this password is the lock on your front door.
4. Add media libraries. Click "Add Media Library," choose the type (Movies, TV Shows, Music, Photos, and so on), and point it at the matching folder. Repeat for each media type.
5. Metadata language and country. The defaults (TheMovieDB for movies, TheTVDB for TV) work well for most people.
6. Remote access. Leave "Allow remote connections to this server" on unless you have a specific reason to lock the server to your home network, then click Finish.

After you finish, Jellyfin scans your folders and downloads covers and descriptions. A large collection takes a while on the first scan — you can watch the progress under Dashboard, then Scheduled Tasks.

Why Can't Jellyfin Find Your Movies? Fix the Folder Names

Jellyfin relies on consistent file naming to match your files against online metadata databases, and poor naming is the number one cause of wrong or missing artwork. The fix is mechanical: separate top-level folders per media type, one folder per movie, and episode files tagged with season and episode numbers.

The year in the folder name is what lets the scanner tell remakes apart, and the S01E01 pattern is what makes episode matching reliable. Keep subtitles, artwork, and extras inside the same movie or show folder, and never put movies and TV episodes inside the same library folder. Vague filenames like episode1-final.mkv are the fastest route to an empty library page.

How Do You Watch on a TV, Phone, or Second Computer?

Install an official Jellyfin client for your device — apps exist for Android, iOS and iPadOS, Android TV, Fire TV, and plain web browsers — then sign in with the server address and your user account. Jellyfin's official apps are built to maximize direct play, which takes the load off your server.

Do not share your administrator login for everyday watching. Create a separate non-admin user for normal playback (Dashboard, then Users), and restrict which libraries that user can see when it matters — kids' accounts are the classic case.

What Is the Difference Between Direct Play, Direct Stream, and Transcoding?

These three words describe how hard your server works for each playback session, and understanding them explains most Jellyfin performance mysteries. Aim for Direct Play everywhere; treat the other two as fallbacks.

Transcoding usually triggers for a concrete reason: the TV app does not support the video codec or bit depth, the audio track is unsupported, the subtitle format forces burn-in, the remote-quality limit sits below the original bitrate, or you are playing in a browser, which supports fewer formats than a native TV or mobile app. Check the playback dashboard first — it normally tells you whether a session is Direct Play, Direct Stream, or Transcode, and often why.

How Do You Turn On Hardware Transcoding in Jellyfin?

Open the Dashboard as admin, go to Playback, then Transcoding, and pick the hardware-acceleration method that matches your machine: Intel Quick Sync (QSV) on Intel chips, NVENC on NVIDIA cards, or VideoToolbox on a Mac. Hardware transcoding is not locked behind any subscription in Jellyfin — that is one of the sharpest differences from Plex, where it is a Plex Pass feature.

1. In Dashboard, Playback, Transcoding, select your acceleration method from the dropdown.
2. Check the boxes for hardware decoding on the codecs you actually use (H.264, HEVC, AV1), so the GPU takes over instead of your CPU doing the work.
3. Save, then test: play a video in the web client, force a lower bitrate or resolution to trigger a transcode, and open the dashboard to confirm the session says Transcoding.

On a Mac mini, the confirmation step is Activity Monitor: play, force the transcode, and search for ffmpeg. If it is not consuming several hundred percent of CPU, VideoToolbox is handling the media-engine work (Zeera Wireless, 2026). One caution from Jellyfin's own Apple guidance: use the FFmpeg build that ships with the server — do not swap in an arbitrary FFmpeg download.

A practical tip that saves transcoding for free: stick with external text subtitles (SRT) rather than image-based ones like PGS. Image subtitles often force the server to burn them into the video, which keeps even a good GPU busy; text subtitles can usually be passed through or converted cheaply.

How Do You Watch Jellyfin Away From Home?

For remote access, give the server a reserved local IP, then either forward port 8096 on your router to it or — better — put Jellyfin behind a reverse proxy with HTTPS, like the Traefik setup ServerKüche walks through. The reverse-proxy route keeps you from exposing the raw port to the whole internet.

Either way, the setup-wizard password warning applies double here: a long, unique admin password, plus a separate playback user for anyone you share with. And remember what you give up for free remote access on Jellyfin versus Plex: remote access and some client polish need more manual work on Jellyfin, while Plex's slicker remote setup now sits behind its subscription tiers (Zeera Wireless, 2026; MakeUseOf, June 2026).

If the server will live on a rented machine instead of hardware at home, read our what is VPS hosting guide first — it covers the storage and bandwidth questions that decide whether a VPS is the right home for a media server.

Jellyfin vs Plex vs Emby: Which Should You Pick?

Pick Jellyfin if you want the server fully under your control with nothing behind a paywall; pick Plex if your household wants the smoothest client experience and you accept the subscription model; Emby sits between them. The table below follows the comparison Zeera Wireless published in their 2026 Mac mini guide.

One honest trade: Jellyfin gives up some conveniences — Plex's slicker remote streaming and the metadata polish it has refined for years. If your family expects a Netflix-like experience with zero explanation, Plex is the easier sell. If you would rather own your library outright and stop worrying about a company moving features behind a paywall later, Jellyfin is the strongest choice.

Fans of self-hosting the whole stack usually end up running more than a media server — if that is you, our Ollama beginner guide walks through self-hosting an AI model on your own hardware next.

Sources

• ServerKüche, "Self-hosting Jellyfin: your own media server" (fetched 2026-10-29; covers Jellyfin 12.2) — the Docker Compose shape (official jellyfin/jellyfin image, port 8096, config/cache/media volumes, UID 1000:1000, read-only media mount), the six setup-wizard screens, the container-path-vs-host-path trap, the fstab nofail warning for block storage, and the reverse-proxy remote-access route. https://serverkueche.de/en/tutorials/jellyfin-media-server/
• MakeUseOf, "Self-hosted media servers aren't as hard as Plex makes them seem" (published June 30, 2026; fetched 2026-10-29) — Jellyfin as free and open source with no subscription, Docker as the cleanest install, port 8096, the Intel N100 Quick Sync 3–4 4K HEVC stream claim and NVENC 6–12+ stream claim, the Dashboard → Playback → Transcoding steps, local authentication, official apps for Android TV and Apple TV maximizing direct play, and the initial release date December 8, 2018. https://www.makeuseof.com/self-hosted-media-servers-arent-as-hard-as-plex-makes-them-seem/
• Zeera Wireless, "Mac mini Plex, Jellyfin & Emby Setup Guide (2026)" (fetched 2026-10-29) — the native macOS install steps (DMG, Applications, menu-bar Launch, localhost:8096), VideoToolbox enablement and verification via Activity Monitor, the Direct Play / Direct Stream / Transcoding definitions and trigger list, the Plex vs Jellyfin vs Emby comparison table, the folder-naming rules, and the storage layout guidance. https://zeerawireless.com/blogs/news/mac-mini-plex-jellyfin-emby-media-server-setup

Frequently Asked Questions

Is Jellyfin really free?

Yes. Jellyfin is free and open source — there is no paid tier, no feature locked behind a subscription, and hardware transcoding is included at no cost. The trade is a more hands-on setup and remote access that you configure yourself instead of having it handled for you.

What do I need to run a Jellyfin server?

A computer you can leave on, storage for your media, and Docker or a native installer — that is the list. An old desktop, a mini PC, a Mac mini, a NAS, or a VPS all work. Hardware transcoding benefits from an Intel chip with Quick Sync, an NVIDIA card with NVENC, or Apple silicon with VideoToolbox.

Why is Jellyfin not finding my movies?

Almost always the folder names. Jellyfin matches files against metadata databases, so use separate top-level folders per media type, one folder per movie as Movie Name (Year), and TV episodes tagged Show Name - S01E01 - Title inside Season folders. After renaming, refresh the library and the artwork usually appears.

Can I watch Jellyfin on my TV and phone?

Yes. Official clients exist for Android, iOS and iPadOS, Android TV, Fire TV, and web browsers, and they sign in with your server address and user account. The TV and mobile apps are built to maximize direct play, which keeps the server load low.

Do I need a Plex Pass-style subscription for hardware transcoding?

No — that is one of Jellyfin's sharpest differences. Hardware transcoding is built in and free: pick your acceleration method under Dashboard, Playback, Transcoding (Quick Sync, NVENC, or VideoToolbox), check the codecs you use, and verify with a forced transcode. On Plex and Emby, the same feature requires Plex Pass or Emby Premiere.