SteelSeries Macro Editor: Create and Assign Macros

VBA & macros · Updated November 22, 2026

To use the SteelSeries Macro Editor, open SteelSeries GG, select a compatible device in Engine, choose a key or button, assign a Macro action, then record and save the inputs you want it to perform. You will need SteelSeries GG installed and your supported keyboard or mouse connected. The exact labels can vary slightly between GG versions and devices, but the basic process is to create a macro, attach it to a control, and test it in a safe app before relying on it.

What You’ll Need

  • A SteelSeries keyboard or mouse that supports key or button remapping and macros. Options differ by model; if the device does not appear in Engine or has no macro action, check its product specifications.
  • SteelSeries GG installed on your computer. Download it from SteelSeries and use the version supported by your operating system and device.
  • The target device connected and recognized by GG. A wired connection can make initial setup and troubleshooting simpler.
  • A clear sequence to record, including which keys or buttons it should press and any pauses needed between actions.

Step-by-Step

  1. Open GG and check the device. Start SteelSeries GG and open Engine. Find your keyboard or mouse in the device list and select it. If it is missing, reconnect it, try another USB port, and check for a device or software update before continuing. Some SteelSeries products do not support every Engine feature, so the controls shown depend on your model.
  2. Choose the configuration you want to edit. If your device has configurations or profiles, select the one that should contain the macro. A configuration can be associated with a particular app or use case, depending on the device and GG version. Check that you are editing the intended configuration; otherwise, the macro may appear to vanish when you switch profiles. If you only see one configuration, continue with that one.
  3. Select the key or mouse button to remap. Open the device’s key-binding or button-binding view, then select the control you want to use as the macro trigger. Choose a control you can reach comfortably and that will not replace a critical key you still need. On some devices, the software shows a diagram; on others, you may choose a control from a list. Look for the selected control’s action menu.
  4. Choose the Macro action and open its editor. In the selected control’s action menu, choose Macro or the equivalent macro assignment. Depending on the GG release, you may be able to create a macro there or select an existing one and open Macro Editor. If the editor offers a choice to create a new macro, use it so the recording does not overwrite another saved sequence. Give the macro a descriptive name, such as “Open map” or “Text shortcut.”
  5. Set up how the macro will record. Before pressing Record, check whether the editor has a setting for recording delays. With delays enabled, pauses between your inputs can be captured; with them disabled, the sequence may play back more quickly. Use delays when timing matters, such as allowing a menu to open before the next key. If the editor offers input-type or recording options, choose only the key or button inputs you actually need. Available options vary by software version and device.
  6. Record a short sequence. Start recording, press the intended keys or buttons in the correct order, and stop recording when the sequence is complete. Avoid extra presses while the recorder is active: they may become part of the macro. If you need a pause, use the editor’s delay control if available, or record the pause only when the recording settings capture delays. Keep a first test simple, for example, a few harmless text characters in a text editor.
  7. Review and edit the recorded events. Inspect the event list before saving. Check that each input is present, in order, and not duplicated. Remove accidental events and adjust delays using the editor’s controls if they are available. Some versions let you add, delete, or change events directly; others provide more limited editing, in which case it may be quicker to clear the recording and record it again. Do not assume the editor can record every kind of mouse movement or system action; its supported event types depend on GG and the device.
  8. Save the macro and assign it. Save or confirm the recording, then make sure the macro is assigned to the key or button you chose. If a playback setting is shown, choose the behavior that fits: a single run is suitable for a short action; a repeat or hold behavior is only appropriate when you intentionally need repeated input. The names and available playback modes vary. Confirm the assignment in the device view, and save or apply the configuration if the interface presents that option.
  9. Test it outside a sensitive task. Open a harmless destination, such as a blank text editor, and press the assigned control once. Check that the macro starts, runs in the right order, and stops as expected. If the sequence is intended for a particular application, test it there only after checking the app’s rules and choosing a low-risk setting. Return to Engine to correct timing, remove unwanted events, or change the trigger if the result is wrong.

