Your server.
A few steps away.

1. Choose your device

Check release availability and the minimum OS in the platform guide. Invited beta testers install through TestFlight. Use the release page for the verified public App Store link when available.

2. Enter the Jellyfin server address

Use the exact address supplied by the server operator, including any port or path. For example, https://media.example.com is a placeholder, not a Zorofin-hosted server. Prefer HTTPS for a remote connection; do not disable certificate checks to work around a connection error.

On Apple TV, the address helper lets you choose HTTP or HTTPS so you can enter the host with less remote typing. Make sure the selected protocol matches the address provided by the operator.

3. Sign in or use Quick Connect

Sign in with the account you already use on that Jellyfin server. If the server enables Quick Connect, choose it in Zorofin, then approve the displayed code from a trusted device already signed in to that same server. Never send a password or Quick Connect code to app support.

4. Open your library and check a title

Browse a movie or show that your account can access. Confirm playback, audio and subtitles with your own media. Your server decides whether a file can direct-play, needs remuxing or requires transcoding; device capabilities and network conditions also matter.

Why are Requests or Live TV missing?

Live TV requires a server with Live TV configured and account access. Requests, server support and related notifications require compatible optional services. Their absence does not mean a normal Jellyfin server needs a Zorofin plugin for library playback.

What if Quick Connect or sign-in is rejected?

Check that the address is reachable and points to the same server as the approving device. Ask the operator whether Quick Connect is enabled and whether your account has reached its session limit. Avoid repeatedly creating new sessions while troubleshooting.

If you can sign in through Jellyfin’s web client but Zorofin fails, contact app support with the device model, OS, app version and a short description. Omit passwords, tokens, private media and sign-in codes.

What should server operators know?

The client uses standard Jellyfin authentication and library/playback APIs. Optional integrations should be presented separately and use the signed-in user’s permissions. Keep server software and TLS current, and test representative files before inviting others. Read how connections and optional features handle data.