How to Use Macros in SteelSeries GG

VBA & macros · Updated November 22, 2026

To use a macro in SteelSeries GG, open Engine, select a compatible device, create or record a macro in its key-assignment controls, then assign that macro to a supported key or button and test it. You will need SteelSeries GG, a supported SteelSeries device, and a clear idea of the sequence you want to automate. Menu labels and available macro features can vary by device and GG version.

What You’ll Need

  • A Windows PC or Mac with SteelSeries GG installed and updated.
  • A SteelSeries keyboard, mouse, or other Engine-supported device that exposes macro assignments. Not every model or control supports macros.
  • The intended keystroke sequence, including where pauses are needed and how you want playback to stop.
  • Permission to use the macro in the app or game where you plan to run it. Some games restrict automation, especially in competitive play.

Step-by-Step

  1. Install and open SteelSeries GG. Download GG from SteelSeries’ official site, install it, and launch the app. If GG is already installed, check for updates before troubleshooting a missing option. Connect your device directly or through its normal wireless receiver, switch it on, and give GG time to detect it. In GG, open Engine. Depending on the version, Engine may appear as a tab or section in the app’s navigation.
  2. Select the device and configuration. Click the card for the keyboard or mouse you want to configure. If you have more than one configuration or profile, select the one you intend to use. Profiles may be associated with particular applications, so a macro saved in one profile might not be available when another profile is active. Confirm the device name and profile before making changes.
  3. Open the assignment controls for a key or button. On a keyboard page, select the key in the on-screen layout or open its assignment menu. On a mouse page, select a programmable button. Look for a macro assignment or an option to open the Macro Editor. The wording and location can differ between devices and software versions. If the assignment list has no macro option, check the device’s support information; a firmware update cannot add a feature the model does not support.
  4. Create a new macro. In the macro editor, choose the control to create a new macro or macro recording, then give it a descriptive name such as Open chat and send greeting. Names that explain the action are easier to recognize later than generic labels such as Macro 1. If the editor offers a choice between recording and creating events manually, recording is simplest for a straightforward sequence; manual editing can be useful for adjusting timing.
  5. Record the keystrokes in order. Start recording, enter the keys exactly as you want them sent, and stop recording. For example, a simple text shortcut might be a modifier key plus a letter; a longer example could open a text field, type a short phrase, and press Enter. Use the target application’s expected key order. Avoid typing passwords or private information into a macro: the sequence is stored as an input action and may be visible to anyone with access to the configuration. If the editor records delays, make sure they reflect the pauses you actually need.
  6. Review the event list and timing. Read through the recorded events before saving. Check that each key press has a corresponding release where the editor displays separate press and release events, and remove accidental keystrokes. If the macro types text, confirm punctuation, capitalization, and keyboard layout. Add a short pause after opening a menu or switching focus if the target program needs time to respond. A delay that is too short can make the next key arrive before the application is ready; an unnecessarily long delay makes the macro feel sluggish.
  7. Choose the playback behavior. Select the mode that matches the task. A play-once option is suitable for a single action. A repeat or while-held option, if offered, can run an action as long as you hold the assigned control. A toggle option may continue repeating after one press and stop after another. Labels and available modes vary, so read the editor’s description and test the behavior in a safe place. For a repeat mode, keep the sequence short and make sure you know how to stop it.
  8. Save the macro and assign it. Save or apply the macro in the editor. Then choose it from the assignment menu for your selected key or button, if it was not assigned automatically during creation. Confirm the assignment appears on the device page, and save or apply the device configuration if GG shows a separate control for doing so. Creating a macro and assigning it are separate tasks in some versions: a saved macro in the editor will not run from a key until it has an assigned control.
  9. Test it outside a sensitive task. Open a harmless text field or a test document and press the assigned key once. Check that the correct sequence runs, the timing is usable, and a held or toggled macro stops as expected. For a text macro, verify the result rather than assuming the recorded input matched what you intended. If the action is meant for a particular game or application, test it there only after confirming that the application permits macros. Do not test a repeating action in a live match or a form that could submit important information.
  10. Check profiles and device memory if needed. Switch to the profile you plan to use and verify that the assignment remains available. Some devices can store selected settings in onboard memory; others rely on GG running and the correct profile being active. Do not assume a macro will work on another computer or with GG closed. Consult the device’s specifications and GG’s device page to see which settings can be stored on the device.

Common Mistakes

Making the macro but not assigning it: Saving a recording in the editor does not always bind it to a key. Return to the key or button assignment menu and select the macro by name.

Using the wrong profile: You may have assigned the macro in a desktop profile while an application-specific profile is active. Check the active configuration in Engine and assign the action in the profile that will actually be used.

Recording extra input: A stray click or keystroke during recording becomes part of the sequence. Review the event list and remove unwanted events instead of trying to compensate by recording again without checking.