Common Mistakes

  • Recording before selecting the correct configuration. The macro may be saved to a different profile than the one currently active. Verify the selected configuration before editing and test again after switching profiles.
  • Leaving the recorder running too long. Extra keystrokes, clicks, or pauses can be captured. Start only when ready, stop immediately after the final intended input, and review the event list before saving.
  • Expecting the macro to behave like a program or script. A macro generally replays supported input events; it does not necessarily detect what is on screen, make decisions, or adapt to a changing application state. Include sensible delays and test each step in the actual workflow.
  • Choosing the wrong playback behavior. A repeated macro can send inputs over and over, while a one-shot macro may not repeat when you expect. Start with a single run and change playback only if the device and task require it.
  • Binding over a useful control. Assigning a macro to a key you use frequently can interfere with normal typing or gameplay. Choose a spare control and make sure you know how to restore its original action.
  • Assuming a saved macro works in every app or on every computer. The assignment may be tied to a device configuration, and behavior can differ across applications. Some devices also have onboard settings or memory limitations; check your model’s documentation rather than assuming every configuration transfers.

Tips

  • Use names that explain both the purpose and, when useful, the app or profile, such as “Editor – insert date.” Descriptive names make it easier to select the right macro later.
  • Build and test one short macro before recording a long chain. A small test reveals whether the trigger, recording, timing, and playback behavior are correct without requiring a lengthy edit.
  • Use delays where an application needs time to respond, such as opening a menu or changing focus. Keep them as short as reliability allows; overly long waits make the macro feel sluggish, while no pause can make later inputs arrive too soon.
  • Save a copy of the original key assignment or note it before replacing it. If the macro is inconvenient, you can restore the previous action without having to guess what it was.
  • Test repeat or toggle modes cautiously. If a sequence can repeat, know how to stop it before testing, and avoid assigning it to a key that could be held accidentally.
  • For a macro that enters text, confirm the active window and keyboard layout first. A sequence recorded on one layout or in one application may produce unexpected characters or go to the wrong field elsewhere.
  • Keep macros within the rules of the software or game where you plan to use them. Some services restrict automation or repeated inputs, even when the sequence is created with a device’s official software.

Troubleshooting

The device does not appear in Engine: reconnect it and check the USB port or cable. Close and reopen GG, then check for software and device updates. If the device still is not listed, confirm that your exact model is supported by the installed GG version; a general SteelSeries brand match does not guarantee that every feature is available.

There is no Macro option: select the device itself and a remappable key or button, not an unrelated settings page. Check that you are using the correct device configuration and that GG is up to date. If the action remains unavailable, the model or selected control may not support macros. Consult the model’s support page rather than following instructions meant for a different keyboard or mouse.

The macro records nothing: make sure recording has actually started and that you are pressing supported keys or buttons. Stop the recording and inspect its event list. If it is empty, try a very short sequence and check any record-delay or input options. Restart GG if the editor appears unresponsive, then try again.

The macro triggers but misses inputs or runs too quickly: edit the event order and add or increase delays between actions where the editor allows it. Test in the target application because a slow-loading menu or changing focus can affect timing. If an input still fails, simplify the sequence to identify which event is causing the issue.

The macro works only sometimes or stops after changing apps: check which configuration is active and whether the macro is assigned in that configuration. Confirm that the intended application is in focus and that another binding is not using the same trigger. If the macro is set to repeat or toggle, verify its stop behavior and switch temporarily to a single run to isolate the problem.

Changes do not seem to save: return to the device view and check the selected macro and configuration. Use any Save or Apply control shown by your GG version, and allow synchronization to finish before unplugging the device. If the assignment disappears after reconnecting, check whether your model stores that setting onboard or relies on GG running in the background.

Frequently Asked Questions

Is SteelSeries Macro Editor part of SteelSeries GG?
Yes. Macro creation and assignment are handled through Engine in SteelSeries GG for supported devices. The exact editor location and available options can vary by device and software version.

Can I use a macro on any SteelSeries keyboard or mouse?
No. Support depends on the model and the control you are trying to remap. If Engine does not offer a macro action for that control, check the device specifications and support information.

Can the macro include delays?
Often, the editor provides a way to capture or adjust timing, but the controls differ between versions. Check the recording settings and event list. Add pauses when the next input depends on an application having time to respond.

Does the macro run when SteelSeries GG is closed?
That depends on the device and how its settings are stored. Some configurations may require GG or its related background components, while device capabilities differ. Check the documentation for your model and test after restarting the computer before relying on it.

Can a macro repeat while I hold the assigned key?
Some devices or software versions offer repeat-style playback, but not all do. If available, read the mode description and test cautiously; repeated input can have unintended effects. Use a single-run mode unless repetition is specifically needed.

Why does a macro type different characters than expected?
Keyboard layout, application focus, and the way a sequence is recorded can change the result. Check the active input language and target field, then record and test the sequence in the same conditions where you plan to use it.

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.