Presenter 2026 Linux?

You need to create a .desktop file for presenter.

Gear Lever can do that automatically for you if you use that, other wise you'll have to do it manually.

If I remember I'll share mine when. I get home.

Devs, would be great if Presenter could do this?

I created the following .desktop file (on Fedora Workstation). This works for the web browser callback when you sign in.

[Desktop Entry]
Type=Application
Name=Presenter 2026_beta
Exec=/home/<user>/Presenter/Presenter-2026.1.0-beta.23.AppImage %u
Icon=presenter_2026_beta
MimeType=x-scheme-handler/presenter
Categories=AudioVideo;

After some much needed vacation, I'm home, and attempting to try out the latest beta (29) and even after creating the desktop entry shared by Paul, I'm still not able to get Presenter signed in, though, I can now see the browser attempting to open Presenter.

We are running Ubuntu 26.04 LTS, and Presenter 2025.1.1 is working without issue.

Thanks!

This works for me on Linux Mint. It was created by GearLeaver

[Desktop Entry]
Type=Application
Name=Presenter
Comment=Church presentation software
Icon=/home/<user>/AppImages/.icons/presenter.appimage_2026_1_0-beta_29_2026_1_0-beta_29
TryExec=/home/<user>/AppImages/presenter.appimage_2026_1_0-beta_29_2026_1_0-beta_29.appimage
Exec=env DESKTOPINTEGRATION=1 /home/<user>/AppImages/presenter.appimage_2026_1_0-beta_29_2026_1_0-beta_29.appimage --no-sandbox %U
Terminal=false
MimeType=x-scheme-handler/presenter;
Categories=AudioVideo;
StartupWMClass=Presenter
X-AppImage-Version=2026.1.0-beta.29.2026.1.0-beta.29
X-AppImage-Name=Presenter

According to gemini:

The .desktop file must be located in either ~/.local/share/applications/ or /usr/share/applications/

The AppImage needs execution rights:
chmod +x /home/<user>/Presenter/Presenter-2026.1.0-beta.23.AppImage

After saving or modifying the desktop entry:
update-desktop-database ~/.local/share/applications
xdg-mime default <filename>.desktop x-scheme-handler/presenter

Test it:
From the terminal:
xdg-open presenter://test-payload
From the browser: Type presenter://test into the address bar. The browser should present a prompt asking: "Open Presenter 2026_beta?" or "Allow this site to open the presenter link?".

Hi guys,

I am on Linux and my media team are currently using the legacy edition, is the beta version on Linux any good?

What are some pros and cons on beta on Linux vs legacy?

The 2026 beta version(s) seem to work exactly like the Windows version. Aside from some hassle of setting up desktop launcher, it works well. I did find that an older computer that ran the "legacy" 2025 version fine would not run the 2026 beta version. It was running linux Mint 21, and I had to upgrade it to Mint 22 in order for it to have the latest libraries that Presenter 2026 required. My other comment is that Worship Tools has been rolling out patches/updates about every week or two, so you'll likely have to keep re-doing the desktop launcher (or else just launch it from the app menu list). The earlier versions definitely had bugs and missing features, but they've been tackling them and fixing them regularly. We are on beta 32 right now and it keeps improving.

Thank you Leon.

I have downloaded version 2026.1.0-beta.17, I had to use AppImage Launcher to integrate it in order to sign in, it would not let me sign in otherwise, then, once i signed in, it auto downloaded Presenter-2026.1.0-beta.32.AppImage.

AppImage launcher has now buggered around with all my other AppImages.

Did anyone else have this problem, or did they just sign in?

Anybody tested ndi on Linux yet?

Thanks for supporting Linux! It's incredibly frustrating to see other services like Proclaim continuing to ignore the growing number of churches using Linux for their backend. I too am curious why the Linux version seems to be hidden; last I checked, you had to go to a post detailing the ChromeOS installation instructions, download a Bash script, and find the AppImage URL hidden inside.