- Category
- Entertainment
- Rank
- No. 262Apps board
Previous survey · No. 239 ·
- Type
- APP
- GitHub
- 2 stars
- Date
About
Jellex is a browser client for an existing Jellyfin media server, aiming for a Plex Web-style interface. Its single-page client talks directly to the server API without a separate application backend. Playback capabilities depend on the browser and server; the client stores a server address and access token in browser storage.
At a glance
Jellex is an alternative web interface for Jellyfin, the server that stores and streams your media. Its stated aim is a Plex Web-style experience using your existing Jellyfin library. It is worth a cautious look if that layout appeals to you; it does not supply films, host your library or remove the need to operate a media server.
Good fit
Existing Jellyfin users interested in a different browser client without migrating their library. The source includes movie, episode and music queues, subtitle selection and browser-specific playback choices. Those are implementation capabilities rather than playback results verified here. The available connection screen confirms that the first step is finding your own server.
Consider something else when
You want a streaming subscription or a player that works without a server account. The hosted HTTPS client also filters out plain-HTTP server addresses, so a LAN server reachable only over HTTP is not a direct fit for that hosted version. Choose a client and deployment arrangement that match how your server is exposed.
Start here
On a client host you trust, enter your Jellyfin server’s HTTPS address and choose Connect. The source then offers username/password sign-in or Quick Connect when the server enables it. A useful first check is loading your libraries and playing one familiar file with your usual audio and subtitle tracks. The public demo option is visible, but neither sign-in nor playback was exercised in this inspection.
Cost and requirements
No separate client price is stated in the README or connection screen. You still need a Jellyfin server, storage and sufficient resources for any media conversion. The app can be served as a static website without its own backend. It saves the server address and access token in browser local storage; blocking storage prevents session persistence.
Limits to know
Playback depends on browser format support and the server’s ability to convert incompatible media. A selected bitrate cap requests conversion, which can add server work. Source-generated media URLs contain the access token, so treat them as credentials. Sign-out clears the saved session token. Only the connection interface and selected source were inspected; codec compatibility, subtitles, playback quality and library-scale behavior remain untested.
Still unclear
- What licence permits reuse or redistribution of the publicly visible Jellex source? Neither the checked manifest nor file inventory establishes one.
Sources checked 2026-11-05. Source-based assessment.
- github.com/iridium/jellex/blob/main/README.md
- github.com/iridium/jellex/blob/main/package.json
- github.com/iridium/jellex/blob/main/src/lib/session.svelte.ts
- github.com/iridium/jellex/blob/main/src/routes/login/%2Bpage.svelte
- github.com/iridium/jellex/blob/main/src/lib/playback.ts
- github.com/iridium/jellex/blob/main/src/lib/settings.svelte.ts
- github.com/iridium/jellex/blob/main/src/routes/%2Blayout.ts
- api.github.com/repos/iridium/jellex/git/trees/main
- jellyfin.org
- jellex.x86.cx/login
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.