Razer Synapse configures supported Razer keyboards, mice, headsets, controllers, and other peripherals through one device dashboard. It changes button assignments, sensitivity or performance settings, macros, and lighting where the connected model exposes those controls. Razer Synapse does not add the same capabilities to generic hardware. The device firmware and hardware decide which pages and assignments appear.
Device profiles
Each detected device opens its own set of configuration pages. A mouse can expose sensitivity stages and button mapping, while a keyboard can expose key assignments and compatible actuation controls. A profile groups those choices so Razer Synapse can recall them for a game or another application. Changing a profile changes the mapped behavior; it does not modify the game’s own control file unless the game receives the resulting key or button input.
Some devices have onboard memory, but the hardware does not necessarily store every Synapse-controlled effect or service. A profile that works while Razer Synapse runs can therefore lose part of its behavior on another computer. The exact difference depends on the device model, so the onboard-memory indicator matters before a profile becomes the only copy of an important mapping.
Second-layer controls
Razer Hypershift gives supported keys or buttons a second assignment layer. One control acts as the Hypershift modifier, and another control performs its alternate action while the modifier remains active. This can place extra shortcuts on a device without changing its physical layout. It also creates two possible meanings for the same button, so an accidental modifier press can trigger an action that is not visible on the keycap.
Rapid Trigger belongs to compatible keyboards and adjusts how a key resets according to travel rather than a fixed release point. Razer Synapse shows that page only when the keyboard supports the feature. Installing Razer Synapse alone cannot add it to a switch or keyboard that lacks the required sensing hardware.
Macro mapping
The Macro module records keyboard and mouse events into a named sequence. Recording creates the sequence, but it does not make any device run it. The user returns to the device dashboard, selects a compatible key or button, chooses the macro assignment, and then selects the recorded sequence. This separation lets one macro serve several controls, but it also explains why a successfully recorded macro may appear to do nothing.
Razer Synapse does not allow every physical key to accept another function. The Windows key and Fn key remain unavailable for reassignment. Other limitations follow the connected model. A mouse button that the dashboard does not expose cannot receive a macro merely because the Macro module can record one.
Profile migration
The migration tool can detect data from Synapse 3 and lets the user select profiles, macros, and Chroma effects to move. Migration is an explicit operation rather than proof that every old setting already exists in the newer installation. Selecting only part of the available data leaves the rest in the earlier configuration. Hardware changes can also make a migrated assignment irrelevant when the destination device lacks the original control.
Hardware limits
Razer Synapse needs a supported Razer device before most configuration pages have useful targets. Available controls can also depend on current firmware. A missing feature may therefore come from the device model, its firmware, or the selected profile rather than a hidden global switch. Checking the exact device page avoids applying instructions for a similarly named keyboard or mouse whose sensors, onboard memory, or key layout differ.
