Open-source project
vkohaupt/vokoscreenNG avatar
vkohaupt/vokoscreenNG

vokoscreenNG for Linux and Windows screen recording

vokoscreenNG is a powerful screencast creator in many languages to record the screen, an area or a window. Recording of audio from multiple sources is supported. With the built-in camera support, you can make your video more personal. Other tools such as systray, magnifying glass, countdown, timer, Showclick and Halo support will help

1,523 stars113 forksC++GPL-2.0

At a glance

What is it?
vokoscreenNG is a Qt-based screencast application for recording screens, areas, and Linux windows with audio and camera input. It suits users who want a desktop recording interface, but its dependency set and lack of project-provided installers make packaging an important adoption constraint.
Who is it for?
Users who want a desktop-oriented recorder with configurable audio, camera input, and recording aids should evaluate vokoscreenNG, especially on Linux. Users who need unattended headless recording or a project-supplied cross-platform installer should look elsewhere.
Can I use it commercially?
Yes, with conditions. GPL-2.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 received new commits within the last day.
What is it written in?
Mainly C++, according to GitHub's language statistics.

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

Editorial analysis

vokoscreenNG capture scope and recording workflow

vokoscreenNG addresses desktop screencasting for users who need to record a presentation, application demonstration, selected region, or window. On Linux, the documented capture scope includes a screen, an area, or a window. Window capture is not listed for Windows, so the two platforms do not have identical capture capabilities.

The application combines visual capture with audio from multiple sources. It also has built-in camera support, which allows a camera feed to be incorporated into a recording rather than requiring every presenter to prepare that layer in a separate editor. Presentation helpers named in the project description include a countdown, timer, Showclick, and Halo support. A magnifying glass, system tray integration, and related controls are intended to keep recording actions accessible while presenting.

The README presents these as GUI features but does not document the internal recording pipeline, command-line interface, unattended mode, or headless behavior. The repository layout identifies a C++ project with its implementation under `src/`, while the Linux dependency list points to Qt6 for the interface and GStreamer components for audio, video, containers, encoding, camera input, and playback-related formats. That supports a Qt interface over a multimedia stack, but the precise pipeline graph is not specified and should not be inferred beyond those documented components.

Linux installation through distribution packages

The documented package route is the simplest starting point for Linux users because the project explicitly does not provide its own Linux installation routine. The README links packages for several distributions. Package names are not identical across package managers, so copy the command for the distribution in use.

For Debian or Ubuntu, the README lists this installation command:

bash
sudo apt install vokoscreen-ng

After a successful installation, the package should make vokoscreenNG available through the desktop environment. The README does not give the executable name or launch command, so this article does not invent either one.

Fedora uses the following documented command:

bash
sudo dnf install vokoscreenNG

openSUSE has separate package links for Tumbleweed and Leap and uses:

bash
sudo zypper install vokoscreenNG

Arch Linux is listed under the package name `vokoscreen`, despite the project being named vokoscreenNG:

bash
sudo pacman -S vokoscreen

For NixOS, the README gives:

bash
nix-env -iA nixos.vokoscreen-ng

These commands install a distribution-managed build. Their availability depends on each distribution's repository and package version, which may not match the recent vokoscreenNG release listed by the repository.

Building vokoscreenNG from the 3.0 branch

For Linux systems without a listed package, or for developers preparing a local build, the README documents a short qmake build sequence. The documented build requirements are `pkgconfig`, `libqt6-devel >= 6.9`, `libqt6-linguist >= 6.9`, `libX11-devel`, `gstreamer-devel`, `libpulse-devel`, and `wayland-devel`.

After installing those requirements through the system package manager, enter a local clone and build the `src` directory with the documented commands:

bash
cd src
qmake6
make

The command sequence assumes that the reader has already downloaded or cloned the repository and changed into its root directory. `qmake6` generates the build files from the project configuration, and `make` compiles the project. The README does not provide a test command, installation target, resulting binary path, or packaging commands, so this sequence establishes a build rather than a verified system installation.

The source build also inherits the runtime requirements listed later in the README, including Qt6, PulseAudio, Wayland libraries, and several GStreamer plugin groups. A successful compile therefore does not mean that every capture source or output format will work until the runtime libraries are present.

GStreamer, Qt6, PulseAudio, and Wayland dependencies

vokoscreenNG's Linux runtime requirements are broader than a basic Qt application. The README requires `Qt6 >= 6.9`, `pulseaudio`, `libwayland-client0`, and `gstreamer >= 1.22.8`. These dependencies connect the interface, desktop audio, Wayland support, and multimedia processing, although the README does not provide a component-by-component architecture.

The required GStreamer packages are divided by function. `gstreamer-plugins-base` supplies audio codecs named as vorbis and opus. `gstreamer-plugins-good` provides mkv and mp4 support along with FLAC audio. `gstreamer-plugins-bad` supplies camera and OpenH264 video support. `gstreamer-plugins-ugly` supplies x264 video and MP3 audio, while openSUSE Packman may provide `gstreamer-plugins-ugly-orig-addon` for x264. `gstreamer-plugins-libav` is listed for a player and x264, and `gstreamer-plugins-rs` supplies GIF video.

