Open-source project
SeaDve/Kooha avatar
SeaDve/Kooha

Kooha records through a desktop portal, and its own troubleshooting section has the heading It Doesn't Work

Elegantly record your screen

3,562 stars103 forksRustGPL-3.0

At a glance

What is it?
Kooha is a Rust and GTK screen recorder whose capture path depends on pipewire and a desktop portal, so whether it works at all is a question its README hands to another project's wiki. Its headline hardware-accelerated encoder is the same feature it lists as disabled for stability, and its development profile ships without backtrace line numbers.
Who is it for?
Kooha is a good fit for a GNOME desktop where you want a recorder with one button and no settings panel, particularly on Wayland where the portal is the only route to a screen capture. Two things to check before you install it.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 9 days ago.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • SeaDve/Kooha3,562 ★ · +48
Star history
Repository2026-09-242026-11-15
SeaDve/Kooha3.5k3.6k

48 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Capture goes through a portal, not through the app

The runtime requirements are four entries, and one of them is not a package you can install from a name. You need pipewire, the GStreamer pipewire plugin, xdg-desktop-portal, and xdg-desktop-portal with a suffix naming your desktop environment, given as examples of gtk, kde or wlr. So the application depends on the desktop's own screencast portal to obtain frames, which is the mechanism that lets an unprivileged program capture a Wayland session. That design choice explains the section headed It Doesn't Work, which opens by saying there are many possibilities, names a missing runtime requirement or an unsupporting distribution as the likely cause, and then points at the screencast compatibility page and the troubleshooting checklist in the xdg-desktop-portal-wlr wiki. The project's own documentation admits it cannot diagnose this on its own.

The headline encoder is the feature marked unstable

Five bullets describe what the recorder does, and the fifth is experimental hardware-accelerated encoding. The experimental features table then names four switches: all, experimental-formats, multiple-video-sources and window-recording. experimental-formats is described as enabling other codecs, with hardware-accelerated encoders, VP9 and AV1 named as examples, and its issue column says stability. multiple-video-sources carries stability and performance, and window-recording carries flickering. So the accelerator that appears in the feature list is gated behind the same key as the two new video codecs, all of it off by default because of stability issues and possible performance degradation, and enabled by setting an environment variable to all or to a comma-separated list of keys.

The development profile strips out line numbers

The manifest contains a build profile with a comment explaining a deliberate trade-off. The development profile sets debug to zero and strips debuginfo, and the comment above it says not to compile and link debug info because it reduces build times at the cost of not having line numbers in backtraces. So a developer working on Kooha gets faster rebuilds in exchange for backtraces that point at a function rather than a line. The release profile takes the opposite trade on optimisation, with link time optimisation enabled and nothing said about debug information, which is the usual arrangement. Everything else in the profile section is conventional, and the rest of the manifest is a normal dependency list with a version floor on the compiler itself.

Both graphics backends are compiled in unconditionally

Look at which graphics bindings are required rather than optional. The manifest lists both the Wayland GTK binding at version 0.11 and the X11 one at the same version, with neither behind a feature flag. The GStreamer GTK plugin is configured with dmabuf, gtk_v4_14, wayland, x11egl and x11glx, so both display server paths and the zero-copy buffer sharing path are compiled in on every build, including the ones where the user cannot turn acceleration on. That is the practical consequence of the experimental table: the code for the unstable features ships in the binary regardless, and the switch only controls whether the application uses it. The version floors are also in this list, with libadwaita at 0.9, gtk4 at 0.11 and gstreamer at 0.25, which is a recent toolchain floor for a distribution package.

Two settings mechanisms sit in one manifest

The feature list says the saving location, pointer visibility, frame rate and delay are configurable. The manifest then carries two unrelated mechanisms for configuration. A GSettings macro crate appears among the dependencies, which is the GNOME way of exposing application settings, and a YAML serialisation library appears beside the JSON one, which is not. Neither is marked optional and neither is commented. So the settings a user can change are backed by two configuration systems in one binary, and the README says nothing about which is which or where either file lives. For a project whose selling point is a minimal interface, that is an implementation detail a packager would need to know about and cannot get from the documentation. The dependency list also shows the settings are not stored through the GNOME database alone, since a YAML serialiser would have nothing to write into without a file of its own.

The recommended build is a sandbox, the manual one writes to /usr/local

