G-Helper: A Single-EXE Armoury Crate Alternative With BIOS Modes, GPU Switching and an In-Game Overlay
Lightweight Armoury Crate alternative for Asus laptops with nearly the same functionality. Works with ROG Zephyrus, Flow, TUF, Strix, Scar, ProArt, Vivobook, Zenbook, Expertbook, ROG Ally, and more.
At a glance
- What is it?
- G-Helper is a C# Windows tool for Asus laptops that exposes performance modes, GPU modes, fan curves, charge limits and BIOS update checks from one executable. It is Asus-specific, tied to what each model's BIOS supports, and releases roughly every few days.
- Who is it for?
- G-Helper is the sensible choice for owners of Asus laptops who want Armoury Crate's performance modes, fan curves and GPU switching without a heavy install. It is useless on non-Asus hardware, several features such as Ultimate GPU mode depend on your model's generation, and its 0.2xx version numbers with new builds every few days mean you should read the wiki troubleshooting page before changing power limits.
- 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 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 November 15, 2026, and from our analysis. They are not legal advice.
Star history
- seerge/g-helper16,059 ★ · +762
| Repository | 2026-09-21 | 2026-11-15 |
|---|---|---|
| seerge/g-helper | 15.3k | 16.1k |
762 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One executable that installs nothing, with the model-specific details left to the wiki
G-Helper is pitched as a small, lightweight Armoury Crate alternative for Asus laptops offering almost the same functionality with a much smaller footprint. The download is a single file, GHelper.exe, taken from the latest GitHub release. The listed advantages say it is a single exe to run and that it does not install anything in your system. Its interface is described as a simple, clean native UI with easy access to all settings.
The supported hardware range is wide: ROG Zephyrus G14, G15, G16, M16, X13, X16, Z13 and DUO, TUF series, Strix and Scar series, ProArt, Vivobook, Zenbook, Expertbook, ROG Ally and Ally X, and more. That list is a statement about families, not a guarantee for a specific model number. What differs between models is spread across four wiki pages the README links: FAQ, Setup and Requirements, Troubleshooting and Power User Settings.
The practical consequence is that the feature list below is a ceiling. A given laptop may not have every item, because the controls come from what that model's firmware exposes. Read the Requirements page for your machine first, and treat a missing toggle as a hardware or firmware limit before assuming a bug. The tool also targets Asus devices only, so it has nothing to offer on another brand.
Silent, Balanced and Turbo are the same BIOS modes Armoury Crate uses
A note in the README makes a specific claim: all modes are baked into the BIOS along with default fan curves and power limits, and they are the same thing as in Armoury Crate. G-Helper is therefore a different front end for firmware modes your laptop already has, rather than a separate performance engine.
Each BIOS mode is paired with a Windows Power Mode, which you can adjust under Fans + Power. Silent in BIOS pairs with the Best power efficiency power mode. Balanced, which is called Performance when on AC power, pairs with the Balanced power mode. Turbo pairs with Best performance.
On top of those defaults, the tool lets every performance mode be fully customised: power limits, a custom fan curve editor and turbo boost selection are available per mode. That is the main reason to use it over the stock settings, and also where responsibility shifts to you. A fan curve that runs quiet will run hot under load, and raised power limits can push temperatures and battery drain upward. The README gives default curves as a starting point but does not publish safe values per model, so adjust in small steps and watch the temperature monitor, which shows CPU and GPU temperature, fan speeds and battery status.
Four GPU modes decide which GPU drives the built-in display
The GPU switching options are defined precisely. Eco enables only the low power integrated GPU, which drives the built-in display. Standard, described as MS Hybrid, enables both the iGPU and the dGPU while the iGPU still drives the built-in display. Ultimate also enables both, but the dGPU drives the built-in display, and the README says this is supported on 2022 and newer models. Optimized disables the dGPU on battery, which is Eco, and enables it when plugged in, which is Standard.
The first advantage listed is seamless and automatic GPU switching, and the Optimized mode is the automation behind it. The consequences are concrete. In Eco, anything that needs the dedicated GPU will not have it, so a game or a render job started on battery will run on the integrated chip. Ultimate offers the direct dGPU path to the screen, but if your laptop predates 2022, the option is not expected to work.
Switching modes can require attention from the system, since the display path changes, so save your work before changing it. The tool also covers screen refresh rate control with display overdrive, a mini-LED multi-zone switch, and flicker-free dimming with Visual Modes, which are relevant mainly on models that have those panels.
Automation reacts to the power cable, not to what you are running
A short list of automation rules covers the common laptop pattern. Performance mode can switch when on battery or plugged in. The Optimized GPU mode disables the dGPU on battery and enables it when plugged in. Screen refresh rate can go automatic, at 60Hz on battery and the maximum Hz when plugged in. The keyboard backlight timeout can differ on battery and on AC.
All four triggers depend on power state. None of them looks at the application in the foreground. If you are rendering on battery, the Optimized GPU mode will still have disabled the dGPU, and the refresh rate will still have dropped to 60Hz, because the rule only sees that the cable is out.
That is a reasonable default for battery life and a trap for people who work unplugged. The fix is to choose a fixed GPU mode, such as Standard, when you want the dedicated GPU on battery. The README does not describe per-application rules, so a workflow that needs different behaviour per program has to be handled by switching modes yourself or with the hotkeys. FN-Lock and custom hotkeys are part of the feature list, and a charge limit is available to preserve battery health.
Overclocking, undervolting and power limits reach into hardware you can destabilise
Beyond mode switching, G-Helper offers tuning controls. In each mode the dedicated GPU can be tuned with Core and Memory Clock offsets, GPU power, Dynamic Boost and Temperature Limit. The feature list adds NVIDIA GPU overclocking and undervolting, and AMD CPU undervolting and temperature limits. There is XG Mobile control for supported docks, plus the performance mode power limits and turbo boost choices.
These are the settings with real downside. An undervolt that is too aggressive can crash a game or freeze the machine, and raising power limits increases heat. The README offers the controls and does not list tested values for any laptop, so there are no recommended numbers to copy. Start with small changes, one setting at a time, and test under the workload you care about.
Availability also varies. AMD CPU undervolting only makes sense on AMD processors and the NVIDIA tuning only on machines with an NVIDIA dGPU. The Power User Settings wiki page is where the more advanced options are documented, so read it before experimenting. Changes are applied per performance mode, which means a stable tweak in Balanced may not carry over to Turbo, and each mode needs its own testing.
The metrics overlay works in DX10 and newer games but not in exclusive full screen
G-Helper includes a built-in in-game overlay that shows live FPS, CPU and GPU temperatures, usage and power on top of your game, with no extra tools needed. It works in DX10 and newer games, and may not be visible over old titles that use exclusive full-screen mode. The fix the README gives is to set the game to windowed or borderless full-screen mode.
The overlay is controlled entirely by keyboard and mouse combinations on Ctrl, Shift and Alt. `Ctrl + Shift + Alt + O` toggles it on and off. Holding the same modifiers while dragging with the mouse moves it, clicking switches mode among Light, Default, Full and Complete, scrolling the wheel resizes it, and a wheel click resets the size.
Three practical points follow. The shortcut needs three modifier keys, so a keyboard layout or game binding that uses the same chord will clash with it. The overlay is only as accurate as the sensors the laptop exposes, which depends on the model. And because it is an OSD drawn over the game, anti-cheat systems in online titles may treat overlays with suspicion, a point the README does not address, so check a game's rules before leaving it on.
Update checks come from Asus servers, peripherals are limited to a list, and builds arrive every few days
The app includes an automatic BIOS and driver update checker. It pulls directly from the official Asus website for your specific model, highlights new downloads as they become available, and every link in the Updates section points to official Asus downloads. So the tool finds updates and links to them, rather than hosting files itself. Apply a BIOS update with the usual care, since a failed flash can brick a laptop.
Peripheral support covers Asus mice rather than a general class. The supported list on a linked discussion includes ROG Chakram, Gladius II and III, Harpe Ace variants, Keris, Pugio, Spatha X and Strix models, among others. A mouse that is not listed has no controls here. Lighting support covers Anime Matrix or Slash Lighting, including animated GIFs, a clock and an audio visualizer, and RGB backlight animation modes and colours.
The project is GPL-3.0 licensed, and the latest releases are v0.289 on 2026-10-20, v0.290 on 2026-10-24 and v0.291 on 2026-11-02, with the last push on the same day. Version numbers below 1.0 and a new build every few days mean fixes arrive quickly and behaviour can change, so keep the Troubleshooting page open after updating. The README also links translations in Chinese, Japanese, Czech, Spanish and Korean.
Editorial conclusion
G-Helper is the sensible choice for owners of Asus laptops who want Armoury Crate's performance modes, fan curves and GPU switching without a heavy install. It is useless on non-Asus hardware, several features such as Ultimate GPU mode depend on your model's generation, and its 0.2xx version numbers with new builds every few days mean you should read the wiki troubleshooting page before changing power limits.
Frequently asked questions
What is G-Helper?
G-Helper is a lightweight Armoury Crate alternative for Asus laptops. It is a single exe that does not install anything and offers performance modes, GPU modes, fan curves and other controls.
Is G-Helper only for Asus laptops?
Yes. It is described as a control tool for Asus laptops, covering ROG Zephyrus, Flow, TUF, Strix, Scar, ProArt, Vivobook, Zenbook, Expertbook and ROG Ally models.
How do I install G-Helper?
Download GHelper.exe from the latest GitHub release and run it. It is a single exe that does not install anything in your system.
Can G-Helper update the BIOS?
It includes a BIOS and driver update checker that pulls from the official Asus website for your specific model and links to official Asus downloads.
Official sources
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.
[](https://hysenlabs.com/projects/seerge-g-helper)Star history chart for your README
[](https://hysenlabs.com/projects/seerge-g-helper)Was this useful?