The app says "Browser Not Supported"
Zmapper's USB flow requires desktop WebSerial. Firefox, Safari, and mobile browsers do not support the required path.
Fix: reopen Zmapper in desktop Chrome, Edge, or Opera.
Use this guide to connect over USB, remap live, and recover from common connection failures.
Use a desktop Chromium-based browser with WebSerial support: Chrome 89+, Edge 89+, or Opera 75+.
Plug your keyboard in over USB, open Zmapper, then click Connect Keyboard and pick your device from the browser chooser.
If Zmapper shows a locked state, press your keyboard's &studio_unlock combo. Zmapper will continue loading after the device reports it is unlocked.
Select a key, choose a new behavior, and adjust its parameters in the editor panel. Changes apply to the connected device immediately so you can validate them before saving.
Click Save to persist your edits to the keyboard. Use Discard if you want to roll back unsaved changes before they are committed.
If Zmapper refuses to connect, stay on USB, retry with a supported desktop browser, and then work through the troubleshooting steps below.
Zmapper's USB flow requires desktop WebSerial. Firefox, Safari, and mobile browsers do not support the required path.
Fix: reopen Zmapper in desktop Chrome, Edge, or Opera.
The browser can only list serial devices it can see. Charge-only cables, flaky hubs, and some dock paths will prevent the keyboard from appearing.
Fix: reconnect with a data-capable USB cable, avoid hubs if possible, and retry Connect Keyboard.
WebSerial access can be blocked by browser policy, hardened work profiles, or extensions that interfere with USB/serial permissions.
Fix: retry in a clean local browser profile. If you are on a managed machine, test from an unmanaged Chrome or Edge profile.
The firmware is reachable, but Zmapper cannot load the live keymap until the keyboard is unlocked.
Fix: press the configured &studio_unlock combo on the keyboard, then wait for the loading state to finish. If you do not know the combo, check the firmware keymap you flashed.
This usually indicates a transport interruption while Zmapper is fetching behaviors, layouts, or keymap data.
Fix: reconnect the keyboard, keep the tab open, and try again. If it keeps happening, swap the cable/port and retry without a USB hub.
Live edits are not durable until you save them back to the device.
Fix: after remapping, click Save and wait for the save to finish before disconnecting the keyboard or closing the tab.