SteelSeries Macro Toggle vs Hold: Setup and Troubleshooting

VBA & macros · Updated November 22, 2026

In SteelSeries GG, a macro set to Toggle typically keeps playing or repeating after you press its assigned key, until you press that key again; Repeat While Pressed runs only while you hold the key down. Choose Toggle for hands-free repeated input and the hold setting for an action that should stop as soon as you release the key, but check the playback options shown for your device and GG version.

What toggle and hold mean

A macro is a saved sequence of input events, such as pressing a key, waiting, and pressing another key. Its playback setting determines what happens after you activate it. The setting changes how long the sequence runs; it does not change the events recorded inside the sequence.

  • Toggle: A press starts playback, and another press of the assigned key stops it. If repeat is enabled, the sequence continues to run between those presses.
  • Repeat While Pressed: The sequence repeats while you keep the assigned key down. Releasing it ends playback.
  • Play Once: The sequence runs one time each time you activate it. This is useful for a fixed sequence that should not loop.

Interface wording and available options can vary between GG releases and devices. In particular, a toggle is not the same as holding a key: after starting a toggled macro, you can release the assigned key and the macro may continue. If you do not see Toggle or Repeat While Pressed, do not assume another option behaves the same way; check the choices available in the macro editor for that device.

Where to find macro controls in GG

SteelSeries GG uses its Engine area to configure supported keyboards, mice, and other devices. The general workflow is to select a device, choose a key or button, assign a macro, and then set its playback behavior. Labels and screen layouts can change with GG updates, so treat these as navigation landmarks rather than a promise that every screen uses identical wording.

  1. Open SteelSeries GG and select Engine.
  2. Choose the connected device you want to configure.
  3. Select the key or mouse button that will trigger the macro. Make sure it is a button you can press safely while the macro is running.
  4. Choose the macro assignment option. Depending on the interface, you may be able to select an existing macro or create one in the macro editor.
  5. Open the macro’s playback or repeat options, choose the behavior you want, and apply or save the configuration.
  6. Test it in a low-risk app, such as a text editor, before using it in a game or other important task.

If the device does not appear in Engine, connect it directly to the computer if possible, check that GG recognizes it, and install any available GG or device updates. Not every SteelSeries product supports every Engine feature, so a missing macro assignment option can be a compatibility limitation rather than a setting you have overlooked.

Creating a macro that repeats

First decide what the macro should do on a single pass. For example, a simple test macro might type the letter A and then wait briefly. A more useful work example could enter a short, fixed sequence in a text field. Record only the inputs you intend to send, and review the sequence for accidental clicks, modifier keys, or long delays before turning on repeat playback.

After creating the sequence, set its playback mode separately. For a hands-free loop, choose Toggle if it is offered and confirm that the macro’s repeat behavior is configured to continue cycling. For a loop that should run only while you hold the assigned button, choose Repeat While Pressed. If the editor shows an option to repeat a macro but not a separate toggle mode, follow the labels in that version of GG; a repeat setting alone does not necessarily mean the macro will stop with a second press.

Start with a short sequence and a modest repeat rate. A loop with no pause can send input very quickly, and some applications respond differently to rapid repeated events. Test the start and stop behavior, confirm that it does not enter text in the wrong window, and only then decide whether to adjust the sequence or timing.

Choosing the right mode for the task

Use Repeat While Pressed when the physical press itself should control the action. A practical example is a temporary, repeated input that should stop immediately when you lift your finger. This mode also makes the activation state easier to understand: if you are not holding the assigned key, the macro should not be continuing under the usual repeat-while-pressed behavior.

Use Toggle when you want to start a repeating sequence and then take your hand off the trigger. For instance, during a harmless desktop test, you might toggle a macro that repeatedly types a character, then press the assigned button again to stop it. The key advantage is convenience, but it also creates a greater chance of forgetting that the macro is still active.

Choose Play Once for a sequence that should happen only once per press, such as entering a short text string or sending a deliberate set of keystrokes. If the sequence itself contains a key-down event without a matching key-up event, or if it switches windows, a one-time macro can still have unintended effects; playback mode is not a substitute for checking the recorded events.

Stopping a running macro safely

With a toggled macro, pressing its assigned trigger again is generally the intended way to turn it off. Keep that trigger accessible and make sure it has not been reassigned or blocked by the application in which you are working. For Repeat While Pressed, releasing the trigger should end playback. A one-time macro normally ends when its recorded sequence finishes.

If a macro appears to keep running, first try its configured stop action in the same app where you started it. Then switch to GG and disable or change the assignment if you need to prevent another start. If necessary, disconnecting the device or quitting GG may interrupt software-driven behavior, but the result depends on how the device and configuration are implemented. Do not rely on an emergency workaround instead of testing the stop control before using a loop.