Two build paths, and the README is emphatic about the first. GNOME Builder is described as the environment used for developing the application, with the reason given that it can use Flatpak manifests to create a consistent building and running environment across distributions, and it is highly recommended. The manual path is Meson, and the whole sequence is four lines:

shell
git clone https://github.com/SeaDve/Kooha.git
cd Kooha
meson _build --prefix=/usr/local
ninja -C _build install

The build directory name starts with a low line character, which keeps it out of the way of a source tree glob, and the final step is what makes the route a system-wide one. That last step is a system-wide install, so it is a root operation on a machine where the sandboxed path would not be. The prerequisite list is annotated in a way that saves time: x264 and the ugly GStreamer plugin set are both named for MP4, and the bad plugin set for VA encoders, which tells you which formats need which packages.

Distribution packages are explicitly unsupported

The third-party packages section is three sentences and one of them is a warning. It says that, unlike Flatpak, those packages are not officially supported by the developer, and then points at Repology for the list of other packages. That is a clear division of responsibility: the Flatpak build is the one the project stands behind, the header links to the Flathub listing, and everything else is best effort from packagers. The application identifier follows the same pattern, using the GitHub-style io.github prefix, which is what the experimental features example uses in its command line. So a distribution package may differ from the Flatpak build in ways the developer is not tracking, and a bug report against one is not the same as a bug report against the other.

Three releases over two years, and a root full of metadata

The release history is three tags over about two years and two months: v2.3.0 on 2024-03-21, v2.3.1 on 2025-08-23 and v2.3.2 on 2026-06-05. The manifest version is 2.3.2, matching the newest tag exactly, and it declares edition 2024 with a compiler floor of 1.90. The root of the repository is more interesting than a typical source tree: a copying file rather than a licence file, a metadata file named after the project, a spell checker configuration, a directory for translation catalogues, a build auxiliary directory alongside the Meson files, and a data directory for the user interface. The translation catalogues pair with the manifest's choice to use the system gettext rather than bundling it.

Editorial conclusion

Kooha is a good fit for a GNOME desktop where you want a recorder with one button and no settings panel, particularly on Wayland where the portal is the only route to a screen capture. Two things to check before you install it. Whether it will work on your system is not something the application can tell you: it needs pipewire and the desktop portal for your session, and the README sends you to another project's compatibility wiki to find out. And the experimental switch is where the interesting features live, including the hardware-accelerated encoder, so expect to read that table before deciding the default build is enough. If you rely on distribution packages, note that the developer does not support them, and the manifest sets a Rust floor of 1.90 with a recent GTK and libadwaita, which narrows which distributions can build it.

Frequently asked questions

What is Kooha?

It is a screen recorder for the GNOME desktop, written in Rust with GTK and libadwaita. You press one record button rather than configuring settings first. It can record the microphone, desktop audio or both, supports WebM, MP4, GIF and Matroska, and can record a whole monitor or a portion of the screen.

How do I install Kooha?

The recommended route is GNOME Builder, which can use the Flatpak manifest to build a consistent environment across distributions: clone the repository with its Clone Repository button and press build. The manual route is Meson, with git clone, a meson setup into a _build directory prefixed at /usr/local, and a ninja install. A Flatpak build is linked from the header and distribution packages are explicitly not supported by the developer.

Why does Kooha not work on my distribution?

The README offers two explanations: the runtime requirements are not installed, or the distribution does not support the screencast portal. It needs pipewire, the GStreamer pipewire plugin, xdg-desktop-portal and the portal for your desktop, and it sends you to the screencast compatibility page and the troubleshooting checklist in the xdg-desktop-portal-wlr wiki to find out whether your system supports capture out of the box.

How do I enable Kooha's experimental features?

Run Kooha with the KOOHA_EXPERIMENTAL environment variable set to all, or to a comma-separated list of keys. The keys are experimental-formats for hardware-accelerated encoders, VP9 and AV1, multiple-video-sources for recording several monitors or windows, and window-recording for a specific window. They are off by default because of stability issues and possible performance degradation.

What is an alternative to Kooha?

The repository names no alternative screen recorder and makes no comparison with one. It does name its own inspirations, crediting RecApp for inspiring the creation of the app and GNOME Screenshot as the reference for the icon design, and it thanks GStreamer, GTK and libadwaita as the projects it is built on.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. README
  4. Releases
  5. SeaDve/Kooha on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/seadve-kooha.svg)](https://hysenlabs.com/projects/seadve-kooha)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/seadve-kooha.svg)](https://hysenlabs.com/projects/seadve-kooha)

Was this useful?