Fladder

Honest look at a cross-platform Jellyfin frontend for people tired of the official client’s limitations.

TL;DR

• What it is: A cross-platform Jellyfin client built with Flutter — not a media server itself, but a polished frontend that connects to your existing Jellyfin instance [2][3].
• Who it’s for: Jellyfin users who want a modern, unified interface across Android, iOS, Windows, macOS, Linux, and Web without running separate apps for each platform [2][3].
• Cost savings: Fladder is free (GPL-3.0). Pair it with Jellyfin (also free) on a $6–15/mo VPS and you’re done paying $50+ monthly for Netflix, Disney+, and Plex Pass [4].
• Key strength: Genuinely modern UI, advanced timeline with chapter markers and intro/credit skipping built in, Jellyseerr integration, and concurrent downloads — features the official Jellyfin web client doesn’t offer [3].
• Key weakness: You still need a working Jellyfin server. Fladder solves the client problem, not the server problem. Collection artwork rendering has a known aspect-ratio bug [3]. At 1,925 GitHub stars, it’s an active but young project.

---

What is Fladder

Fladder is a Jellyfin frontend — full stop. It doesn’t store your media, doesn’t transcode anything on its own, and doesn’t replace Jellyfin. What it does is replace the interface you use to browse and watch your Jellyfin library.

The project was started by “partydonut” (DonutWare on GitHub) with a clear stated goal: “My aim was to make a clean alternative to the current ones available but also to unify it across different platforms” [2]. It’s written in Flutter, which means a single codebase compiles to Android, iOS, Windows, macOS, Linux, and the Web. That’s the whole pitch — one app, every screen you own.

As of this review it sits at 1,925 GitHub stars. The GPL-3.0 license means you can self-host the Docker web version, fork it, or modify it freely, but derivative work has to stay GPL.

If you’re not familiar with Jellyfin: it’s a free, open-source media server you run on your own hardware or a VPS. You point it at your media library, and it handles transcoding, metadata, and library management. Fladder is how you watch what’s in that library. No Jellyfin server, no Fladder.

---

Why people choose it

The short version from the reviews: the official Jellyfin web UI is functional but dated, and the third-party client landscape is fragmented. Finamp handles music well, SwiftFin is iOS-only, Jellyfin Media Player is desktop-only. Fladder is the attempt at something that covers everything without looking like it was designed in 2015.

The HowToGeek endorsement matters here. A January 2026 roundup of the best third-party Jellyfin clients [3] listed Fladder as the go-to for desktop movie watching: “When I want to watch movies on my PC, my go-to Jellyfin client has become Fladder. It’s an app written in Flutter that looks and feels modern.” That’s a meaningful signal — HowToGeek isn’t in the business of recommending half-finished projects.

The specific features called out in that review are the timeline and skipping behavior. Fladder shows chapter breaks, intro markers, and credit markers on the scrubber in a way that’s intuitive — you can see at a glance where the intro ends without blind-guessing. If you have trickplay enabled on your Jellyfin server it shows trickplay thumbnails; if not, it defaults to chapter thumbnails instead of showing nothing. That kind of graceful degradation is not common in this category [3].

The Instagram community has picked up on it too. One creator called it “The Cleanest Jellyfin Client” [5], which matches the HowToGeek description. The r/selfhosted thread from the original announcement [2] generated interest primarily because the promise — clean UI, cross-platform, unified — is something people have wanted for a while.

Compared to the competition:

• vs. official Jellyfin web: Fladder has intro skipping, concurrent downloads, trickplay, and a more modern layout. The official client is good enough but ships with every Jellyfin install — Fladder is the upgrade you install on top.
• vs. Infuse: Infuse (iOS/tvOS) has better Apple TV support and media scanning, but it costs money ($9.99/mo or $99.99 lifetime) and only runs on Apple devices. Fladder is free and runs everywhere.
• vs. Streamyfin: Mentioned in comments alongside Fladder [5] — Streamyfin is iOS-focused. If you’re cross-platform, Fladder is the more complete choice.
• vs. Finamp: Finamp is music-only [3]. Not the same category.

---

Features

Everything below is from the GitHub README and first-hand review descriptions:

Playback:

• Direct play, transcoded play, and offline/local sync [2]
• Media segments skipping — intro, credits, recaps, previews [README]
• Trickplay support on the timeline scrubber (falls back to chapter thumbnails if trickplay isn’t configured server-side) [3][README]
• Download items with progress sync across devices [README]
• Next-up overview when watching a queue [README]

Library management:

• Refresh content and edit metadata from the client [2]
• Favourites, resume, and library search [README]
• Simple comic book format support (.cbz, .cbr) [README]

User and server management:

• Multiple profiles — add multiple users or switch between different Jellyfin servers [2][README]
• Jellyseerr/Overseerr integration for requesting new content [3][README]
• Keyboard shortcuts on desktop [README]