Choosing an unsuitable repeat mode: A repeating macro can send input repeatedly or continue longer than expected. Use play once for one-off tasks, and test repeat or toggle behavior away from games, messages, and forms where repeated input could cause trouble.

Expecting every button or device to support macros: Macro availability depends on the model, control, and software support. If the assignment menu does not offer the feature, verify compatibility before spending time reinstalling the app.

Tips

Keep macros narrow: one macro should perform one predictable task. A short sequence is easier to edit, test, and stop than a long chain that combines unrelated actions. If a routine involves several steps, make separate macros when your device and workflow allow it.

Use clear names that describe both the task and, where helpful, the intended app. Names such as Browser search or Push-to-talk toggle are more useful than names based on when you made them. If you revise a macro, test the changed version again; a small timing or key-order adjustment can change the result.

Use pauses only where the target software needs time to react, such as after opening a menu or changing focus. Do not add delays to every event without a reason. If the macro misses input, increase the pause around the slow step first, then test again. If it is simply too slow, remove excessive waits one at a time.

Keep the assigned control easy to identify and unlikely to be pressed by accident. Avoid replacing a key you rely on in normal use unless the device offers a convenient way to switch profiles. For a macro that can repeat, choose an assignment you can release or toggle off quickly.

On macOS, the layout and available features may differ from Windows, and some device functions are not supported equally on every platform. Follow the controls shown in your installed GG version rather than relying on a Windows-only guide. If macOS blocks input-related behavior, check for a system permission prompt for GG and review the relevant Privacy & Security settings, granting only permissions needed for the feature.

For games, check the game’s rules and the device maker’s guidance before using automation. A macro that simply sends a permitted shortcut is different from one that automates gameplay or creates an unfair advantage, but the game’s policy decides what is allowed. When uncertain, do not run it in online competitive play.

Troubleshooting

The device does not appear in Engine: Check its cable, receiver, power, and connection, then restart GG. Try a different USB port if appropriate, and install any available GG or device firmware updates through the supported SteelSeries tools. If it still does not appear, verify that the exact model is supported by GG and that you are using the correct software for it.

There is no macro option: Select the device itself, not just a general settings page, and open the assignment menu for a programmable key or button. Some models expose fewer assignments than others. Confirm compatibility and update GG; if the feature remains absent, the device or selected control may not support macro assignment.

The macro is saved but does nothing: Check that it is assigned to the intended control, that the right profile is active, and that the device is connected. Test in a basic text field. If it works there but not in one app, the app may ignore simulated input, require focus, or restrict macros. Check the app’s own settings and rules rather than repeatedly changing the recording.

Keys are missed, repeated, or stuck: Open the event list and check for missing releases, accidental duplicate events, and timing that is too tight. Add a modest pause around the step that fails and test the macro again. If a repeat or toggle sequence is running, use its configured stop action or release the assigned key; if the device stops responding, disconnect and reconnect it or switch profiles, then revise the macro before trying again.

It works only while GG is open: This can be expected if the device does not store that macro in onboard memory or if the active profile depends on the software. Check the model’s onboard-memory capabilities and GG settings. Keep GG running and the correct profile active when required; do not assume a saved macro automatically transfers to another computer.

It behaves differently on a Mac: Confirm that your SteelSeries model and the specific Engine feature are supported on macOS. Check the key layout and the application’s shortcuts, since the same physical key combination may have a different effect. If GG or macOS displays a permission request related to input control, review it in System Settings before allowing access.

Frequently Asked Questions

Can I use macros on any SteelSeries keyboard or mouse?
No. Support depends on the device model, the programmable control, and the GG version. Check the device’s Engine page and specifications for macro assignments.

Can I edit a macro after recording it?
Usually, the editor lets you review and adjust recorded events or timing, but the available editing controls vary. If your version does not expose the edit you need, create a revised recording, then test and assign it.

Can I make a macro repeat while I hold a key?
Use a while-held or repeat playback mode if the editor offers one for your device. Test how it stops before using it in a real task, because the labels and behavior can differ.

Will a macro run when SteelSeries GG is closed?
Not necessarily. That depends on whether the device can store the macro and whether the particular setting is saved to onboard memory. Check your device’s documentation and test after closing GG rather than assuming it will work.

Can I use a macro in a game?
Only if the game’s rules permit it. Some games prohibit automation or limit which actions can be bound to macros. Check the current rules, especially for online or competitive play.

Why does a text macro type the wrong characters?
Check the keyboard layout, capitalization, and recorded press-and-release events. A sequence recorded under one layout or application focus may produce different results elsewhere. Test it in a plain text field and adjust the recording for the intended setup.

Related

Try it: the Column Letter to Number: aA is 27, XFD is 16,384. Converts both ways.

More in VBA & macros

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.