- Top Pick: Razer Basilisk V3
- Runner-up: Razer DeathAdder V3 Pro (Black)
- Also consider: Razer BlackWidow V4 (Green Switches)
Razer Synapse has no Linux version, so a Razer mouse or keyboard plugged into a Linux gaming PC runs on factory defaults: fixed DPI steps, stock polling and whatever lighting effect the firmware last remembered. OpenRazer is the community project that closes that gap, an open-source driver and daemon that talks to Razer hardware directly, with Polychromatic as its graphical front end.
Coverage is broad but never automatic. The project’s own supported-device list runs to more than two hundred peripherals, and everything in this guide follows that list and the project’s documentation: every feature claim, every install note and every product below is there because the project itself documents it. If a device is not on the list, OpenRazer does not control it, and no front end will change that.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
For Razer hardware on the project’s supported-device list, OpenRazer restores the settings Synapse would handle: mouse DPI and polling rate, Chroma lighting effects and brightness, keyboard lighting modes, and battery readouts on wireless models. Polychromatic provides the graphical controls. Firmware updates, dongle pairing and cloud profiles still require Synapse on Windows.
What OpenRazer controls, layer by layer
OpenRazer has three parts. A kernel module, rebuilt for each new kernel through DKMS, handles the hardware protocol. A daemon sits on top of it and adds persistence, battery notifications and small behaviours such as turning device brightness off when the screensaver starts. A Python library lets scripts and applications drive both. Front ends like Polychromatic are simply graphical clients of that daemon.
For a listed device, the daemon exposes the functions the firmware itself offers: DPI stages and polling rate on mice, brightness, the hardware lighting effects stored in the firmware, and custom addressable RGB lighting written by software. Wireless models report their battery state to the daemon, which is where the low-battery notifications come from.
The project is candid about the edges. Settings persist across power cycles only on some hardware, and connecting a device to a machine running Synapse resets that stored state. The hardware DPI buttons on most mice are not intercepted, so they keep their default behaviour and range. Headphones are the narrowest category of all: for supported headsets OpenRazer provides lighting features only and no audio features. Keypads are a similar partial case, where the project itself notes that key rebinding needs a third-party application such as input-remapper.
Polychromatic: the graphical front end
The daemon alone is a command-line and scripting tool. Polychromatic is the front end most people install with it: a device overview, per-device pages for the settings the daemon exposes, and an editor for building custom lighting effects zone by zone. Its tray applet covers the quick jobs, switching effects and checking a wireless mouse’s battery without opening the full window.
RazerGenie is a smaller alternative front end built on the same daemon. Choosing between them is a matter of taste, because neither adds hardware support: a front end can only display what the daemon recognises. If a device does not appear in Polychromatic, the missing piece is driver support for that device, not a different window on top of it.
What still needs Synapse on Windows
Firmware updates are the hard boundary. OpenRazer configures devices; it does not flash them, so a mouse or keyboard firmware release still means a Windows machine with Synapse, or a device whose settings were prepared there in advance. First-time pairing of some wireless arrangements belongs in the same bucket: the project documents known limitations around devices configured through a charging dock, and pairing a fresh HyperSpeed receiver is a Synapse task.
Synapse’s cloud layer stays behind too: synced profiles across machines, per-game linked profiles and Chroma effects that react through Synapse itself. Razer’s Windows audio software is separate again, so the surround processing sold with its headsets does not exist on Linux; a supported headset there is a USB stereo headset whose lighting you control. Finally, newly launched Razer hardware routinely arrives before support does, because each model is added by a contributor once its protocol is understood. The standard bridge for all of this is on-board memory: configure a device once on Windows, save the profile to the hardware, and Linux inherits it.
Installing OpenRazer, distro family by distro family
Every route starts with the same preparation. Install the kernel headers package that matches your running kernel, because DKMS compiles the module against them. Add your user to the plugdev group, then reboot so the driver and the group permissions take effect. Because the module is unsigned and built locally, Secure Boot may need to be disabled, as the project warns in its own install notes.
On Ubuntu, OpenRazer has been in the official repositories since 20.04, with the universe repository enabled; the project’s stable PPA serves newer releases, and installing the openrazer-meta package pulls in the full set. Debian carries it in the official repositories from Debian 10 onward, with the openSUSE Build Service repository as the route to newer builds. Fedora users should install the kernel-devel package explicitly first, since a Fedora quirk can otherwise pull the wrong headers package, then add the project’s hardware repository and install openrazer-meta. Arch provides the daemon in its official repositories. NixOS turns it on declaratively with the hardware openrazer option and a list of users. openSUSE and Mageia use Build Service packages, and openSUSE users should also enable the dkms service. SteamOS is the exception throughout: its immutable filesystem can remove the driver at a system update, and the project points Deck owners to community instructions rather than supporting it.
Five supported devices, checked against the list
Every model below appears by name on OpenRazer’s supported-device list, with the device ID the project publishes for it.
Razer Basilisk V3
The wired ergonomic mouse is the straightforward OpenRazer case: DPI stages, polling rate and its eleven Chroma zones are all reachable through the daemon, with no receiver in the path. Note that the list entry is this original V3; the later 35K refresh is a separate entry with its own ID.
- Sensor: Razer Focus+ optical, up to 26,000 DPI
- Buttons: 11 programmable
- Switches: Razer optical switches, generation 2
- Wheel: HyperScroll tilt wheel with free-spin and tactile modes
- Lighting: 11 Chroma RGB zones
- OpenRazer device ID: 1532:0099
Razer DeathAdder V3 Pro
Razer’s lightweight wireless esports mouse is where the battery readouts earn their keep: the daemon reports charge state and sets DPI and polling over the receiver or the cable. True 8,000 Hz polling needs the separate HyperPolling wireless dongle, and pairing accessories like that remains Synapse territory.
- Sensor: Razer Focus Pro optical, up to 30,000 DPI
- Weight: 63 g in black
- Connection: HyperSpeed wireless receiver or USB cable
- Battery: maker-rated up to 90 hours at 1,000 Hz polling
- Switches: Razer optical switches, generation 3
- OpenRazer device IDs: 1532:00B6, 00B7, 00C2, 00C3
Razer BlackWidow V4
The full-size mechanical board is a lighting-led case: per-key Chroma, the two-side underglow and brightness are what OpenRazer manages, along with the keyboard’s lighting modes. The six dedicated macro keys are hardware that other Linux tools can bind, but they are not the reason to install this driver.
- Switches: Razer Green mechanical, tactile and clicky (this listing)
- Layout: full-size, with 6 dedicated macro keys
- Keycaps: doubleshot ABS
- Extras: media roller and keys, magnetic wrist rest
- Lighting: per-key Chroma RGB with 2-side underglow
- OpenRazer device ID: 1532:0287
Razer Huntsman V2
The optical board’s headline figure, true 8,000 Hz polling, is a hardware property that OpenRazer neither adds nor removes; the daemon’s job here is the per-key lighting, brightness and effect selection. This listing is the linear-switch version with the sound dampeners and PBT keycaps.
- Switches: Razer Linear Optical Switches, generation 2 (this listing)
- Polling: up to 8,000 Hz
- Keycaps: doubleshot PBT
- Extras: dedicated media keys and dial, ergonomic wrist rest, sound dampeners
- Lighting: per-key Chroma RGB
- OpenRazer device ID: 1532:026C
Razer Kraken Kitty V2
The headset is the honest limit of the whole project. OpenRazer’s headphone support is lighting only, so on Linux the kitty ears and earcup Chroma are fully yours to configure while the audio side is plain USB stereo; Razer’s surround software runs on Windows. Buy it for the lighting and the microphone, not for audio processing.
- Drivers: Razer TriForce 40 mm
- Microphone: HyperClear cardioid
- Connection: USB wired
- Lighting: Chroma RGB kitty ears and earcups, stream-reactive
- OpenRazer support: lighting only
- OpenRazer device ID: 1532:0560
How to choose
Start with the device list, not the product page: match your exact model name against it before buying anything, because support is per model and sometimes per hardware revision. Wired devices are the safest purchases, since every function the firmware exposes is reachable over the cable. Wireless owners gain the most from the daemon day to day, through battery reporting and notifications, but should expect pairing jobs to stay on Windows. Headset buyers should read OpenRazer as a lighting tool and judge the headset on its drivers and microphone. If your desk is entirely Razer, OpenRazer plus Polychromatic replaces Synapse for daily settings; keep a Windows dual-boot or a second machine for firmware days.
Who should skip this
Skip OpenRazer if you game on Windows, where Synapse does all of this in one application. Skip it if your Razer gear is absent from the supported list, especially a just-launched model, because until a contributor adds it the hardware runs on defaults. Skip it if your setup depends on Synapse cloud profiles or Razer’s Windows audio processing. And skip it if factory defaults plus on-board memory configured elsewhere already give you everything you actually change.
FAQ
Does OpenRazer work on a Steam Deck?
Not as a supported route. SteamOS keeps its system image immutable, so an update can remove the locally built driver, and the project directs Deck owners to community-maintained instructions instead. Settings saved into a device’s on-board memory from a regular PC carry over to the Deck with the hardware.
Will my settings survive a reboot or a trip back to Windows?
It depends on the hardware. The project notes that devices retain settings across power cycles only where the firmware supports it, and that using the same device on a computer running Synapse resets that stored state. Profiles held in the daemon’s configuration stay on the Linux machine that created them.
My new Razer device is not detected. Why?
Because support is added one device ID at a time by contributors. The project asks owners of unlisted hardware to check its unreleased changes and issue tracker, and to file a support request with the device ID. Until support lands, the device works as a standard mouse or keyboard with no configuration layer.
Can Polychromatic record macros or rebind keys?
That is not what the front ends do. Polychromatic and RazerGenie expose the settings and effects the daemon supports; they add no macro engine of their own. The project makes the same point for its keypads, where rebinding is explicitly a job for a third-party tool such as input-remapper.
Final verdict
For listed hardware, OpenRazer is a genuine Synapse replacement for the settings Linux gamers actually change: DPI, polling, brightness, Chroma effects and battery awareness, with Polychromatic making all of it point-and-click. Its limits are equally specific and documented by the project itself: no firmware updates, no cloud profiles, lighting-only headsets and a wait for new models. Check the list first, and Razer hardware stops being a reason to keep Windows around.











