Jellyfin for Kodi

Part of the Jellyfin Project

Our informal Kodi support target is current release±1, which currently translates to Nexus (old), Omega (current) and Piers (next).

Please note that next release is a moving target, has a relatively low priority, and is unlikely to receive active work before the release candidate stage.

A whole new way to manage and view your media library.

The Jellyfin for Kodi add-on combines the best of Kodi - ultra smooth navigation, beautiful UIs and playback of any file under the sun, and Jellyfin - the most powerful open source multi-client media metadata indexer and server. You can now retire your MySQL setup in favor of a more flexible setup.

Synchronize your media on your Jellyfin server to the native Kodi database, browsing your media at full speed, while retaining the ability to use other Kodi add-ons to enhance your experience. In addition, you can use any Kodi skin you'd like!

#Supported

The add-on supports a hybrid approach. You can decide which Jellyfin libraries to sync to the Kodi database. Other libraries and features are accessible dynamically, as a plugin listing.

• Library types available to sync:
  • Movies and sets
  • TV shows
  • Music videos
  • Music
• Other features supported:
  • Simple Live TV presentation
  • Home Videos & photos
  • Playlists
  • Theme media
• Direct play and transcode
• A 2-way watched and resume state between your server and Kodi. This is a near instant feature.
• Remote control your Kodi; send play commands from your Jellyfin web client or Jellyfin mobile apps.
• Extrafanart (rotating backgrounds) for skins that support it
• Offer to delete content after playback
• Backup your Jellyfin Kodi profile (Create and restore from backup )
• and more...

#Install Jellyfin for Kodi

Detailed installation instructions can be found in the Jellyfin Client Documentation.

#Known limitations

• Chapter images are missing unless native playback mode is used.
• Certain add-ons that depend on seeing where your content is located will not work unless native playback mode is selected.

#Contributing

#AI/LLM

Please see Jellyfin's official LLM policy.

Any PR, issue or comment that is primarily LLM generated will be rejected outright on principle.

Machine translation as a communication aid is allowed, but requires disclosure and that you also include the original language text.

LLM generated code has a high probability of getting rejected. Relatively low effort AI contributions put an unsustainable and unproportional extra burden on project maintainers, which during the review process need to understand the suggested changes, and evaluate whether they are good changes, whether there are better alternatives and so on.

LLM can be a decent tool to get up to speed and learn about the code-base, but is highly likely to generate subpar code.

Fine for debugging, research and proof of concept, but not currently suitable for production code.

#Dev environment

The project use the following tools:

• black auto-formats the Python code (mandatory)
• flake8 to highlight potential issues
• EditorConfig to ensure consistency in editor indentation and similar
• pytest for code regression testing
• pre-commit helps run the most important ones before commiting

Visual Studio Code is my current editor of choice, and as such the project is configured around this. A devcontainer config is available for consistency's sake and quick setup, but I often don't use it myself.

mypy is planned, but there is a lot of work needed to properly implemet type-checking.