Hound vs Jellyfin

Editor take

Choose Hound for titles you stream instead of store and for IPTV beside your library. Choose Jellyfin for transcoding a file a device cannot play and for apps on more screens.

Editor

Where they differ

Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.

Hound

Where Hound is stronger

  • Stream without storingPlays a title straight from a Stremio addon over torrent, Usenet or Debrid, so nothing is saved to the library; Jellyfin plays files already on your drives.1
  • IPTV beside the libraryAdds Xtream providers and M3U8 playlists; Jellyfin's built-in M3U tuner takes a playlist, with guide data mapped separately.2
  • Save a stream to the libraryA download queue writes the file into the library, where it behaves like a local file.3

Jellyfin

Where Jellyfin is stronger

  • Transcodes for any playerConverts a file a device cannot play, on the CPU or a GPU; Hound has no transcoding yet.4
  • Apps for TVs, phones and consolesRoku, Fire TV, Xbox, LG, Samsung and Apple TV apps from their stores, plus Android and iOS; Hound Android is in closed testing and iOS comes through TestFlight.5

Hound vs Jellyfin: specs side by side

Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.

Spec
PriceFreeFree
LicenceAGPL-3.0GPL-2.0
Media typesMovies, TVMovies, TV, Music
Transcoding–Hardware (NVENC, QSV, VAAPI)
Watch statePer-user accountsPer-user accounts
Watch partyNoSynced playback (no chat)
Remote access–Self-managed (reverse proxy or VPN)
Live TV–Tuner and guide
Web UIYesYes
iOSYesYes
Apple TV–Yes
AndroidYesYes
Android TVYesYes
Roku–Yes
webOS–Yes
Tizen–Yes
Xbox–Yes
WindowsYesYes
macOSYesYes
Linux–Yes
DockerYesYes
Linux package–Yes
Windows–Yes
macOS–Yes
Tech stackGo.NET
Docker Containers2 (app, Postgres)1 (app only)
DatabasePostgresSQLite
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Hound site and Jellyfin docs.

Updated