Open-source project
benjamimgois/goverlay avatar
benjamimgois/goverlay

Goverlay: A Qt6 Frontend for MangoHud, vkBasalt, and Proton Tweaks

Goverlay is an easy graphical interface to configure linux gaming applications.

1,483 stars66 forksPascalGPL-3.0

At a glance

What is it?
Goverlay is a graphical configuration tool for Linux gaming stacks, wrapping MangoHud, vkBasalt, vkSumi, OptiScaler, and Proton environment tweaks into a card-based UI. It generates per-game config files and launch commands for Steam or Lutris.
Who is it for?
Adopt Goverlay if you are a Linux gamer who wants a visual way to manage MangoHud, vkBasalt, vkSumi, and Proton environment overrides without editing config files by hand. It is not for you if you prefer manual config management or need to run on Fedora, Debian, or Ubuntu without Flatpak, since those repositories often ship outdated versions.
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 1 day ago.
What is it written in?
Mainly Pascal, according to GitHub's language statistics.

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

DEEP OPEN-SOURCE ANALYSIS

What Goverlay Actually Solves

Linux gaming often means juggling several separate tools: MangoHud for performance overlays, vkBasalt for post-processing, vkSumi as an alternative post-processor, OptiScaler for upscaling, and Proton environment variables for per-game tweaks. Each has its own config file format and launch command syntax. Goverlay wraps these into a single Qt6 GUI with a card-based layout, so you can enable, disable, and tune these tools without opening a terminal or reading multiple man pages. The target user is a Linux gamer who wants the performance and visual benefits of these tools but does not want to manage them as separate text configs. The README describes it as a 'modern Qt6 GUI application' that 'puts powerful performance and visual tools behind an easy-to-use interface.' The project is written in Pascal, which is unusual for GUI tools, but the user-facing interface is what matters.

Per-Game Config Architecture and Game Mode

The key mechanism is the per-game config directory. When you select a game, Goverlay switches to Game Mode and creates an XDG-compliant directory for that game. Inside it, you get files like MangoHud.conf, vkBasalt.conf, vkSumi.conf, OptiScaler.ini, fakenvapi.ini, and bgmod.conf. The bottom launch command box updates to show a game-specific command with a %command% suffix, ready to paste into Steam. This means each game can have its own overlay settings, post-processing effects, and environment variables without affecting others. The architecture is a clear improvement over global config files, but it also means more moving parts: every game has its own directory, and you need to know which file controls what. The README does not explain the exact XDG path, so you will have to discover it in the app or in the generated files.

The bgmod Wrapper and Its Role

bgmod is a compiled Free Pascal binary, not a bash script, that replaces the legacy fgmod approach. It intercepts game execution arguments, exports environment variables from bgmod.conf, sets up Wine DLL overrides, copies upscaler binaries and plugins into the game folder on launch, and supports launcher EXE replacements and UE Shipping EXE auto-discovery. It logs to /tmp/bgmod.log, the game directory, and ~/.local/share/goverlay/logs/[Game Name]/. There is also an uninstaller binary, bgmod-uninstaller, that removes wrapper files and restores original backups. This wrapper is the bridge between Goverlay's GUI and the actual game process. Because it is a compiled binary, it avoids some of the fragility of shell scripts, but it also means you need to trust a binary that modifies your game directories. The README does not detail how the wrapper handles game updates or Steam verification, which could be a concern if a game overwrites the copied files.

Getting It Running: Flatpak, AppImage, and Distro Packages

The README gives clear installation paths. The universal method is Flatpak: add the Flathub repository, install io.github.benjamimgois.goverlay, and then install the required Vulkan layers for MangoHud and vkBasalt from the freedesktop platform. vkSumi requires a separate flatpak runtime downloaded from its GitHub page. Alternatively, you can download an AppImage from the Releases page, chmod +x it, and run it. For Arch, you can use the official repository with sudo pacman -S goverlay or the AUR with yay -S goverlay-git. OpenSUSE and Solus have packages as well. The README warns that Fedora, Debian, and Ubuntu official repositories often ship outdated versions, so it strongly recommends Flatpak or AppImage for those distros. You also need libqt6pas, which is not available in some repos; the README points to a third-party repository with a .deb example. The note about MangoHud being required since version 0.6.4 is important: you must install MangoHud separately, or Goverlay will not run.

