SteelSeries Macro: How to Add and Assign One in GG

VBA & macros · Updated November 22, 2026

To add a macro in SteelSeries GG, open GG > Engine, select your connected device, choose the key or button to customize, and assign a new macro from its binding options. Record or edit the actions, save the macro, and test it in a safe app before using it in a game. You will need a SteelSeries device supported by Engine and the SteelSeries GG software; available controls can vary by device and software version.

What You’ll Need

  • A SteelSeries keyboard, mouse, or other peripheral that appears in the GG Engine section and supports custom bindings. Not every model supports macros or lets you assign them to every control.
  • SteelSeries GG installed on your Windows PC or Mac. Download it from the official SteelSeries website, install it, and allow the application to update if prompted.
  • The device connected to the computer. Use a direct USB connection for setup if a wireless device is not detected, and make sure its battery is charged.
  • A clear plan for the macro: the keys or clicks it should send, their order, and whether it should run once or repeat. Check the rules of any game or app where you plan to use it.

Step-by-Step

  1. Open SteelSeries GG and check Engine. Start GG and select Engine from the navigation. Wait for the device list to load. If your peripheral does not appear, reconnect it, try another USB port, and check for a GG or device firmware update before continuing.
  2. Choose the device and configuration. Click the keyboard or mouse you want to configure. If the device offers multiple configurations or profiles, select the one you want to edit. A configuration is the set of assignments and settings that applies in a particular profile; changing one profile may not change the others.
  3. Open the control’s binding menu. In the device layout, select the key or mouse button where you want the macro to run. The control’s assignment panel or dropdown should appear. Look for a binding type named Macro, Macros, or similar. Names and layout can differ between device models and GG releases. If you cannot select the control or do not see a macro option, check that the device supports programmable bindings.
  4. Create a new macro. Choose the option to make a new macro, such as New Macro or Create Macro, in the binding panel or macro editor. Give it a descriptive name, for example Type greeting or Open map. A useful name makes it easier to distinguish several macros later.
  5. Record the actions in order. In the macro editor, start recording, enter the desired keystrokes or button actions, and stop recording when the sequence is complete. For example, a simple text macro could record the keys needed to enter a short phrase. A shortcut macro could record the modifier keys and letter in the order the target application expects. Use the editor’s own record and stop controls rather than typing into unrelated fields.
  6. Review delays and recorded events. If the editor offers a record-delays option, decide whether to preserve the pauses between actions. Recorded pauses can make a sequence behave more like deliberate typing, but they also make it slower. Remove accidental keystrokes, unnecessary waits, or duplicate events using the editor’s event list or editing controls. If the macro relies on a key being held, confirm that the editor represents the press and release correctly.
  7. Choose how it plays back. Select the playback behavior that suits the task, if your device and GG version offer the choice. Play once is suitable for a short, finite sequence. Repeat while pressed repeats while you hold the assigned control, while a Toggle option may continue after one press until you press again. Read the displayed behavior carefully: a repeating macro can continue sending inputs when you do not expect it.
  8. Save the macro and assign it. Save or confirm the macro in the editor. Return to the selected key or button’s binding menu and choose the macro you just created. Some versions assign it as part of the creation flow; others require selecting it from the macro list afterward. Confirm that the control now displays the macro name or macro binding rather than its previous action.
  9. Apply the configuration and test. Save or apply the device configuration if a button is shown. Open a harmless text editor or another safe test app and press the assigned control once. Check that the correct actions occur, in the right order, and only as many times as intended. If the device uses profiles, confirm that the active profile is the one you edited before testing in your target app.
  10. Adjust and retest if needed. If the sequence is too fast, too slow, or contains an unwanted action, reopen the macro editor, change the events or delays, save again, and test again. Change one thing at a time so you can identify which adjustment fixed the behavior. Do not test an uncertain repeating macro in a live game or in a field where it could submit or delete data.

Common Mistakes

  • Editing the wrong profile. A macro can appear missing when you switch to another device configuration or application profile. Check the active profile before changing the binding, and test with that same profile active.
  • Creating a macro but not binding it. Saving a sequence does not always assign it to a key. Return to the chosen control and select the saved macro from the binding menu.
  • Recording the wrong input. Clicking another window, pressing a setup shortcut, or typing extra characters during recording can add unwanted events. Stop recording promptly, inspect the event list, and remove anything that should not be part of the sequence.
  • Using repeat or toggle without checking the result. A loop can send a key or click many times. Start with play-once behavior where possible, then try repetition only after confirming how it stops.
  • Expecting every SteelSeries device to offer identical controls. Engine options depend on the model, firmware, operating system, and GG version. A feature shown for one keyboard or mouse may not be available on another.
  • Ignoring an app’s rules or focus. A macro sends input to the active app; it does not guarantee that the intended window or field is selected. Some games and services also restrict macros, especially those that automate gameplay.

