- Top Pick: LG UltraGear 27GR83Q-B
- Runner-up: Sapphire Pulse Radeon RX 9070 XT
- Also consider: WD_BLACK SN850X 2TB NVMe SSD
The Linux performance-overlay stack is powerful but stubbornly text-driven. MangoHud wants a config file, vkBasalt wants another, and every experiment means editing key-value lines and restarting the game. GOverlay exists to remove that friction: a desktop application that writes those same config files for you, from toggles, sliders and dropdowns.
This guide explains what GOverlay does, which tools sit behind its tabs, and how its per-game profiles and launch commands work. It also compares it with hand-editing and with SteamTinkerLaunch, covers install routes, and finishes with hardware that makes the data easier to read.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
GOverlay is a free Qt6 desktop app that configures MangoHud, vkBasalt, vkSumi and OptiScaler through toggles and sliders instead of text files. It writes the same config files, builds the launch command, and previews the overlay live. It renders nothing itself: the underlying tools still do the work in game.
What GOverlay is, and what it is not
GOverlay is an open-source graphical front end, written in Free Pascal with the Lazarus toolkit and released under the GPL-3.0 licence. Its job is configuration, nothing more. When you tick a metric or move a slider, GOverlay edits the plain-text files the tools already read: MangoHud.conf for the overlay, vkBasalt.conf for post-processing, vkSumi.conf for the alternative effects layer, and OptiScaler.ini for upscaling and frame generation. It also assembles the launch command you paste into Steam or Lutris.
Two design choices make it more than a pretty text editor. It ships PasCube, a small built-in Vulkan demo that runs your current settings live, so you can watch the overlay change and judge sharpening strength before committing to a long session. And it has a per-game mode: select a game and it gets its own configuration directory with its own copies of those files, plus a small compiled wrapper, bgmod, that applies the profile’s variables and DLL overrides at launch while keeping logs out of the game folder. A launch-command box always shows the matching command, ending in the standard Steam placeholder.
What GOverlay never does is inject code, hook a running game or render a frame of overlay itself. If the overlay appears, that is MangoHud working; if the image looks sharper, that is vkBasalt.
The tools behind the toggles
MangoHud is the foundation, and a hard requirement: the project notes that MangoHud must be installed before GOverlay will run. Its tab covers FPS and frametime readouts, CPU and GPU load, temperatures, clocks, power draw, RAM and VRAM use, plus the frame limiter and benchmark logging.
vkBasalt is the Vulkan post-processing layer, handling effects such as contrast adaptive sharpening and the FXAA and SMAA options, with effect order and per-effect strength as controls; recent releases added colour LUT support and native handling for ReShade-style effects. vkSumi is an alternative post-processor with its own parameter set, for players who prefer its look.
OptiScaler, with its fakenvapi companion file, is where upscaling and frame-generation bridging is configured per game: which backend a title should use.
Proton tweaks collects environment-variable switches, including the GameMode daemon toggle and options such as simulating a Steam Deck or enabling Wayland paths. The Lossless Scaling frame-generation layer, lsfg-vk, can also be managed when installed. Older release lines also carried a ReplaySorcery page; current documentation centres on the tools above, so check your build’s tab list.
The workflow, from toggle to game
A typical session looks like this. In the MangoHud tab you choose the metrics you read, drag the overlay to a corner, set font size, colours and background opacity, plus FPS limit and logging hotkeys. In the vkBasalt tab you enable effects, order the chain and set strengths, checking the result in the PasCube preview instead of relaunching a game six times. Then you either save globally, so every title inherits the setup, or clone the global profile into a specific game as a starting point. A blacklist covers programs where the overlay should never appear, and the launch command copies with one keyboard shortcut.
The mental model: saving writes files. Nothing applies to a running game, and a title only picks settings up if launched with the generated command, or with the plain overlay option pointing at the same global config.
GOverlay vs a text editor, and vs SteamTinkerLaunch
Against hand-editing, GOverlay’s win is discoverability. MangoHud has hundreds of keys; the GUI shows them grouped, with valid choices, and the preview shows the result immediately. Per-game profiles and one-click cloning save real time across a big library. Hand-editing still wins for some: no extra software, dotfiles in version control, configs generated by script. The two do not fight, because GOverlay reads and writes the same MangoHud.conf you could open in an editor afterwards.
SteamTinkerLaunch is a different animal: a launch-time wrapper you register as a Steam compatibility tool, with a wide feature net reaching into trainers, custom Proton builds and per-game launch logic. GOverlay is a standalone settings app you run before gaming, narrower but calmer: overlay, effects, upscaler bridging and Proton switches, with a live preview. If the overlay stack is all you want to tame, GOverlay is the lighter tool; SteamTinkerLaunch goes further and asks more of you.
Installing GOverlay
The Flatpak from Flathub is the route the project pushes first, and it pulls in the required Vulkan layers automatically. Two caveats apply. Host-dependent features such as GameMode and protontricks are hidden in the Flatpak build, because the sandbox cannot reliably reach host binaries. And if your games run inside Flatpak Steam, the layers still need to exist as Flatpak Vulkan-layer extensions matched to the game’s runtime branch; a host configurator cannot cross that boundary for you.
An AppImage from the releases page is the other universal option. Arch carries GOverlay in its official repositories (with a development build in the AUR), and openSUSE and Solus package it too. The project warns that Fedora, Debian and Ubuntu repositories often ship outdated versions, and recommends the Flatpak or AppImage there instead. Tarball and source builds exist but need a Lazarus and Qt6 toolchain. Either way, install MangoHud first, and add a Nerd Font if you want the interface icons to render as intended.
The honest limits
GOverlay configures; it does not optimise, and it cannot conjure features the underlying tools lack. If MangoHud is missing, outdated or the game never loads the Vulkan layer, no overlay appears, and the fix lies with the layer, not the front end. vkBasalt only affects Vulkan rendering paths, so it is no system-wide colour panel. OptiScaler and wrapper features depend heavily on the title, and DLL-override tricks are best kept to single-player games, since competitive anti-cheat is understandably hostile to modified game folders. Finally, any overlay plus post-processing adds some GPU work of its own; the practical advice is simple: keep the metric set lean on modest hardware.
Gear that makes overlay data easier to use
The overlay only helps if you can read it at a glance. These five products support that workflow: a fast main panel, a small second screen for logs, a current GPU whose sensors feed MangoHud’s richest readouts, fast storage, and a tiny second computer to drive the stats display.
LG UltraGear 27GR83Q-B
Frametime graphs only help if the panel can show the judder they describe. This 27-inch QHD IPS monitor runs at 240 Hz, so the display keeps up with MangoHud’s frame-pacing readouts.
Specs:
- 27-inch IPS panel, 2560 by 1440 resolution
- 240 Hz refresh rate via DisplayPort 1.4 or HDMI 2.1 (maker-stated)
- 1 ms GtG response time (maker-stated)
- VESA DisplayHDR 400, FreeSync Premium and G-Sync compatible
PeakDo 7-Inch Portable Touchscreen Monitor
A small second screen keeps frametime logs, dashboards and chat visible without covering the game. This 7-inch 1080p panel connects over one USB-C cable on hosts that support it, and its listing states touch input works on Linux.
Specs:
- 7-inch IPS touchscreen, 1920 by 1080, 60 Hz
- USB-C with DisplayPort alt mode, plus mini HDMI input
- Touch input listed as supported on Linux
Sapphire Pulse Radeon RX 9070 XT
MangoHud’s most useful readouts, GPU load, clocks, power and VRAM, come from a modern card with well-exposed sensors, which AMD’s open driver stack surfaces cleanly. This RDNA 4 card adds the headroom to use the effects and upscaling tabs, not just admire them.
Specs:
- AMD RDNA 4 GPU, model 11348-03-20G
- 16 GB GDDR6 memory
- Boost clock up to 2970 MHz (maker-stated)
- Dual HDMI and dual DisplayPort outputs
WD_BLACK SN850X 2TB NVMe SSD
Overlay logging, shader caches and a library big enough to need per-game profiles argue for fast, roomy storage. The SN850X is a proven Gen4 drive, and 2 TB keeps the games you tune installed, not archived.
Specs:
- 2 TB capacity, M.2 2280 form factor
- PCI Express Gen4 NVMe interface
- Sequential reads up to 7,300 MB/s (maker-rated)
- Model WDS200T2X0E, the heatsink-free version
Raspberry Pi 5 8GB
The tinker’s route: a Pi drives the small display with a dashboard fed by your gaming PC, so the rig runs the leanest possible overlay.
Specs:
- Model SC1112 with 8 GB LPDDR4X memory
- Quad-core Arm Cortex-A76 processor at 2.4 GHz (maker-stated)
- Dual micro-HDMI outputs supporting 4K at 60 Hz (maker-stated)
- USB-C power input; a 5 V, 5 A supply is the maker’s recommendation
- Board only: storage, cooling and power supply sold separately
How to choose
Match the install route to how your games are installed: Flatpak GOverlay for a native Steam, and extra care with layer extensions if Steam itself is a Flatpak. Decide early whether you are a global-profile person or a per-game tuner; mixing the two creates confusion. Keep the metric set purposeful: FPS, frametime and GPU load answer most questions, and every extra row is visual noise. Spend first on the main panel, where the overlay lives, and add the second screen only if you genuinely read logs while playing.
Who should skip this
Skip GOverlay if you already hand-edit MangoHud.conf happily and keep configs in version control; the GUI adds nothing you need. Skip it if you only play competitive multiplayer with strict anti-cheat and would never touch effects or upscaler bridging, since half the tabs are closed to you anyway. Skip it if you expect capabilities MangoHud itself does not have, because a front end cannot invent features. Steam Deck owners who never leave the built-in performance overlay gain little; GOverlay is aimed at desktop Linux.
FAQ
Does GOverlay improve performance?
No. It writes configuration files. Performance comes from the game, your hardware and your settings; the overlay MangoHud draws adds a small cost of its own, so keep the metric set lean.
Do I still need MangoHud installed?
Yes. MangoHud is a hard prerequisite and does the actual overlay work in game. GOverlay is the control panel that configures it, plus vkBasalt, vkSumi and OptiScaler where installed.
Why does nothing appear in my Flatpak games?
Almost always the sandbox. The layers must be installed as Flatpak Vulkan-layer extensions matching the runtime branch your game uses; a host-side configurator cannot place them inside the sandbox for you.
Can I mix GOverlay with hand-edited configs?
Yes, because both edit the same files. Just avoid changing the same settings in both places at once, since whichever saves last wins, and keep a copy of a config you like before experimenting.
Final verdict
GOverlay is the friendliest way into the Linux overlay stack: it turns cryptic config files into a visual control panel with a live preview, per-game profiles and a launch command that simply works. It adds no magic and no performance, and is honest about that by design. If you use MangoHud on desktop Linux, GOverlay earns its place; if you live in a text editor already, it politely has nothing to sell you.