Platform availability:

• Android (including Android TV) [README]
• iOS [README]
• Web (browser) [README]
• Docker (for self-hosting the web version) [README]
• Windows [README]
• macOS [README]
• Linux [README]

UI:

• Adaptive layout that adjusts for mobile, tablet, and desktop [README]
• Dark and light mode with multiple color styles [README]

What it does not do: server-side transcoding settings, user management, or library indexing — those remain in the Jellyfin admin panel. Fladder is a consumption client, not an administration tool.

---

Pricing: SaaS vs self-hosted math

Fladder costs nothing. GPL-3.0, zero license fees, free to download from GitHub or the Play Store. The cost question is really about the Jellyfin stack underneath it.

The streaming bill it replaces:

• Netflix Standard with ads: ~$7/mo; Standard: ~$15/mo; Premium: ~$23/mo
• Disney+: ~$8–14/mo
• Plex Pass (for hardware transcoding and offline sync): $4.99/mo or $119.99 lifetime
• A “just the essentials” streaming bundle easily runs $40–60/mo

The self-hosted alternative:

• Jellyfin: $0 (FOSS, no license)
• Fladder: $0 (GPL-3.0)
• Server to run Jellyfin: if you already have a NAS or spare PC at home, $0 additional. On a VPS, $6–15/mo on Hetzner or Contabo depending on storage and transcoding load
• Storage: existing drives or object storage — highly variable

The realistic math: if you’re buying a $10/mo VPS and already have media, your total cost is $10/mo with no per-user fees, no per-stream limits, and no content licensing expiry. Versus $50+/mo for the streaming bundle you’re replacing. That’s roughly $480/year saved — and the savings compound as streaming services raise prices [4].

The caveat the Instagram content doesn’t mention: acquiring the media library in the first place has its own complexity and legality depending on jurisdiction. Fladder and Jellyfin are tools; what you put in them is your responsibility.

---

Deployment reality check

Fladder itself has almost no deployment overhead. The mobile versions are on the Play Store (Android). Desktop builds are on the GitHub releases page. The web version can be self-hosted via Docker. There’s no database to configure, no secrets to manage — it’s a client app that talks to Jellyfin over the standard Jellyfin API.

The real deployment work is Jellyfin, which you need running before Fladder is useful. That’s outside Fladder’s scope but worth being clear about:

• A basic Jellyfin install via Docker Compose on a Linux VPS takes 30–60 minutes for someone with Docker experience
• Adding a reverse proxy (Caddy or nginx) for HTTPS is another 15–30 minutes
• Hardware transcoding on a VPS requires a server with an Intel or AMD iGPU — not all VPS providers support passthrough
• Configuring trickplay (thumbnail scrubbing) requires server-side processing and additional disk space

Fladder-specific setup: close to zero. Download the app, enter your Jellyfin server URL, log in. That’s it. The HowToGeek reviewer didn’t mention any install friction [3], and the r/selfhosted thread from the project announcement got straight into features without setup complaints [2].

Known issues:

• Collection artwork is cropped to a square even when the source image is portrait/poster ratio — browsing collection libraries looks off [3]. The HowToGeek reviewer flagged this explicitly as their only complaint.
• The project is maintained by a small team (DonutWare). Feature velocity is good based on GitHub history, but bug fixes depend on a small contributor pool.
• iOS availability exists but App Store distribution for niche open-source clients can lag behind Android.

---

Pros and Cons

Pros

• Actually cross-platform. Android, iOS, Windows, macOS, Linux, and Web from one Flutter codebase. You don’t need a different app per device [2][3][README].
• Modern UI. Multiple reviewers cite it as the cleanest Jellyfin client available [3][5]. The default Jellyfin web interface is functional but not pleasant.
• Intro and credit skipping that works. Timeline shows chapter breaks, intro markers, and credit markers. Graceful fallback when trickplay isn’t configured [3].
• Jellyseerr integration. Request new content from inside the client without opening a separate app [3][README].
• Offline downloads with progress sync. Download episodes before a flight and your watch position stays in sync [README].
• GPL-3.0 license. Open source, auditable, forkable. The app won’t disappear behind a paywall.
• Free. No subscription, no license fee, no “Pro” tier [README].
• Comic book support. Niche, but .cbz/.cbr reading from your Jellyfin library is there if you need it [README].

Cons