Tips

  • Use a short, specific name. Names such as Paste support reply are easier to recognize than Macro 1, particularly if you keep separate macros for work and gaming.
  • Keep sequences as simple as possible. A macro with only the required actions is easier to test and less likely to send an unwanted command. For a complicated workflow, consider whether the target application has a built-in shortcut or automation feature instead.
  • Use delays intentionally. A small pause can help an application process one action before the next, but there is no universal delay that works everywhere. Test with the actual app and increase pauses only when the sequence is being missed or mistimed.
  • Save a backup or note the original binding. Before replacing a useful key assignment, record what it did or take a screenshot of the configuration. That makes it easier to restore the control if the macro is not convenient.
  • Test both the trigger and the sequence. Check that the chosen key is comfortable to press, does not conflict with a control you use often, and runs only once per intended activation. Then confirm the macro’s individual actions.
  • Check whether GG must remain open. Some device settings may be stored or supported differently depending on the model. If the macro works only while GG is running, consult the device’s Engine options and product documentation to see whether that model supports onboard profiles or requires the software.
  • Respect software and game policies. Do not use a macro to bypass protections or automate activity prohibited by a game’s or service’s terms. If unsure, check the relevant rules before assigning or using it.

Troubleshooting

  • Your device is missing from Engine: Disconnect and reconnect it, try a different USB port or cable, and restart GG. For a wireless device, check its charge and receiver connection. Install any available GG or firmware update, then reopen Engine. If the model still does not appear, confirm that it is supported by SteelSeries GG rather than an older or different configuration utility.
  • There is no Macro option: Select a programmable key or button rather than a control with a fixed function. Check the product specifications and update GG. Some devices or particular controls do not support macro assignment, so there may not be a software setting to enable it.
  • The macro is not listed after recording: Make sure you saved or confirmed it in the editor, then reopen the binding menu and check the macro list. If the list is still empty, close and reopen Engine, verify the correct device and configuration are selected, and create a short test macro to see whether saving works.
  • The assigned control does nothing: Confirm that the intended configuration is active and that the binding panel shows the macro name. Test the key in a plain text editor, check that the target app has focus, and verify that the macro is not assigned to a different device or profile. If the key itself has a hardware lock or special function, test another programmable control.
  • Only some actions register: Edit the sequence to remove unnecessary events, add or adjust pauses if the target app needs time between inputs, and verify the press-and-release events. Test the revised macro in a simple app before using it elsewhere. Some applications ignore simulated input or handle shortcuts differently, so a macro may not work in every program.
  • The macro repeats or stops unexpectedly: Return to playback settings and select play once for a one-time action. For repeat or toggle modes, check the displayed stop behavior and test it in a safe app. Reassign the macro or restart GG if the setting appears not to update after saving.
  • It works only while GG is running: Check the device documentation for onboard profile or memory support. Not all peripherals can store every Engine setting on the device. If onboard storage is not supported for that feature, keep GG running and ensure the correct configuration is active.

Frequently Asked Questions

Can I add a macro to any SteelSeries keyboard or mouse?

No. Macro support and the controls you can assign vary by model. Look for the device in GG Engine and check its product documentation if the macro binding option is missing.

Can a SteelSeries macro type text?

A keyboard macro can record keystrokes that produce text, but its result depends on the keyboard layout, active application, and text field. Test it in a plain text editor first, especially if the text includes symbols or uses a different keyboard layout.

Can I make a macro repeat while I hold a key?

If your device and GG version provide a repeat-while-pressed playback mode, select it in the macro settings. Test how it starts and stops before using it in an app, and avoid repeat behavior when one activation should send only one sequence.

Do I need to leave SteelSeries GG open?

It depends on the device and whether it can store the relevant profile or macro onboard. Check the device’s Engine settings and documentation. If the assignment stops working when GG closes, run GG and select the correct profile.

Why does my macro work in a text editor but not in a game?

Games may handle input differently, ignore simulated keystrokes, or restrict macros under their rules. Check the game’s policy and test only in a permitted setting. Do not try to defeat anti-cheat or other protections.

Can I undo a macro with Ctrl+Z?

Ctrl+Z usually undoes text in an application, not actions already sent by a device macro. Test carefully in a harmless window, and avoid assigning a macro that submits, deletes, or purchases anything until you have verified its sequence.

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.