That split is operationally significant. A missing plugin can remove a particular format, codec, camera path, or presentation feature even if vokoscreenNG itself starts. The list also suggests a format choice boundary: the documented set includes mkv, mp4, FLAC, MP3, GIF, OpenH264, and x264, but the README does not state which combinations are exposed in the interface or which encoder settings are selectable.

For Wayland, the README additionally requires `pipewire >= 1.0.0`, `gstreamer-plugin-pipewire >= 1.0.0`, `xdg-desktop-portal >= 1.18.2`, and a desktop portal for KDE, GTK, GNOME, or another desktop environment. Users should not assume that installing Wayland libraries alone is sufficient for screen capture on a particular desktop.

Windows availability and build requirements

vokoscreenNG supports Windows, but the project sends users to its own download page rather than documenting a direct installer command. The repository contains Windows build requirements for Windows 10 64-bit. For version 4.10.0 and later, the README lists Qt 6.10.0 through the Qt Online Installer, including Qt Network Authorization, Qt Creator, debugging tools, and OpenSSL 1.1.1 toolkit components. It also links a GStreamer 1.28.1 MSVC installer.

The build-requirements section marks older 32-bit `vc_redist.x86.exe` and MinGW 11.2.0 entries as obsolete. This matters for anyone following an older build guide, because those entries no longer describe the documented Windows setup.

The Windows package differs from Linux in its named toolchain and multimedia stack. The README does not provide Windows build commands, an MSVC configuration procedure, a camera dependency list, or confirmation of the supported Windows capture APIs. Its Linux-only qualification for window capture is another concrete platform boundary. A Windows evaluation should therefore focus on the download route and the features shown for that build rather than assuming parity with Linux.

Packaging, licensing, and maintenance constraints

The project intentionally leaves installation routines to platform packagers and installer authors. The README says that installation metadata, desktop files, icons, a manpage, and logos must be created and supplied by each packaging route. This choice avoids forcing one installer model across Linux and Windows, but it creates work for anyone distributing vokoscreenNG themselves. The repository does not include a finished platform-neutral installer in the documented download section.

The repository is licensed under GPL-2.0. That is the project license for the repository as described here, but this article does not provide legal advice about how a particular distribution or derivative should comply. Contributions have separate terms. The README asks contributors to obtain agreement before submitting code and requires source code to remain in separate files under the MIT License, with the required license header included. That distinction matters when reviewing contribution patches or packaging bundled components.

The repository is not archived, and its last push was on 2026-10-17. Recent releases include 4.11.0 on 2026-10-02, 4.10.0 on 2026-06-27, and 4.9.0 on 2026-04-11. The release cadence provides evidence of ongoing project changes, while the required Qt6, GStreamer, PulseAudio, PipeWire, and portal versions create upgrade work for packagers. The README does not define a migration procedure from an older release.

Where vokoscreenNG is the wrong recording choice

The clearest limitation is the absence of documented unattended or headless recording controls. vokoscreenNG is described as a desktop screencast creator with graphical helpers such as systray, countdown, timer, Showclick, and Halo. Nothing in the README describes a CLI, scheduled recording, remote control interface, or unattended capture workflow. A user who needs recordings to start and stop through scripts should verify those functions before adopting it.

Linux users also face a meaningful dependency surface. Recording multiple audio sources and camera video depends on several GStreamer plugin groups, while Wayland capture requires PipeWire, a GStreamer PipeWire plugin, desktop portals, and a compatible desktop environment. A packaged installation can therefore look complete while still failing for a particular source or format if optional plugins are absent or portal access is restricted.

The practical alternative approach is to use a command-driven multimedia pipeline built around GStreamer and FFmpeg. Such a setup can be configured as a script and directed by a scheduler or another application, which differs from vokoscreenNG's desktop controls and presenter aids. The README does not compare encoder quality, resource use, or output fidelity, so the choice should be based on control requirements and available desktop integration rather than unsupported performance claims.

Editorial conclusion

Users who want a desktop-oriented recorder with configurable audio, camera input, and recording aids should evaluate vokoscreenNG, especially on Linux. Users who need unattended headless recording or a project-supplied cross-platform installer should look elsewhere. Verify first that the desired distribution package or build environment includes the required Qt6 and GStreamer components, then confirm that screen, audio, camera, and output-format behavior fits the intended recording setup.

Frequently asked questions

How do I install vokoscreenNG on Linux?

The README lists distribution packages for Debian, Ubuntu, Fedora, openSUSE, Arch Linux, and NixOS. It also documents a source build using `qmake6` and `make` from the `src` directory.

Does vokoscreenNG record audio from more than one source?

Yes. The project description states that recording audio from multiple sources is supported. The README also lists audio-related GStreamer plugins and codecs.

What are the main vokoscreenNG limitations on Linux?

Linux builds require Qt6, GStreamer plugin groups, PulseAudio, and additional components for Wayland. The project does not document a CLI, unattended recording mode, or a project-provided Linux installer.

Official sources

  1. License: GPL-2.0
  2. Project website
  3. README
  4. Releases
  5. vkohaupt/vokoscreenNG 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/vkohaupt-vokoscreenng.svg)](https://hysenlabs.com/projects/vkohaupt-vokoscreenng)

Was this useful?