What customization features does Aurora-RGB offer for lighting effects?

Aurora-RGB provides customization at four levels: a layering system for combining effects, profile import/export for saving and sharing setups, scripting for effects and devices the built-in options don't cover, and device-level settings such as keyboard layout, mouse orientation, and global brightness. These features apply to the RGB peripherals from the brands the software supports; the page does not state system requirements or platform limitations, so check those before relying on a specific feature.

Layering system: the core of customization

Aurora-RGB is built around layers rather than a single effect applied to the whole keyboard. Each layer carries its own effect, and layers stack to produce the final lighting.

• Custom layers with individual effects — you define a layer and assign an effect to it, so a background gradient, a reactive key effect, and a status indicator can coexist.
• Freeform region key selection — instead of picking keys one at a time, you select a freeform region of the keyboard for a layer's effect.
• Gradient layers — customizable gradient layers let you define color transitions as a layer of their own.
• Program-defined layers — other programs can add their own lighting layers, which is how the software supports daytime and nighttime themes driven by external tools.

A practical example: a user wants a static blue base, a red flash on damage in a game, and a volume bar in one corner. Each becomes a separate layer, and the layering system resolves them into one output instead of forcing a choice between effects.

Profiles, import/export, and previews

• Import/Export for profile settings — configurations can be exported and imported, which is the mechanism for backing up a setup or moving it to another machine.
• Preview lighting effects without launching the game — effects can be tested in the software before committing to a game session.
• Shortcuts Assistant — displays shortcut keys, useful when a layer is bound to a hotkey.
• Automatic updater — keeps the installation current without manual downloads.

Scripting support

Scripting extends customization beyond the built-in effect list in two directions:

1. Custom lighting effects — effects that the standard layer options don't produce.
2. Custom devices — device definitions for hardware not covered by the existing support.

This is the escape hatch for unusual hardware or a specific visual behavior. It assumes some willingness to write code; the page describes the capability but not the scripting language or API, so treat the specifics as something to confirm in the project's documentation.

Device and environment settings

The brightness and timed-off controls are the practical ones for daily use: brightness changes mid-game without alt-tabbing, and the timed shutoff handles lights left on after you step away.

On-keyboard information displays

Customization also covers what the keyboard shows beyond color:

• Volume percentage
• CPU and memory usage

These occupy keyboard real estate, so they compete with game effects for the same keys — another reason the layering system matters.

Game integration as a customization layer

Game effects are themselves customizable layers rather than fixed presets. The page lists per-game features such as health and ammo indicators, kill animations, ability cooldowns, and team-based background lighting across titles including CS2, Dota 2, Diablo 3 and 4, Borderlands 2, DOOM, GTA V, and Euro Truck Simulator 2. Support extends to almost any Logitech LED and Razer Chroma supported game, and multiple brands of peripherals can run simultaneously.

How to decide if these features fit

• Choose Aurora-RGB if you want to combine effects rather than pick one, need per-game reactive lighting, and are comfortable with a layer-based model that may require scripting for edge cases.
• Look elsewhere if you want a single static color with no configuration, or if your peripherals fall outside the supported brand and model range — the page claims wide coverage across top brands but does not enumerate every model.
• Verify before committing the scripting language, the exact list of supported devices, and platform requirements, since the page describes capabilities without those details.