By Nora Blake
How to Move From Plex to Jellyfin (2026): The Realistic Guide
Most Plex-to-Jellyfin guides are written for someone with a weekend, no household, and unlimited patience for a scraper that mislabels a film.
This one assumes the opposite: you have other people who watch things, and you'd like them not to notice a gap. The single most useful piece of advice is at the top for that reason.
The honest framing: Tuneline is a media player for content you provide. It is not a media server, not a Plex replacement, and not a Jellyfin client. It gets a brief, precise mention at the end.
Rule Zero: Run Both in Parallel
Do not turn Plex off. Not on day one, not on day seven.
Jellyfin reads the same files from the same disks. Both servers can point at the same library folders simultaneously, because scanning is read-only. So:
- Install Jellyfin alongside Plex.
- Point it at the same media folders.
- Let it scrape while Plex carries on serving everyone.
- Move people over one at a time as their devices are confirmed working.
- Turn Plex off only when nobody has used it for a fortnight.
Every migration horror story starts with someone decommissioning the working system on Friday night. There is no upside to it.
Step 1: Audit Your Folder Naming First
This is the step people skip, and it's the one that determines whether your migration feels smooth or maddening.
Plex has years of accumulated matches, manual fixes and metadata corrections stored in its database. None of that transfers. Jellyfin starts from your filenames alone. If your naming is sloppy, Plex was quietly compensating and Jellyfin will not.
Get this right before scanning:
Movies — one folder per film:
Movies/
The Thing (1982)/
The Thing (1982).mkv
Series — show, season, SxxExx:
Shows/
Severance (2022)/
Season 01/
Severance (2022) - S01E01.mkv
The year in the folder name resolves the majority of mismatches by itself. An hour of renaming here saves a great deal of manual correction later, and tools like FileBot or tinyMediaManager will do most of it.
Do the renaming while Plex is still running. Both servers read the same corrected names, so you validate the work immediately.
Step 2: Install Jellyfin
Docker is the usual route and the easiest to move later. Native packages exist for Windows, macOS, most Linux distributions, and NAS app stores (Synology, QNAP, Unraid).
Two things to get right at install time:
- Mount your media read-only if your setup allows. A scanner has no business writing to your library.
- Pass through your GPU if you want hardware transcoding —
/dev/drion Linux for Intel QuickSync, or the NVIDIA container runtime. This is free in Jellyfin, which is a large part of why people move.
Step 3: Scan and Correct
Point Jellyfin at your folders and let it scrape. On a large library this takes hours; leave it alone.
Then check the usual suspects:
- Films with generic or numeric titles. These mismatch most often.
- Anime, where numbering conventions vary between databases.
- Documentaries and concerts, which often aren't in the movie databases at all.
- Multi-part films, which need
- part1/- part2suffixes.
Fix by editing the item's identifier in Jellyfin (search by title or provider ID) rather than by re-scanning repeatedly.
Step 4: What Does and Doesn't Transfer
Be clear-eyed about this before you promise anything to anyone.
| Transfers? | Notes | |
|---|---|---|
| Media files | N/A | Never moved — both servers read the same disks |
| Library structure | Yes | Rebuilt from folders |
| Metadata and artwork | Re-scraped | Fresh, not copied. Usually fine with good naming |
| Watch history | Largely no | Third-party tools exist, imperfect. The real loss |
| Users and accounts | No | Recreate by hand |
| Playlists and collections | Mostly no | Rebuild manually |
| Subtitle files | Yes | Sidecar .srt/.ass next to the video are picked up |
Watch history is the one that hurts, especially on long-running series. Migration scripts exist and can match a good proportion of items, but expect gaps. If ten years of history genuinely matters to someone in your house, tell them before you start, not after.

Step 5: Check the Clients, One Device at a Time
This is where migrations actually fail. Jellyfin's server is excellent; the apps vary by platform, and the general reputation tells you nothing about your specific devices.
Before moving anyone across, personally verify on each device:
- Does the app exist for it at all?
- Does it direct-play your files, or transcode everything?
- Does it handle your subtitle formats?
- Does the remote work sensibly on TV devices?
Test on the actual hardware in your house. A device that transcodes everything will make Jellyfin feel broken when the real problem is a client that can't direct-play your codec.
Step 6: Remote Access
Plex handles remote access with its relay service. Jellyfin does not. You configure it yourself, and this is a genuine step up in responsibility.
Options, in increasing order of exposure:
- A private network overlay (Tailscale, WireGuard). Safest. Nothing is published to the internet. Best default for a household.
- A reverse proxy with HTTPS (Caddy, nginx) on your own domain. Works well, but you are now running an internet-facing service and are responsible for keeping it patched.
- Raw port forwarding. Don't.
If remote access matters and you don't want to become a part-time sysadmin, this is the strongest argument for staying on Plex or looking at Emby.
Step 7: Retire Plex, Slowly
Once every person and device has been on Jellyfin for two weeks without complaint, stop the Plex container. Don't delete its data for another month — a config you can restore is cheap insurance.
Where a Separate Player Fits
One narrow point, since the terms get conflated.
A server organises your library. A player is what you watch in. If your Jellyfin server is fine but the app on one particular device isn't, you don't have to fix that with a different server.
Jellyfin can expose a stream URL or an M3U for its live side, and any capable player can open one. That's the role Tuneline can fill — it is not a Jellyfin client, has no Jellyfin integration, and doesn't browse your library. It opens a URL your server hands out. (How the bridge works.)
Useful for one awkward device. Not a substitute for a Jellyfin client on devices that have a good one.
FAQ
Can I run Plex and Jellyfin at the same time?
Yes, on the same machine and the same media folders. Scanning is read-only. Running both in parallel is the recommended approach.
Will I lose my watch history moving to Jellyfin?
Mostly. Third-party tools can migrate part of it. Plan for gaps and warn your household first.
Does Jellyfin support hardware transcoding for free?
Yes. It's one of the main reasons people move, given the Plex Pass price. You must pass the GPU through to the container.
Is Jellyfin harder to set up than Plex?
The install is comparable. Remote access is meaningfully harder — Plex handles it for you, Jellyfin makes it your job.
Why does Jellyfin get my movie titles wrong?
It scrapes from filenames alone, with none of Plex's accumulated manual fixes. Rename to Title (Year)/Title (Year).ext before scanning.
Bottom Line
- Run both in parallel. Never decommission Plex on day one.
- Fix your naming first — Jellyfin has none of Plex's accumulated corrections.
- Watch history is the real loss. Say so before you start.
- Client apps decide success, not the server. Test your actual devices.
- Remote access is your job now. Use a private network overlay unless you want to run an internet-facing service.
- Budget a weekend, not an evening.
If one device's app is the weak link, download Tuneline and point it at a stream URL your server exposes. Free and ad-free.
— Nora Blake
Share this article
Get Tuneline free
A clean, no-account media player for macOS, Windows, Linux, Android, TV, and iOS. Bring your own playlist.
Download freeTuneline is a media player application. It does not provide, host, or distribute any content. You bring your own playlist, exactly as you would with VLC.