Jitsi Desktop: a multi-protocol communicator that is no longer actively developed

What Jitsi Desktop is, and what it is not

Jitsi Desktop is a free open-source audio, video and chat communicator written in Java. The repository describes it as supporting SIP, XMPP/Jabber, IRC and "many other useful features". That protocol list is the point: one desktop application that can hold an XMPP account, a SIP account and an IRC connection at the same time, rather than three separate clients.

The README opens with a warning that matters more than any feature list. It asks readers not to confuse this project with Jitsi Meet, the online video conferencing solution with a free instance at https://meet.jit.si. The two share a name and an origin, not a codebase or a purpose. Jitsi Desktop is an installed client for individual accounts; Jitsi Meet is a browser-based meeting service. Most search traffic for "jitsi" is about the latter, and that traffic is not about this repository.

The audience here is narrow and specific. It is people who already have SIP or XMPP infrastructure, or who run an IRC network, and who want a single Java desktop client for it. It is not for someone who wants to start a video call by sharing a link.

How the Java client handles SIP, XMPP/Jabber and IRC at once

The repository layout shows the architecture without needing to read the source. A top-level pom.xml and a .mvn directory mark this as a Maven multi-module Java build. The modules/ directory holds the functional units, lib/ holds bundled dependencies, and native/ holds platform-specific code that the Java layer calls into. resources/ and docs/ carry assets and documentation, and lombok.config indicates Lombok is used to reduce boilerplate in the Java sources.

That structure explains the practical behaviour. Protocol support is not a single monolith; each protocol is a module plugged into a common user interface and a common contact list. A SIP account and an XMPP account can therefore coexist in one running application, which is the reason this client exists rather than a protocol-specific one. The native/ directory is the trade-off that comes with Java: where the JVM cannot reach the operating system directly, for example audio capture or desktop integration, platform code fills the gap.

The debian/ directory is also visible at the top level, which is consistent with the README offering an APT repository for Debian and Ubuntu. The build is driven by Maven, and the README links two GitHub Actions workflows, java.yml and installers.yml, which build the Java code and the installers respectively.

Installing Jitsi Desktop on Windows, macOS and Debian or Ubuntu

Installation depends entirely on the platform. For Windows and macOS, the README says to download the installers from GitHub releases at https://github.com/jitsi/jitsi/releases/latest/. There is no build step and no package manager involved; you download an installer and run it.

For Debian and Ubuntu, an APT repository is available. The README gives this exact line, and warns that the trailing slash at the end of the distribution name is required because the repository has no components:

deb https://nexus.ingo.ch/jitsi-desktop-unstable/ <distro>/

Replace the distribution name with your own, keeping the trailing slash. If you drop the slash, the entry will not resolve. The README also states plainly that there are currently no RPM packages available, so Fedora, RHEL and openSUSE users have no supported install path from this project.

Snapshot or pre-release builds are published separately. For Windows and macOS they appear under https://github.com/jitsi/jitsi/releases, and for Debian and Ubuntu they live in the unstable repository at https://nexus.ingo.ch/jitsi-desktop-unstable/. The README does not document rollback from a snapshot build, so treat those as a separate track from the stable installers.

Once installed, the first real use is adding an account. The README does not walk through the account setup screens, so the reliable starting point is the Documentation Wiki at https://github.com/jitsi/jitsi/wiki, which the README lists under Helpful Resources alongside the Community Forums at https://community.jitsi.org/c/jitsi-desktop/.

The maintenance question the README answers directly

The Support section of the README is unusually candid. It states that Jitsi Desktop is the heritage of Jitsi Meet, that some components are still used in projects such as Jigasi, and that "the project is not actively developed anymore". Improvements, bugfixes and builds are, in its own words, entirely based on community contributions.

The repository is not archived, and the last push was on 2026-09-22, so code is still moving. But an active push date and an active project are different claims, and the README explicitly declines the second one. Treat community contributions as the maintenance model: fixes arrive when someone contributes them, not on a roadmap.

The release history reinforces the point. The most recent listed release is v2.11.5633 from 2020-11-08. Before that, Jitsi 2.8.5426 and Jitsi 2.6.5390 both date from 2017-10-01. A stable release cadence measured in years, with the newest stable build several years old, is the concrete shape of a heritage project. Anyone evaluating Jitsi Desktop for a workplace deployment should weigh that against the protocol support it offers, because the protocol support is genuinely hard to replace in a single client.

Where Jitsi Desktop is the wrong tool

The clearest failure mode is a category error: using it for what Jitsi Meet does. If you want a browser link that opens a video room for people who have installed nothing, Jitsi Desktop is the wrong project. It is an installed client, and the README's opening warning exists precisely because people arrive looking for the conferencing service.

Platform coverage is the second limit. The README states there are currently no RPM packages, so RPM-based distributions are unsupported through the project's own channels. Windows and macOS users get installers from GitHub releases, and Debian and Ubuntu users get the APT repository, but there is no equivalent offer for the RPM family.

Third, the maintenance model is a real constraint rather than a footnote. A project whose README says it is not actively developed will not guarantee timely fixes for security or interoperability problems. For a personal XMPP or IRC client that is a manageable risk. For an organisation standardising its staff on one communicator, it is a decision that needs to be made deliberately, with the community contribution model understood in advance.

How Jitsi Desktop differs from Jitsi Meet

The natural alternative is Jitsi Meet, and the difference is architectural rather than a matter of features. Jitsi Meet is an online video conferencing solution with a free instance at https://meet.jit.si, reached through a browser. Jitsi Desktop is a Java application you install, and it speaks SIP, XMPP/Jabber and IRC as a client.

That means the two solve different problems. Jitsi Meet gives a meeting room with a URL and no installation. Jitsi Desktop gives persistent accounts and protocol connections on your own machine. If your requirement is joining an existing XMPP or SIP deployment with a desktop client, Jitsi Meet does not help you at all. If your requirement is a quick group video call with people outside your network, Jitsi Desktop is the wrong starting point.

The relationship is not purely historical either. The README notes that some Jitsi Desktop components are still used in Jigasi, so the older codebase has not been abandoned as a source of components even though it is no longer developed as a product.

Licence and the cost of staying on an older build

Jitsi Desktop is licensed under Apache-2.0, and the LICENSE file sits at the top level of the repository. Apache-2.0 is a permissive licence, which in practice means you can use, modify and redistribute the code, including in commercial settings, provided you meet the licence's conditions. This is a description of the licence identifier, not legal advice; if you plan to redistribute a modified build, read the LICENSE file and take your own advice.

The upgrade cost is the more pressing question. Because the README states the project is not actively developed and improvements come entirely from community contributions, there is no vendor to escalate to and no committed release schedule. The stable release line is old, and snapshot builds are published separately, which means an organisation that needs a fix may be choosing between an old stable build and a pre-release one. The README does not document a rollback path from snapshots, so that choice should be made before deployment, not after. If you install through the APT repository, the distribution name and its trailing slash are part of your configuration and need to be maintained alongside it.

Editorial conclusion

Adopt Jitsi Desktop only if you need a single desktop client for SIP, XMPP/Jabber and IRC and you accept that the project is not actively developed. Do not adopt it if you want Jitsi Meet video conferencing, a maintained client, or RPM packages, which the README says do not exist. Before installing, verify the current release on GitHub releases and the Debian/Ubuntu APT repository at https://nexus.ingo.ch/jitsi-desktop/, including the trailing slash the README requires after the distribution name.

Frequently asked questions

Official sources

1. jitsi/jitsi on GitHub
2. License: Apache-2.0
3. Project website
4. README
5. Releases