• Requires Jellyfin. This is not a self-contained media solution. Non-technical founders who don’t have Jellyfin running get nothing from Fladder alone. The server setup is the hard part.
• Collection artwork bug. Poster-ratio images cropped to square in collection view. Cosmetic but visible [3].
• Young project. 1,925 stars puts it well below the major players. Smaller community means slower bug discovery and resolution. No dedicated support channel beyond GitHub issues.
• No server administration. You can’t manage users, configure transcoding, or set up libraries from inside Fladder. Everything administrative stays in Jellyfin’s own web UI.
• Flutter has trade-offs. Flutter apps can feel slightly “off” compared to native platform conventions, especially on iOS/macOS. No review explicitly complained about this for Fladder, but it’s worth knowing the underlying framework.
• Limited review coverage. The third-party review base is thin — one HowToGeek article [3], one Reddit announcement thread [2], and some short-form social coverage [4][5]. There aren’t extensive long-term user reports to synthesize.

---

Who should use this / who shouldn’t

Use Fladder if:

• You already run Jellyfin and you’re frustrated with the official web interface.
• You want one app that works on your phone, tablet, laptop, and TV without maintaining separate clients.
• Intro skipping and clean timeline scrubbing matter to your watching experience.
• You want Jellyseerr integration without opening a separate browser tab.

Skip it if:

• You don’t have a Jellyfin server — get that running first, then come back.
• You’re on Apple TV — Fladder doesn’t support tvOS as of this review. Look at Infuse or the Jellyfin iOS app with AirPlay.
• You primarily use Jellyfin for music — Finamp is more purpose-built for that use case [3].
• You want the most stable, most widely-supported client — the official Jellyfin clients have more users, more issue reporters, and faster critical bug fixes.

Skip it (stay with official clients) if:

• Your setup is working and you’re not experiencing pain. Fladder solves UI and feature gaps — if those gaps don’t bother you, there’s nothing to fix.

---

Alternatives worth considering

Official Jellyfin clients — The built-in web interface works. Jellyfin also has official Android and iOS apps. They’re less polished than Fladder but more battle-tested. First choice if you don’t have specific complaints about the stock client.

Finamp — Purpose-built for Jellyfin music streaming. If your primary use is listening to your music library, Finamp is ahead of Fladder for that use case [3]. Not the right tool for video.

Infuse (iOS/tvOS) — The premium option for Apple devices. Excellent Apple TV support, hardware-accelerated playback, clean UI. Costs $9.99/mo or $119.99 lifetime. If you’re Apple-only and willing to pay, Infuse is mature and well-reviewed.

Streamyfin — iOS-focused Jellyfin client mentioned alongside Fladder in the community [5]. Less cross-platform than Fladder; comparison data is limited.

Jellyfin Media Player — Desktop-only (Windows/macOS/Linux), built on libmpv. Better video codec support and lower-level playback control than Fladder for desktop-only users. Less polished UI, no mobile support.

Swiftfin — Native iOS/tvOS client for Jellyfin. Good Apple TV integration. Platform-specific, so it’s the alternative when you need tvOS support that Fladder doesn’t currently cover.

---

Bottom line

Fladder is a focused tool with a clear job: make Jellyfin look and feel modern across every device you own. It does that job well enough that a major tech publication picked it as their desktop Jellyfin recommendation in early 2026 [3]. The intro skipping, timeline design, and cross-platform Flutter implementation are genuinely better than what the stock Jellyfin clients offer. The trade-offs are real — it’s a young project, the collection artwork bug is visible, and it does nothing for the harder problem of setting up and maintaining a Jellyfin server.

For existing Jellyfin users who are annoyed by the official interface: install Fladder, point it at your server, and see if it fits in twenty minutes. The setup cost is essentially zero. For non-technical founders who don’t have Jellyfin yet: the server side is the work; Fladder comes after.

If the server setup is the blocker, that’s exactly what upready.dev handles for clients — one-time deployment, you own the infrastructure.

---

Sources

1. Ethan Sholly, Self-Host Weekly — “Self-Host Weekly (9 January 2026)”. selfh.st. https://selfh.st/weekly/2026-01-09/
2. partydonut (DonutWare), Reddit r/selfhosted — “Fladder - A Simple Jellyfin Frontend”. reddit.com. https://www.reddit.com/r/selfhosted/comments/1g24hcj/fladder_a_simple_jellyfin_frontend/
3. Jordan Gloor, How-To Geek — “Make Jellyfin look like Spotify and Plex: 5 clients you need to install” (January 10, 2026). howtogeek.com. https://www.howtogeek.com/these-fan-made-jellyfin-clients-totally-redefined-my-home-media-server/
4. Various creators, Instagram — “Fladder Jellyfin” (community content). instagram.com. https://www.instagram.com/popular/fladder-jellyfin/
5. carter.keel.me, Instagram — “The Cleanest Jellyfin Client | Fladder” (March 12, 2026). instagram.com. https://www.instagram.com/reel/DVykZwdAqbO/

Primary sources:

• GitHub repository and README: https://github.com/donutware/fladder (1,925 stars, GPL-3.0 license)
• Official website: https://donutware.github.io/Fladder