Basilisk V3 Pro Chroma Profiles Explained

The Razer Basilisk V3 Pro supports Chroma profiles through Razer Synapse and Chroma Studio, but the important catch is this: Chroma lighting effects are not saved to the mouse’s onboard memory. Button bindings, DPI stages, polling behavior, and stored mouse profiles can travel with the mouse; custom lighting profiles need Synapse running on the computer.

Skip to the picks

That distinction is the answer most people are looking for when they search for Basilisk V3 Pro Chroma profiles. The mouse is Chroma-compatible, and Razer lists it with 13 Chroma lighting zones and 16.8 million color options on the original RZ01-04620 model, but those zones are controlled by software rather than by a self-contained lighting memory slot on the mouse itself. Razer’s own onboard-memory support page says lighting effects cannot be saved to onboard memory and require Razer Synapse to be installed and running.

If you want Chroma lighting profiles on the Basilisk V3 Pro

Use Razer Synapse, then configure the mouse under the mouse device page and Chroma Studio. On the original Basilisk V3 Pro, the support page identifies the model as RZ01-04620 and lists it as Razer Synapse 3-enabled. The newer Basilisk V3 Pro 35K is RZ01-0524 and is listed as Synapse 4-enabled.

For the original Basilisk V3 Pro, the practical path is:

1. Install Razer Synapse 3 from Razer.
2. Connect the Basilisk V3 Pro by USB-C cable or the 2.4 GHz HyperSpeed dongle.
3. Open Synapse and select the mouse.
4. Use the mouse page for device settings such as button assignment, DPI, polling rate, and basic lighting.
5. Open Chroma Studio for layered Chroma effects.
6. Save the lighting effect in Synapse.
7. Keep Synapse running if you want that lighting profile active.

Razer’s Chroma Studio guide names the Studio tab and includes effects such as Breathing, Fire, Reactive, Ripple, Spectrum Cycling, Starlight, Static, and Wave. The Basilisk V3 Pro master guide also says the Lighting subtab controls brightness, power-saving lighting behavior, and quick effects such as Audio Meter, Breathing, Fire, Reactive, Spectrum Cycling, Starlight, Static, and Wave.

The exact wording matters because there are two different things people call a “profile.” A Synapse mouse profile can hold performance and button settings. A Chroma effect is the lighting setup. Synapse can associate those things while the software is running, but the Chroma effect itself is not written into the mouse as a standalone lighting mode.

If you want profiles without Synapse running

The Basilisk V3 Pro can store mouse profiles for use without Synapse, but not the Chroma lighting effects. Razer’s master guide says the Basilisk V3 Pro can store up to 5 profiles from Synapse and that the profile button cycles through them. It also says profiles are assigned to onboard memory by clicking the On-board Profiles button and dragging the profile to the preferred memory slot.

On the original Basilisk V3 Pro, Razer’s support page lists storage as Hybrid On-board and Cloud Storage with 4+1 profiles. In the master guide, the profile indicator colors are:

That is useful if you want the mouse to behave the same way on another PC, a work laptop, or a machine where Synapse is not installed. It is not useful if the goal is to carry a full desk-wide Chroma lighting scene from one computer to another. The onboard slots are for device behavior, not for the Chroma Studio lighting layers.

If the profile button changes settings but not lighting

That is usually expected behavior, not a broken Basilisk V3 Pro. The bottom profile button cycles onboard profiles. Those profiles can affect mouse behavior such as button assignments, sensitivity stages, and polling settings. The lighting profile still belongs to Synapse.

A clean check looks like this:

1. Close Synapse from the system tray with Exit All Apps.
2. Press the profile button on the underside of the Basilisk V3 Pro.
3. Watch the profile indicator, not the logo or underglow.
4. Confirm whether DPI stages or button behavior change.
5. Reopen Synapse and check whether the selected profile is visible in the app.

If the indicator changes but the Chroma lighting does not, that matches Razer’s documented limitation for lighting effects and onboard memory. If nothing changes at all, move to firmware, connection, and detection checks.

If you have the Basilisk V3 Pro 35K instead

Do not mix instructions blindly between the original Basilisk V3 Pro and the 35K revision. They look related, but Razer documents them as different model numbers with different Synapse generations.

The same lighting limitation still matters. Razer’s general onboard-memory support article says lighting effects are managed through Synapse and cannot be saved to onboard memory. The 35K model can store onboard profiles, but that does not turn it into a hardware-only Chroma Studio device.

Also check firmware against the exact model number before updating. Razer lists the original Basilisk V3 Pro RZ01-04620 firmware updater as v2.01.01_r1, released December 14, 2024. For the Basilisk V3 Pro 35K RZ01-0524, Razer lists v2.52.00_r1 for the standard model and v2.53.00_r1 for the Phantom Edition. Installing the wrong updater is not a Chroma fix; it is a model mismatch risk.

If you want a DeathAdder-like replacement that matches a Chroma setup

The Basilisk V3 Pro is Chroma-compatible, but it is not shaped like a DeathAdder. It is a right-handed ergonomic mouse with a thumb rest, multi-function trigger, 11 programmable buttons, a tilt wheel, and underglow zones. A DeathAdder user who mainly wants the same palm shape may find the Basilisk more feature-heavy and wider-feeling than expected.

For the lighting setup, though, the key answer is simple: the Basilisk V3 Pro can join a Razer Chroma setup through Synapse. It can use Chroma effects, including per-zone lighting through Chroma Studio. It just cannot carry those Chroma profiles independently in onboard memory.

Choose the Basilisk V3 Pro if the priority is Chroma compatibility plus more controls: thumb trigger, tilt wheel, scroll modes, and stored mouse profiles. Do not choose it expecting a hardware-only Chroma profile that works the same way with Synapse closed. If the old DeathAdder feel is the priority, compare the shell shape before buying; Chroma compatibility alone does not make the Basilisk a DeathAdder replacement.

What to check before returning it

Check these items before treating Chroma profile behavior as a defect:

1. Confirm the exact model number: RZ01-04620 for Basilisk V3 Pro or RZ01-0524 for Basilisk V3 Pro 35K.
2. Use the correct Synapse generation: Synapse 3 for the original model, Synapse 4 for the 35K model.
3. Update Synapse before changing firmware.
4. Update firmware only from the support page for that exact model.
5. Connect directly to the PC by USB or use only the intended 2.4 GHz dongle connection while troubleshooting.
6. Keep Synapse running when testing Chroma effects.
7. Close Synapse only when testing onboard mouse profiles.
8. Do not expect Chroma Studio lighting layers to survive on a PC without Synapse.

Razer’s mouse troubleshooting guide also recommends direct PC connection instead of a hub, firmware updates, testing on another system without Synapse, checking for conflicting software, and a clean Synapse reinstall if the mouse is not detected or buttons/DPI behave incorrectly.

Contact Razer support or start a warranty case if the Basilisk V3 Pro is not detected in Synapse after direct USB testing, the profile button never changes stored profile behavior with Synapse closed, the mouse cannot accept the correct firmware updater for its exact model, or the lighting zones fail even with Synapse running and a basic Static effect selected. Those are different from the onboard Chroma limitation; they point to software corruption, connection trouble, or hardware failure.