A useful precaution is to assign a toggle macro to a button that is easy to reach but unlikely to be pressed by accident. Avoid placing the start and stop control somewhere you cannot access while using the target app. When testing, use a blank text document or another harmless destination so an unexpected repeat does not send commands to a work file or active game.

Common problems and practical checks

  • The macro runs only once: Check whether its playback mode is Play Once and whether a repeat option is available. A macro does not automatically loop simply because it contains several events.
  • It stops when you release the button: That behavior is consistent with Repeat While Pressed. Choose Toggle if you want playback to continue after release and the device offers that mode.
  • A second press does not stop it: Confirm that the assigned behavior is actually Toggle, not Repeat While Pressed or Play Once. Also check that the trigger is still assigned to the macro and that the target application is receiving the button.
  • The macro starts but sends unexpected input: Reopen the macro and inspect its event list, delays, and recorded key or mouse actions. Re-recording a short, clean sequence can be easier than diagnosing unwanted events in a long recording.
  • The setting is missing: Confirm the exact device model and its Engine feature support, then check for GG updates. Available assignments can depend on the device and software version.
  • It behaves differently in another app: Test outside that app to distinguish a macro configuration issue from application focus, input handling, permissions, or rules that restrict automated input.

Also check for conflicting assignments. If the same physical key is assigned to a macro in one profile and a different action in another, switching profiles can make the result seem inconsistent. Check which profile is active and whether the device or GG is changing profiles automatically. If you edit a macro while it is assigned in multiple places, verify each assignment rather than assuming every profile uses the same playback mode.

GG running, profiles, and device storage

There is an important difference between a configuration available through SteelSeries GG and one saved to a device’s onboard memory. Support for onboard profiles and the functions they retain varies by product. Do not assume that a toggle macro will continue to work the same way on another computer, with GG closed, or after unplugging the device. Consult the documentation for the specific model and test the configuration in the conditions where you plan to use it.

Profiles can also affect behavior. A macro may be assigned in one configuration but not another, or the selected profile may not be the one you expect. Before troubleshooting the macro recording itself, check the active device, profile, assignment, and playback option. Keeping a simple test profile with one clearly labelled macro can make it easier to isolate the issue.

If GG offers a way to save or apply changes, make sure the change has taken effect before testing. A configuration visible in an editor may not be active if it has not been applied, or if another profile is currently selected. The exact save and profile controls depend on the software version and device.

Safety, game rules, and responsible use

Macros can send repeated inputs much faster and more consistently than a person can. In a text editor, that may merely fill a page with repeated characters; in another application, it could trigger commands, alter data, or interact with a live session. Test in a safe location, avoid using a loop where an unintended action could cause damage, and keep the stop control available.

For games and competitive services, check the relevant game’s rules and the service’s terms before using macros. Some environments restrict automation or repeated inputs, and rules differ by title and activity. A macro that is technically possible in GG is not automatically permitted in a particular game. Do not use it to bypass limits or automate actions that the game or service prohibits.

For accessibility or repetitive desktop work, a macro can reduce repeated manual input, but it should still be designed so you can stop it promptly. Prefer a short, predictable sequence, use an obvious trigger, and test whether the target application handles repeated input as intended. If a task involves sending messages, submitting forms, or changing important records, use a one-time sequence or manual confirmation wherever an accidental repeat would matter.

Frequently Asked Questions

Does SteelSeries macro toggle mean hold?
No. Toggle generally means press once to start and press again to stop, so the macro can continue after you release the trigger. Repeat While Pressed is the mode that ties playback to keeping the button held.

How do I make a SteelSeries macro run while I hold a key?
In GG, select the device and the assigned key or button, open the macro playback options, and choose Repeat While Pressed if it is available. Test the behavior in a harmless application to confirm that releasing the button stops it.

How do I stop a SteelSeries toggled macro?
Press the same assigned trigger again if the macro is configured for Toggle. If that does not work, check the playback mode and assignment in GG, then disable or change the macro before testing it again.

Why does my SteelSeries macro not have a toggle option?
Options can differ by device and GG version. Check that the product is recognized in Engine and review its available macro controls; the feature may not be offered for that model or configuration.

Will a SteelSeries macro keep working when GG is closed?
That depends on the device and whether it supports storing the relevant configuration onboard. Check your model’s documentation and test it under the exact conditions you plan to use; do not assume every macro or playback mode is saved to device memory.

Can I use a toggle macro in every game?
No. Technical support in GG does not guarantee that a game permits macros. Check the game’s current rules and avoid macros that automate prohibited actions or create unintended repeated input.

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.