A community project that swaps Jellyfin's standard web interface for a Star Trek–style LCARS look has been made public. The author, who says they spent months tinkering with it privately, published the work as a GitHub project called jellyfin-lcars, with a container image available from the project's package registry. The announcement appeared in the r/jellyfin thread.
What it actually is
This is not a plugin in the usual sense. The build process pulls the point release of the official Jellyfin Docker image, compiles the LCARS web UI, and replaces the /web/ directory inside that image. A small LCARS plugin is added on top for a bit of extra information. In other words, it is a direct replacement for the jellyfin-web part of the stack, distributed as a Jellyfin 12.4 container.
Because the change happens at the web layer, it applies to any client that simply frames the standard web UI. The author names the LG TV app, iOS and Jellyfin Desktop as the ones they know of.
Who is affected
Anyone running Jellyfin in Docker who wants a different front end, and anyone who runs clients that wrap the web UI — those users will see the new look without installing anything extra. Server-side APIs and playback behavior are not described as changing.
Why it matters
Jellyfin's web client is the piece most self-hosters stare at every day, and theming it has traditionally meant either a CSS tweak or a fork. Shipping a ready-made container lowers the barrier considerably: you pull an image instead of maintaining a build pipeline.
The caveats, plainly
The author is upfront that this is a beta. Known gaps include Live TV, Chromecast and SyncPlay, and the iOS mobile experience still needs styling work. They also disclose AI use in the project — for splitting it away from a private repository, gap analysis against the current jellyfin-web, boilerplate, build processes and GitHub workflows — while noting two decades of software engineering experience.
Commentary for self-hosters
Treat this as an experiment, not a drop-in upgrade. Run it on a test instance first, keep your existing container tag pinned and your compose file backed up, and expect the web UI to move independently of upstream Jellyfin releases. The missing Live TV and SyncPlay pieces are exactly the features households notice quickly, so decide whether you can live without them before rolling it out to the family. If you want a safer first step, browse our Jellyfin plugins for add-ons that extend the server without replacing its front end.