What SteelSeries GG does well
GG's Engine module is solid for hardware-level configuration. You can set CPI stages, adjust lift-off distance, configure acceleration curves, change polling rate, and manage onboard memory profiles. For RGB lighting, Engine gives you full control over per-key and per-zone effects, including reactive lighting that responds to in-game events through SteelSeries GameSense. These features require direct communication with the mouse's firmware, and only SteelSeries software can do that.
GG also supports per-game profiles that activate automatically when a linked game launches. For SteelSeries users who want different CPI settings and lighting per game, this integration works well. Macro recording is available through Engine, with the ability to record sequences and edit delays after the fact.
Sonar, the audio module, is a genuine differentiator. It provides parametric EQ, spatial audio processing, and separate audio streams for game, chat, and media. For headset users, it adds real value. Moments captures gameplay clips in the background for sharing. Both features go well beyond what you'd expect from peripheral configuration software.
Where GG becomes a problem
The issue with GG is that all three modules run together as a single application. You can't install just Engine for mouse remapping without also installing Sonar and Moments. Even if you disable Sonar and Moments, GG's background processes still consume more resources than a simple peripheral manager should.
CPU and memory usage
Reports of high CPU usage from SteelSeries GG are widespread across Reddit, SteelSeries' own support forums, and Steam community discussions. The GG Core process has been reported consuming significant CPU cycles even when idle. Sonar's real-time audio processing is the heaviest contributor, but Engine's polling of peripherals for status updates adds overhead too. Users on the SteelSeries subreddit and Microsoft Q&A forums have documented cases where GG's processes contribute to measurable frame rate drops during gaming sessions.
System crashes
The Sonar module in particular has been linked to system instability. Users on Microsoft's support forums have documented repeated hard reboots triggered by kernel-level errors traced back to SteelSeries GG's audio driver components. These aren't application crashes where GG freezes and you restart it. They're full system reboots with no warning, logged as Kernel-Power Event ID 41 errors in Windows Event Viewer. The issue has been reported across different hardware configurations and Windows versions.
SteelSeries hardware only
GG only works with SteelSeries devices. If you switch to a different mouse brand, or if you use a SteelSeries mouse at work and a different brand at home, your button mappings don't follow you. Your configuration is locked to both the software and the hardware.
What MouseKey does differently
MouseKey is a lightweight Windows app that remaps mouse buttons at the operating system level. It doesn't communicate with your mouse's hardware at all. It intercepts input through Windows APIs after the mouse sends its signal, which means it works with any mouse from any brand, including SteelSeries mice.
Where GG assigns one action per button, MouseKey uses click cadences to assign up to 6 actions per button: a different shortcut for 1x, 2x, 3x, 4x, and 5x clicks, plus a 2-second hold. A SteelSeries mouse with 2 side buttons gets 2 programmable actions through GG. Through MouseKey, the same two buttons get up to 12.
MouseKey also includes a timed macro recorder, automatic profile switching based on the foreground application, typed string playback for commands like git status or email templates, and button reassignment.
Side by side comparison
| MouseKey | SteelSeries GG | |
|---|---|---|
| Works with any mouse brand | ✓ Yes | ✗ SteelSeries only |
| Multi-click cadence actions | ✓ Up to 6 per button | ✗ 1 per button |
| Auto profile switching (per app) | ✓ Any application | ✓ Game launch only |
| Timed macro recording | ✓ Yes | ✓ Yes |
| Typed string playback | ✓ Yes | ✗ No |
| CPI / sensor configuration | ✗ No | ✓ Yes |
| RGB lighting control | ✗ No | ✓ Yes |
| Audio processing (EQ, spatial) | ✗ No | ✓ Yes (Sonar) |
| Gameplay clip capture | ✗ No | ✓ Yes (Moments) |
| Resource usage | ✓ Minimal | Heavy (3 modules) |
| Account required | ✓ No account | ✗ SteelSeries account |
| Network access required | ✓ Fully offline | ✗ Online features |
When you still need GG
If you use any of these features, you need GG because no other software can provide them for SteelSeries hardware:
- CPI stages and sensor settings: Polling rate, lift-off distance, acceleration, angle snapping. These are written to the mouse's onboard memory.
- RGB lighting: Per-zone colors, effects, reactive lighting, GameSense integration.
- Onboard memory management: Saving profiles directly to the mouse so they work without software running.
- Sonar audio processing: Parametric EQ, spatial sound, separate audio streams. There's no equivalent from MouseKey or any other mouse remapping tool.
These features require direct communication with SteelSeries firmware. MouseKey doesn't do any of that, and it doesn't try to.
When you don't need GG
If your primary use for GG is assigning keyboard shortcuts to mouse buttons, recording macros, or remapping button functions, none of that requires hardware-level communication. It can all be done at the operating system level by intercepting mouse input before it reaches your applications. Your mouse doesn't need to know about it.
This means you can uninstall GG entirely and handle all of your button remapping through MouseKey. Or, if you want to keep GG for CPI and lighting but want more remapping power, you can run both side by side. Use GG for the hardware settings and MouseKey for your actual button shortcuts. If GG crashes or gets uninstalled, your button mappings through MouseKey keep working because they don't depend on GG.
Switching from another brand's software? See how MouseKey compares to Logitech G Hub, Razer Synapse, X-Mouse Button Control, AutoHotkey, and PowerToys.
The stability difference
GG runs three modules (Engine, Sonar, Moments) with multiple background services, kernel-level audio drivers, and network connectivity for account sync and updates. MouseKey runs as a single lightweight app in the system tray with no background services, no kernel drivers, no network access, and no account. The difference in what can go wrong is significant.
MouseKey doesn't auto-update and break your configuration. It doesn't install audio drivers that can trigger system crashes. It doesn't consume CPU cycles polling your hardware for status updates. It intercepts mouse input at the Windows API level, translates it to the action you configured, and that's it.
Setting up MouseKey on a SteelSeries mouse
MouseKey treats SteelSeries mice the same as any other brand. Install from the Microsoft Store, click + to add a button slot, press the mouse button you want to configure, and assign an action. The entire setup takes under a minute. Your existing GG button mappings won't transfer automatically since they're stored in GG's own format, but recreating them in MouseKey is fast.
What 6 actions per button looks like on a SteelSeries mouse
Take a SteelSeries Rival 5, for example. It has 9 buttons. Through GG, each button gets one action. Through MouseKey, each of those 9 buttons can have up to 6 actions using click cadences. That's 54 possible shortcuts on the same hardware, compared to 9 through GG.
Even on a simpler mouse like the Rival 3 with its two side buttons, click cadences give you 12 programmable actions across those two buttons. Add the middle click and you're at 18. GG would give you 3. The math is the same regardless of SteelSeries model: MouseKey multiplies every button by 6.
Here's a practical example for the two side buttons on any SteelSeries mouse.
Back button: 1x Copy, 2x Paste, 3x Undo, 4x Screen Snip, 5x Mute Audio, hold: Show Desktop.
Forward button: 1x Close Tab, 2x Reopen Tab, 3x Next Desktop, 4x Task View, hold: Lock Screen.
That's 11 shortcuts on 2 buttons. Through GG, those same 2 buttons could do Copy and Close Tab. Everything else would require reaching for the keyboard.
Running MouseKey alongside GG
If you want to keep GG for CPI, lighting, or Sonar, you can run it alongside MouseKey without conflict. The two apps operate at different levels. GG communicates with your SteelSeries hardware's firmware for sensor and lighting configuration. MouseKey intercepts input at the Windows API level after the mouse has already sent its signal. They don't interfere with each other.
The practical benefit of running both is resilience. If GG crashes, updates, or gets uninstalled, your CPI might reset to its default and your lighting goes off, but every button mapping you configured in MouseKey keeps working. Your shortcuts survive GG instability because they never depended on GG in the first place.
If you decide to drop GG entirely, the only things you lose are the hardware-level features: CPI stages, lighting, onboard memory, and Sonar. Your mouse still works at the system level with Windows default CPI settings, and MouseKey handles all the button remapping.
Profile switching: GG vs MouseKey
Both GG and MouseKey support per-app profiles, but they work differently. GG's profiles activate when a linked game launches. This is handled at the application level and works reliably for games, but it only triggers on full application launches, not on window focus changes. If you Alt+Tab out of a game and into a browser, GG doesn't automatically switch to a different profile.
MouseKey monitors the foreground window continuously. Click into Photoshop and your Photoshop profile activates. Click into a browser and your general profile comes back. Click into a game and your gaming shortcuts are ready. The switching is instant and happens on every window focus change, not just on application launch. For users who switch between applications frequently, this is a meaningful difference. See the per-app profiles guide for setup details.
Making the switch
If you're currently using GG for button remapping, here's the practical path to switching. Start by writing down your current GG button assignments. Open GG, go to your mouse's configuration in Engine, and note which button maps to which shortcut. You'll recreate these in MouseKey.
Install MouseKey from the Microsoft Store. Add your first button slot, select the button, and assign the same shortcut you had in GG. Once you've replicated your existing mappings, start experimenting with click cadences to add the extra shortcuts that GG couldn't support. Most users end up with 3 to 4 times as many actions per button within the first week.
If you're keeping GG for CPI and lighting, you can disable GG's button remapping for the buttons you've moved to MouseKey. This avoids any possibility of both apps trying to act on the same button press. If you're dropping GG entirely, just uninstall it. MouseKey doesn't need GG installed to work.
For game-specific setups, check the gaming shortcuts guide. If you're dealing with games that don't recognize your side buttons, that's a separate issue with a separate fix.
Get MouseKey
Mouse button remapping without the overhead. 6 actions per button, any mouse, zero background services.
