Jellyfin has lost three of the people who built it. Inside a single week in July 2026, the man who had led the project since its first day, a core team member of roughly eight years, and one of the co-founders all stepped away from their roles. None of it was announced on the project blog.
The short version for anyone with a server running: nothing is shutting down. But the names at the top have changed, and one official app is no longer official.
What the announcement actually said
In a thread titled “Project Leadership Changes” on the official Jellyfin forum, Joshua Boniface announced he was stepping down as Project Leader, effective 19 July. He had held the role since Jellyfin began in late 2018 as a fully open-source fork of Emby.
He was direct about why.
I simply could no longer provide the effort (mental or time-wise) that the role demanded, and thus I was not performing my duties to an acceptable degree, facing severe burnout, and risks to my mental health. It was time to step aside.
The same post covered Anthony Lavado, who had been on the core team for about eight years. Lavado had not been writing much code recently, but he ran app store submissions, public communications, releases, finances, and the administrative work that keeps a project this size upright. He cited personal changes, and said he would help with the handover for as long as it takes, “even if it takes a year.”
Boniface described the transition as amicable. He said he is still in contact with the team, sees minimal risk to Jellyfin’s immediate future, and expects the project to do fine without him.
Andrew Rabert leaves, and the desktop client goes with him
Two days earlier, on 17 July, Andrew Rabert announced his own departure in a GitHub issue on his own repository. Rabert co-founded Jellyfin and maintained Jellyfin Media Player, the official desktop client.
He gave two reasons: burnout, and a growing disagreement with how the project handles development. The specific flashpoint was his proposal to add a CLAUDE.md file, which met pushback under Jellyfin’s LLM policies. Those rules restrict LLM-assisted code contributions. Rabert called them “increasingly burdensome and restrictive.”
His client left with him. Jellyfin Media Player has been renamed Jellium Desktop, now hosted at andrewrabert/jellium-desktop and continued as an unofficial project. If you use the desktop app rather than the web interface, this is the change that touches you directly.
The part nobody has confirmed
This is where speculation starts, so it is worth separating what is known from what is being asked.
The leadership post went up on the forum rather than the blog, and it said nothing about Rabert’s exit two days before. Self-Host Weekly flagged both details and raised the question of whether the three departures were coordinated. That is a fair question to ask. It is not an answer, and no one involved has said they were connected.
Boniface has since published a follow-up on his personal site pushing back on the idea that the LLM dispute drove him out. His own account is longer and messier than any single disagreement.
Both men used the word burnout. Volunteer projects with millions of users tend to pile an enormous amount of unpaid work onto a handful of people, and Jellyfin never solved that. It is a boring explanation. It may also be the right one.
What changes for your server
Practically, very little.
- The Jellyfin server, the mobile and TV apps, and the repositories are all still maintained. There is no sign of abandonment anywhere.
- A large group of experienced contributors is still in place, and day-to-day development has continued through all of this.
- The desktop client is the one real change. The app formerly shipped as Jellyfin Media Player now continues separately as Jellium Desktop.
- No successor as Project Leader has been named publicly so far.
Governance handovers in open source are usually slower and duller than they look from outside, and Jellyfin has survived worse. It started as a fork by people walking away from Emby’s move to a closed licence, which is a decent reminder that this community rebuilds things when it has to.
The question worth watching is not whether Jellyfin survives the next month. It is who picks up the unglamorous release-and-paperwork job Lavado was doing, and whether anyone wants the leader role after seeing what it cost the last person to hold it.
Further coverage is available at Linuxiac.