Aurora vs the Jellyfin web client

What Aurora actually replaces

Worth being precise, because “alternative Jellyfin frontend” is ambiguous in a way that matters.

Aurora does not replace Jellyfin. Your server keeps doing the scanning, the transcoding, the user accounts, the metadata and the plugins. Aurora replaces one layer: the interface you browse and play from. It talks to your server over the same public HTTP API that every Jellyfin app uses, with an API key you generate from the dashboard.

Nothing is installed into Jellyfin. No plugin, no theme, no patch. Stop the Aurora container and there is no trace of it on the server.

The design trade

The official web client has to be everything. It is where you add a library, create a user, configure a plugin, check transcoding, and also where you watch things. That breadth is the reason it looks the way it does — an interface that must expose a dashboard cannot also be a ten-foot experience.

Aurora makes the opposite choice. There is no dashboard, no library management, no user administration and no settings beyond its own. It does browsing and playback.

What that buys is an interface designed for one situation: a TV, a sofa, and someone deciding what to watch. Full-bleed backdrops, rails for continue-watching, favourites and recommendations, detail pages with cast and related titles, and transitions that hold up in a TV browser.

Whether that trade is worth a container depends entirely on whether the Jellyfin interface is the thing that bothers you. If your complaint is transcoding or metadata, Aurora changes nothing.

Aurora is not a theme

There are several good Jellyfin theme projects that restyle the official client with CSS. They are lighter than Aurora and they keep every feature, since they are the same application with a different skin.

The limitation is structural: a theme inherits the client’s information architecture. It can change how a row of posters looks; it cannot decide that the home page should lead with a full-bleed hero and a set of rails, because that markup does not exist to restyle. Themes also break when the upstream client changes its DOM.

Aurora is a separate application against the API, which is why it can differ in structure. It is the heavier answer — a whole extra container rather than a stylesheet — and for many people a theme is the right amount of change.

Multi-user and attribution

A detail that matters in a shared house.

Aurora can run in single-session mode, where it uses one Jellyfin account for playback, or with profiles. Set AURORA_MULTI_USER=true for per-profile browsing and AURORA_REQUIRE_LOGIN=true to make everyone sign in with their own Jellyfin account.

With required sign-in on, playback and watch progress are attributed to the right person — continue-watching is yours rather than the household’s. With it off, everything runs through the shared session user in JELLYFIN_USERNAME and the resume points mingle.

What you give up

Live TV and DVR. Not in Aurora. If you use Jellyfin for broadcast, you are in the official client for that.

SyncPlay. Watching in sync with someone remote stays in the official client.

Plugin interface elements. Intro Skipper is the common case. The plugin keeps working server-side, but its skip button lives in the official web client’s player and does not appear in Aurora.

Completeness. Aurora is marked In Progress, which is accurate. It covers browse-and-play well; it does not cover every corner of Jellyfin, and the official client has years of bug reports behind it that Aurora does not.

Running both

This is the recommended setup, not a hedge. Aurora on port 3000 for the TV, the official client where it already is for everything else:

services:
  aurora:
    image: getcoral/aurora:latest
    restart: unless-stopped
    depends_on: [jellyfin]
    ports:
      - "3000:3000"
    environment:
      AURORA_DATA_DIR: /data
      JELLYFIN_URL: http://jellyfin:8096
      JELLYFIN_API_KEY: ${JELLYFIN_API_KEY}
      JELLYFIN_USER_ID: ${JELLYFIN_USER_ID}
    volumes:
      - ./aurora-data:/data

Because Aurora holds no state that Jellyfin owns, trying it costs one container and removing it costs nothing. See the Aurora module page for full configuration, or the Docker Compose stack guide to set it up alongside Jellyfin from scratch.