Choose the integration model before installation
JellyCon browses; Jellyfin for Kodi syncs metadata into a local SQLite library. Choose according to the actual task and existing sources. For an original planning example, a Kodi library already maintained by another tool calls for a different integration decision from a fresh device intended only for one Jellyfin server.
Inventory the current Kodi library and preserve a backup before changing its database workflow. A device already using local movies or another library integration deserves particular care. A new server connection should not silently become the owner of a database that other tools depend on.
Follow the official repository trail
Use the official repository at https://kodi.jellyfin.org and its repository ZIP. Verify that provenance before installation. A similarly named archive attached to a public conversation is not the same download trail. Keep the selected package identity in the device notes so a later update can be assessed against the real installation.
Install the intended client from the Kodi Jellyfin repository’s video add-ons through the current documented route. Record Kodi and add-on versions. Keep any installation-source permission scoped to the owner’s deliberate action and preserve the working configuration.
Connect to the real server and viewer
Use the actual server discovery result or authorized endpoint, including the required scheme, port and subpath. Select the intended viewer and verify that account’s library access. An administrator account can hide a missing viewer permission during a test.
Open one known video through the chosen integration. For the browsing model, inspect the add-on’s actual server view. For the synchronized model, allow the documented metadata process to establish its selected libraries before interpreting the ordinary Kodi home screen. Keep those two presentations distinguishable.
Keep database requirements and update behavior explicit
The sync add-on requires local SQLite and recommends Kodi Sync Queue. Check the actual server and database arrangement before selecting that model. Preserve any unrelated working library integration. A new setup should have a clear owner for its data rather than allowing several tools to overwrite the same state without a plan.
Use one known added or changed item to observe the chosen update route. A startup that completes before every poster is visible does not by itself establish a failed sync. Preserve the item, client and timing rather than repeatedly copying database files between devices.
Verify playback and the ordinary user workflow
Test picture, speech and required subtitles on the known item, then return to the intended home or add-on route. If using a customized skin, verify its actual navigation separately; skin layouts do not make all integrations identical.
The expected outcome is an understood official integration with a checked library and media sample. This documentation guide does not claim a hands-on account test, universal skin compatibility or conflict-free coexistence for every database integration. Keep the chosen data model in support notes so later advice fits the installation.
Questions answered
What should I decide before installing an integration?
Inventory the current Kodi library and decide whether the task needs server browsing or a locally synchronized collection. Preserve a recoverable baseline.
How should I verify the intended server connection?
Keep the endpoint, viewer and one known item together. A familiar poster alone does not establish the correct account and playback result.
Does a skin shortcut change the underlying integration?
No. It changes navigation. Keep the actual browsing or synchronized model identified.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.