Related tools
- Keyboard Layout HeatmapShow per key press counts and finger load for any pasted text, compared across ten common keyboard layouts.
- Display InfoLive readout of your screen resolution, pixel density, refresh rate, color capabilities, and input features.
- Key Rollover TesterCheck N-key rollover and ghosting visually by holding down keys and watching a live diagram.
- Keycode InfoShow a live readout of every keyboard event field: key, code, legacy keyCode, active modifiers, location, and repeat state.
- Media Key TesterVerify Media Session action handlers and hardware media keys, and see whether your headset or keyboard buttons actually reach the page.
- Multitouch TesterVisualize simultaneous touch points, dead zones, and stylus pressure.
What it does
Compares two revisions of a ZSA Moonlander layout and lists every key that changed, layer by layer. It reads the keymap.c file from the Download Source zip that Oryx gives you, parses the LAYOUT macros (including nested keycodes like LT(1, KC_SPC) and MT(MOD_LSFT, KC_ESC)), and names each changed key by where it physically sits: which hand, which row, which column and which finger zone. Layer names come from the layers enum in the file when it has one. It also reports layers added or removed between the two revisions, and spots bindings that moved from one key to another on the same layer.
How to use it
In Oryx, open each revision of your layout and use Download Source to get its zip, then open keymap.c from each one. Paste the older keymap.c into the box, add a line containing only =====, then paste the newer keymap.c below it. The report shows changed keys per layer with old and new names; switch on "Show unchanged keys" for the full picture of every key, or pick CSV to get position, layer, old and new columns you can drop into a spreadsheet.
Why this one
Oryx has no layout diff, so comparing revisions means opening two browser tabs and eyeballing the configurator key by key until something looks off. This reads the keymap.c you already export and names every changed key by its physical position, so a review takes seconds instead of a squinting session. It runs entirely in your browser: your files and inputs never leave your device.
FAQ
- Where do I get the keymap.c file?
- In Oryx, open the layout, click Download Source, and unzip what it hands you. keymap.c is in there, and it is the only offline export Oryx offers that contains the actual key assignments. Do this for both revisions you want to compare and paste the two files in, separated by a line of five equals signs.
- Does this work for the ZSA Voyager or the ErgoDox EZ?
- Not yet, honestly. The parser reads any QMK LAYOUT macro, so a Voyager or ErgoDox keymap.c will still be diffed and you will still see which keys changed, but only the Moonlander physical map (72 keys per layer) ships with the tool. Layers with a different key count are reported by key index instead of hand, row and column, and the tool says so in a warning.
- Is my layout uploaded anywhere?
- No. The parser and the diff both run in your browser, and your files and inputs never leave your device. Nothing is sent to ZSA, to this site, or anywhere else, so you can compare a work layout without thinking twice about it.
Keyboard shortcuts: press ? anywhere on this page to see them.