Choose a client from the project directory
The Jellyfin client directory distinguishes browser, desktop, television and mobile options and links their distribution routes. Use that directory to identify the intended application rather than trusting a similarly named store result. The phone and television interfaces can be separate clients even within the same system.
Write down the client name, platform and release alongside the server version. That four-part identity is useful when a tutorial’s controls do not match your screen. Keep server administration credentials separate from an ordinary household viewing account wherever the server operator provides that distinction.
Connect before diagnosing a title
Obtain the correct server address and account from its operator. Confirm that the client can reach the authorised library and display the expected items. Keep a private server URL out of public screenshots, especially if it contains a token or points to a home network.
A visible library and successful video playback are separate milestones. For a first check, select one ordinary permitted sample rather than importing or exposing an entire private collection. If the library loads but video fails, preserve that result: it narrows the question beyond basic sign-in.
Compare the media path
Jellyfin documents client-specific codec support and conversion when necessary. A file playing in a browser does not prove a native television client will use the same decoding or server-processing path. Identify the exact item, selected tracks and reported playback mode when asking the server operator for help.
If testing a second client, hold the item and account steady. A useful comparison records one title across two named clients, rather than changing the source and device together. This page describes documented roles and an editorial diagnostic method; it does not verify a specific Jellyfin server or IPTV Australia account.