Integrated Vulkan Preview: PasCube

Goverlay ships with PasCube, a full Vulkan demo compiled from the PasVulkan engine. It launches automatically or on demand to preview your MangoHud, vkBasalt, and vkSumi settings in real time. The demo title bar and overlay display the current GOverlay version. This is a useful feature because it lets you see the effect of your config changes without launching a full game. However, it is a Vulkan demo, so it will not exercise any OpenGL or DXVK paths. If you are tweaking settings for a specific game engine, you may still need to launch the game to see the real result. The README does not specify whether PasCube can be run standalone or only from within Goverlay, but it says it launches automatically or on demand, so the integration is likely tight.

Limitations and Wrong-Tool Cases

The most obvious limitation is the dependency on MangoHud: the README says 'Since version 0.6.4, MangoHud must be installed to run Goverlay.' That means this is not a standalone config tool; it is a frontend for a specific stack. If you do not use MangoHud, there is no reason to use Goverlay. Another limitation is the Flatpak sandbox: the README notes that in Flatpak, Goverlay hides host-dependent features such as GameMode and Protontricks because it cannot reliably detect or execute host binaries. So if you rely on Protontricks for prefix management, you will need the native build, which may be outdated on some distros. The bgmod wrapper copies binaries into game folders, which could break anti-cheat or game updates, though the README does not discuss that risk. Finally, the project is written in Pascal with Lazarus, which is a niche stack; that may affect long-term maintenance if the original author steps away, but the project has recent releases as of August 2026, so it is active.

Alternatives: Manual Config vs. Other GUIs

The direct alternative is to configure MangoHud and vkBasalt manually. MangoHud reads a config file, typically at ~/.config/MangoHud/MangoHud.conf, and you set environment variables like MANGOHUD=1 to enable it. vkBasalt uses vkBasalt.conf and requires setting ENABLE_VKBASALT=1. This approach gives you full control but requires learning each tool's syntax. There are also other GUI tools, such as MangoHud's own simple config editor, but the README does not mention any by name. The key difference is that Goverlay centralizes not just MangoHud but also vkBasalt, vkSumi, OptiScaler, and Proton env vars into one interface, and it generates the launch command for you. Manual config means you have to remember to set the right environment variables for each game, which is error-prone. Goverlay's per-game directories reduce that risk, but they also add abstraction. If you prefer minimal dependencies, manual config is lighter.

Maintenance and License Implications

Goverlay is licensed under GPL-3.0, which means if you distribute modified versions, you must make the source available under the same license. For personal use, this has no practical impact. The project is actively maintained, with a nightly release and a stable 1.9.0 from August 2026. The README credits the original maintainers of the core tools, so Goverlay depends on those upstream projects. Upgrading Goverlay may require upgrading the core tools to match config formats, but the README does not specify any version compatibility matrix. The Flatpak installation includes Vulkan layers from the freedesktop platform, which are updated separately, so you may see version mismatches if you update one side. The tarball and AppImage options give you a standalone binary, but you still need to install MangoHud and other dependencies yourself. The maintenance cost is low for end users: you update via your package manager or Flatpak, and the per-game configs are plain text files that you can back up.

Editorial conclusion

Adopt Goverlay if you are a Linux gamer who wants a visual way to manage MangoHud, vkBasalt, vkSumi, and Proton environment overrides without editing config files by hand. It is not for you if you prefer manual config management or need to run on Fedora, Debian, or Ubuntu without Flatpak, since those repositories often ship outdated versions. Before adopting, verify that your distro provides recent packages or use the Flatpak, and confirm that MangoHud is installed because Goverlay requires it since version 0.6.4. Also check that your GPU and drivers support Vulkan layers, as the tool depends on them.

Official sources

  1. Official README
  2. Project repository
  3. Release notes
Community notes

Community notes