How to use: Game Keybind Conflict Checker
Choose a preset or enter each action, physical key and active context.
Resolve same-context duplicates and review reserved or hard-to-reach combinations.
Export the plan locally, then test the highest-frequency cluster in the keyboard lab.
What the result actually measures
BindGraph normalizes physical keys and detects duplicate assignments only within the same active context. It also groups movement-hand, mouse and system-reserved risks, and can send a selected cluster to the live keyboard test.
Measurement boundary: A conflict-free plan does not prove comfort, accessibility or matrix rollover. Game updates and regional keyboard layouts can change action labels and physical reach.
How to interpret the output
Direct conflict
Two actions use the same physical key inside the same context and may compete.
Safe reuse
The same key appears in mutually exclusive contexts such as gameplay and menu.
Reach warning
A heuristic prompt to physically test the combination, not an ergonomic diagnosis.
Troubleshooting unexpected results
Import is rejected
Use the exported Keymap JSON shape; malformed or oversized files are refused locally.
Game accepts a duplicate
Mark the actions with distinct contexts if they are never active together; otherwise verify which action wins in game.
Frequently asked questions
Does Keymap read my game configuration files?
No. You enter or import a Keymap-formatted local plan; the page does not inspect installed games.
Can one key be valid twice?
Yes, when actions belong to mutually exclusive contexts. That is why the checker is context-aware.
Can I save a preset?
You can export and re-import a versioned JSON file without an account.