

Don’t have to make an account, for starters. Gives you more detailed control of transcoding options, audio playback and whatnot.
The UI is worse, that much is true, but that’s not the end all be all of user experience.


Don’t have to make an account, for starters. Gives you more detailed control of transcoding options, audio playback and whatnot.
The UI is worse, that much is true, but that’s not the end all be all of user experience.


I don’t think transcoding is that difficult if you’ve already set up your own server. Like, that’s only a thing the admin would have to figure out and it’s a quick lookup.
I do agree with the client UI issue tho, and would like to add that the lack of a per-user watchlist is a pretty baffling decision given that it’s been widely requested for years and years and it would make it enormously more comfortable.


Huge disagree on the last part. Jellyfin has a bunch of Android, Roku, Google tv and PC clients. I struggle to think of a device me or my friends use that has a Plex client but not a Jellyfin one.


It depends on whether you want to use torrents or have a usenet subscription. You’d do well to look at TRaSH guides, save yourself a lot of headaches if you structure the container’s directory structures in the way the guides suggest and then you can just use Prowlarr to manage the actual download requests and send them to your torrent or usenet client.
I use Jellyfin and I suggest you do the same, but honestly you could use whatever you feel like, the *arr stack is going to put everything in the proper folder structure and naming convention so by and large your media server app should be pretty plug and play, just point it at the proper folder and get to scanning.
Roku app has a watchlist, but mostly I don’t bother to get around it or put it in a collection which is clunky as shit