To get a macro on a SteelSeries device, open SteelSeries GG, choose your device in Engine, create or record a macro in the key-binding controls, then assign it to a key or button. You will need a compatible SteelSeries device and GG installed; menu labels and macro features can vary by device and GG version.
What You’ll Need
- A SteelSeries keyboard, mouse, or other compatible device connected to your computer. Macro options are not identical across every model.
- SteelSeries GG installed and up to date. Download it from the official SteelSeries website, install it, and open the app.
- A clear idea of the actions the macro should perform, including the order and any pauses between them.
- An application where you can safely test the sequence. A plain text editor is useful for testing text-entry macros; use a harmless test area for other actions.
You generally do not need a separate macro program or a SteelSeries account just to configure a device in Engine. On Windows and macOS, GG has a similar overall workflow, but device support and some controls can differ. If Engine does not show your model or macro controls, check the model’s support information and update GG before troubleshooting further.
Step-by-Step
-
Install GG and connect the device. Download SteelSeries GG from the official SteelSeries site, install it, and launch it. Connect the device directly to the computer if possible, rather than through a hub, and wait for GG to recognize it. Wireless devices should be switched on and connected using their supported receiver or Bluetooth connection. If the device is not detected, resolve that first; there is nothing to assign a macro to until it appears in Engine.
-
Open Engine and select the device. In the GG window, open Engine and select your keyboard or mouse from the device tiles. The exact layout can change between GG releases. Look for the device’s configuration or key-binding screen. If you have more than one SteelSeries device connected, double-check the model name so you do not set up the macro on the wrong one.
-
Choose the configuration you want to edit. Engine settings are often grouped into configurations or profiles. Select the one you use for the desktop or the application where you want the macro. If you create a new configuration, give it a recognizable name, such as “Text shortcut” or the name of the application. A macro assigned to a different configuration may seem to disappear when you switch profiles, even though it is still saved.
-
Pick the key or button that will trigger it. In the device’s key bindings, click the key, mouse button, or other assignable control you want to use. Avoid choosing an essential key unless you are comfortable replacing its usual action. A spare mouse button or a key you rarely use is often easier to test. Check whether the assignment will affect the key in every configuration or only the one currently selected.
-
Open the macro assignment option. In the assignment menu, look for a Macros category. Choose an existing macro if you already made one, or choose the option to create a new macro. Depending on the GG version, you may be taken to a Macro Editor or prompted to create and name the macro from the assignment menu. If you do not see Macros, confirm that you selected an assignable control and that the device and software support this feature.
-
Name the macro and record the sequence. Give it a short, descriptive name so you can identify it later. Start recording in the editor, perform the key presses in the intended order, and stop recording when the sequence is complete. For example, a simple text macro might enter a short phrase followed by a tab. If the editor provides a setting for recording delays, decide whether the timing between presses matters. A sequence entered too quickly can fail in applications that need time to respond.
-
Review and adjust the recorded actions. Read through the event list before saving. Remove accidental keystrokes, add or adjust pauses if the editor offers timing controls, and check that each press has a corresponding release where appropriate. Do not assume a recording is correct just because the keys were pressed in the right order; a held key, missed release, or unintended extra event can make playback behave differently. The editor’s controls and supported event types depend on the device and GG release.
-
Choose how the macro should play. Select the playback behavior offered by the editor, such as playing once or repeating while the trigger is held, if those choices are available. For most first tests, use a single playback rather than a repeat or toggle mode. Repeating actions can enter text many times or keep triggering commands unexpectedly. If the editor offers a toggle mode, learn how it starts and stops before using it in an important application.
-
Save the macro and assign it to the control. Save your recording, then return to the key-binding screen if needed and choose the saved macro for the key or button. Check that the binding display now shows the macro name, not the key’s previous function. Some interfaces save edits automatically; others show a save or confirmation control. Follow the prompt shown in GG and make sure the selected configuration remains active.
-
Test it in a safe place. Open a text editor or another low-risk application, click in a blank area, and press the assigned control once. Confirm that the expected actions happen in the right order and at a usable speed. If it types or triggers the wrong thing, stop and edit the macro rather than repeatedly testing it in a live game, document, or chat. Test again after changing the timing or playback mode.
-
Check how it behaves after switching applications. Try the target application only after the simple test works. Make sure the intended configuration is active and the application has focus. If the macro is needed only in one program, use a dedicated configuration if your device and GG version support application-specific switching. Do not assume the macro will be stored on the device itself; onboard memory and macro playback support vary by model.
Common Mistakes
Assigning the macro to the wrong key or profile: It is easy to edit one configuration and then test another. Verify the selected device, configuration name, and binding before deciding that the macro was lost.
Recording unwanted input: Starting recording too early or stopping too late can capture stray presses. Review the recorded event list and remove anything that is not part of the intended sequence.
Using repeat playback by accident: A repeat or toggle setting can cause an action to run many times. Start with play-once behavior, if available, and only use repetition when it is genuinely needed.
Testing in a sensitive place: A macro may send text, key combinations, or repeated actions into whichever application has focus. Test in a blank, harmless area first and avoid triggering it in a live match, an unsaved document, or a form.
Expecting every model to offer the same controls: SteelSeries devices differ in their buttons, configuration features, and onboard memory. A guide for a particular keyboard may not match the menus or capabilities of a mouse. Use the options shown for your exact model.
Tips
- Keep each macro focused on one predictable task. A short sequence is easier to test, edit, and troubleshoot than a long chain of unrelated actions.
- Use clear names that describe what the macro does, not just the key that triggers it. This helps when you have several configurations or recordings.
- Include pauses only when timing matters. A delay can give an application time to respond, but unnecessary delays make a simple macro feel slow.
- Use a key or button that is comfortable to press and unlikely to be triggered by accident. If you replace a key’s normal function, record that choice so you remember how to restore it.
- Make one change at a time when tuning a macro. If you alter the recording, timing, playback behavior, and profile all at once, it is harder to identify what fixed or caused a problem.
- Before relying on a macro, check the rules for the application or game where you plan to use it. Some games and services restrict automation, especially when it provides an unfair advantage. Follow their current policies.
- If you want the macro to work when GG is closed or on another computer, check the documentation for your specific device. Some devices have onboard profile storage, but that does not mean every Engine feature or macro can be saved or played back independently of GG.
Troubleshooting
GG does not detect the device: Reconnect it, try another USB port, and check that a wireless device is powered on and paired using its supported method. Close and reopen GG, then check for software updates. If it still does not appear, consult SteelSeries support for that model rather than following instructions for a different device.
There is no Macros option: First select a key or button that can be remapped; some controls cannot take custom assignments. Confirm the device is supported in Engine and that GG is current. If the macro feature remains unavailable, it may not be supported for that model, operating system, or specific control.
The macro is saved but does not run: Confirm that the macro is assigned to the intended control and that the correct configuration is active. Check whether the application has focus, and test the trigger in a plain text editor or another safe application. If it works there but not in the target program, that program may handle input differently or restrict automation.
Only part of the sequence happens: Reopen the macro editor and inspect the event order. Re-record missed presses, check for unintended held keys, and add a small delay where the receiving application needs time between actions. Test after each adjustment.
The sequence runs too many times or will not stop: Return to the macro’s playback setting and switch to a one-time behavior for testing. If the macro uses repeat-while-held or toggle behavior, release the trigger or use the editor’s stated stop action. If necessary, remove the binding temporarily while you edit it.
It works only while GG is open: This can be expected when a device or macro depends on GG software rather than onboard memory. Check your model’s manual and Engine options for supported onboard configurations. If the feature cannot be stored on the device, keep GG running when you need the macro.
Frequently Asked Questions
Can I make a macro without recording it?
Some GG versions let you create or edit events in the Macro Editor, while others center the workflow on recording and then editing. Use the controls actually shown for your device and version; you do not need to record a perfect take if the editor lets you correct the event list.
Can a SteelSeries macro type a sentence?
It can, if your device and GG version support the required input events or text-entry option. Test capitalization, punctuation, and keyboard layout in a text editor first, since language settings and application behavior can affect the result.
Will the macro work on every SteelSeries keyboard or mouse?
No. Macro controls, assignable buttons, and onboard storage vary by model. Check the device tile in Engine and its product support information for the features available on your exact device.
Does SteelSeries GG have to stay open?
It depends on the device and how the macro is stored. Some configurations may rely on GG running, while certain devices support onboard profiles. Verify the behavior for your model by testing with GG closed only after saving your work.
Can I use the same macro in a game?
Technically, a macro may work in an application that accepts its inputs, but individual games set their own rules for automation. Check those rules before using a macro, and do not use it to bypass restrictions or gain an unfair advantage.
How do I remove or change a macro?
Return to Engine, select the same device and configuration, and open the binding for the assigned key or button. Choose another assignment or restore its default action, then edit or delete the macro through the macro controls available in your GG version.
Related
- ZP Balance of Payments: Meaning and Key Concepts
- Assembly Split in CATIA: How to Separate a Product
- Balance Sheet Accounting: How It Works
Try it: the Column Letter to Number: aA is 27, XFD is 16,384. Converts both ways.
More in VBA & macros
- Excel VBA Day From Date: Weekday Numbers and NamesIn Excel VBA, use Day(dateValue) to return the day of the month, such as 14, and Weekday(dateValue, vbMonday)…
- Auto Macro Recorder in Excel: How to Record and Use ItExcel’s macro recorder captures supported actions as VBA code, letting you replay a routine instead of repeating it…
- How to Use Macros in SteelSeries GGTo use a macro in SteelSeries GG, open Engine, select a compatible device, create or record a macro…
- Excel VBA Function Output: Return Values and DisplayAn Excel VBA function outputs a value by assigning that value to the function’s name. That value appears…
- Excel VBA Find Value in Range: Examples and TipsTo find a value in an Excel range with VBA, use the range’s Find method, then check whether…
- VBA AutoFilter Off: Remove Arrows or Clear FiltersTo show every row while keeping the filter controls, use VBA’s ShowAllData method when the worksheet is filtered.…
Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources
Spotted an error in this guide? Let us know.