Installation

There are several ways to install Keymapper — use whichever fits you best.

Drag and drop from Superhive

The fastest route. On your Superhive orders page, drag the Keymapper extension straight from the browser into the Blender window. The first time, Blender asks for your Superhive API token (found in your Superhive account settings) and adds Superhive as a remote extension repository.

See Superhive’s own guides: extension support announcement and connecting Superhive as a remote repository.

Install through Blender's extension system

With Superhive connected as a remote repository (see above), open Edit > Preferences > Get Extensions, find Keymapper in the list, and press Install. Updates later are a single click on Update.

Drag and drop the downloaded zip

Download the Keymapper .zip from Superhive (do not extract it), then drag the file from your file browser into the Blender window and confirm the install prompt.

Install from Disk

1. Download the Keymapper .zip from Superhive. Do not extract it.
2. In Blender, open Edit > Preferences > Add-ons.
3. Click the dropdown arrow in the top-right corner and choose Install from Disk…
4. Select the downloaded .zip and confirm.
5. Make sure the checkbox next to Keymapper is enabled.

Updating

Via the Superhive repository: press Update in Get Extensions. Manually: install the new version over the old one and restart. Your shortcuts, folders, and settings are preserved either way.

Uninstalling

Before removing the addon, press Restore KMIs in the Keymapper panel to return every keybinding to its original state, then disable or remove Keymapper from the Add-ons list.

Getting Started

Keymapper's panel can be shown in three places:

• Edit > Preferences > Keymap — shown at the top of the Keymap section. Always enabled, so at least one Keymapper panel exists.
• The N-panel in the 3D Viewport, under the Keymapper tab.
• The addon's own preferences page.

The N-panel and Addon Preferences locations are toggled in the addon preferences (Edit > Preferences > Add-ons > Keymapper) under the Panel Visibility dropdown.

This is the Keymapper panel as it appears in Preferences > Keymap, its default location:

The Settings row

At the top of the panel you'll find:

• Active / Inactive — the master switch. Turning it off unregisters all your shortcuts and restores every disabled default.
• Keyconfig dropdown — the native keyconfig template Blender is using (Blender, Industry Compatible, etc.).
• Restore KMIs — removes all Keymapper entries (KMIs = keymap items, Blender's individual keybinding entries) and restores defaults.
• Re-scan — refreshes the operator and keymap scan; it turns red when a re-scan is recommended (e.g. after enabling other addons or switching keyconfig template).
• Save — saves your entries; highlighted when there are unsaved changes.
• F / P — toggles between friendly operator names and raw Python identifiers.

Creating Shortcuts

1. Click the + button in the toolbar to open the entry form.
2. Pick one or more operators via Browse Operators.
3. Set the keybinding — key, modifiers (Shift/Ctrl/Alt/Win), and event type (Press, Click, Drag, …).
4. Confirm. The shortcut is registered immediately.

Adding from the right-click menu

The fastest way to bind something you're looking at: right-click a button or menu item in the UI and choose Add Keymapper Shortcut Entry…

A popup panel opens with that operator already filled in — set the keybind and confirm right there, without opening the full Keymapper panel. The popup offers the same controls as the main editor: the Button section, context selector, detection contexts, and button preview. The popup also has a button that redirects you to the full panel for further editing; which panel it redirects to is configurable in the addon preferences.

Browse modes

Browse Operators opens as a draggable popup dialog. A "Selected" summary grows with your picks, and nothing is applied until you press Confirm — Cancel, Esc, or clicking away discards the changes. The same dialog style is used across the editor: value pickers, per-operator Context, detection contexts, and button locations.

• All — every operator, organized into categories.
• Simple — curated multi-operator actions, e.g. one "Select All" that covers every editor and mode at once.
• Factory — every binding the factory keymap actually uses. Disabled by default; enable in preferences under Other.

Multi-Operator Entries

An entry can hold several operators and several extra keybinds at the same time. Each operator in the entry carries its own context (which editor or mode it fires in) and its own properties — each operator sits in the Operators list with a Properties dropdown on its row and its own context selector. Because contexts don't overlap, the operators never fight each other — the one that belongs to the editor you're in is the one that runs.

This is what makes one key work "everywhere": a single Select All entry can carry mesh.select_all, object.select_all, curve.select_all and more, each scoped to its home context. Contexts can be left on automatic, where Keymapper resolves each operator's home keymaps for you, or set manually per operator. While you edit, each conflict dropdown shows a live "(Preview – n)" count whenever your unsaved changes would alter the result.

The quickest way to build one is the Simple browse mode: selecting a multi-op there adds the whole bundle of operators in one click, with the correct per-operator contexts and properties already set.

Labels & Icons

Entry labels

An entry's displayed name comes in two flavors. By default it is pre-registered: Keymapper derives it from the entry's first operator using its friendly-name catalog (the F/P button in the Settings row switches between these friendly names and the raw Python identifiers). Set a custom label in the entry form and it overrides the derived name entirely — useful when a bundle of operators deserves a name of its own.

Attribute-based operators get plain-language names too: an entry built on a wm.context_* operator is named after the setting it changes, so a shortcut reads "Face Orientation" rather than "Context Toggle".

Custom icons

Each entry shows an icon, automatically resolved from its first operator. To change it, open the entry form and click the icon to open the icon picker — browse by category or search, preview the current and selected icon side by side, and use Reset to Auto to return to the automatic choice.

Entry Buttons

A shortcut doesn't have to be a keybind at all — an entry can also be a button placed in Blender's UI. In the entry editor, enable Button (Keybinds and Button share one section) and pick one or more locations via the Locations dialog; the button shows the entry's icon and/or label (both can be toggled, though at least one must stay on), with a live preview while you edit — in both the main editor and the right-click popup. Pressing the button runs the first of the entry's operators that is valid in that context.

Keybind and Button can be combined on the same entry, but at least one of the two must remain enabled. A button-only entry registers no keybindings and disables no defaults — by default it is excluded from conflict scanning, but an optional toggle can make it detect and disable shortcut conflicts.

The entry card gives quick access too: a visibility toggle hides or shows the entry's button in all its locations with one click, and clicking the card's locations line opens the locations picker directly.

Additional Keybind Detection Contexts

Every keybind slot has an Additional Keybind Detection Context(s) picker, tucked behind a small arrow next to Repeat — it opens as a popup dialog. Contexts checked here don't create a keybinding — they extend the conflict detection for that key, so same-key defaults in those extra contexts are disabled too. Use it when a default binding in a context your operators don't cover would otherwise still swallow your key. Contexts the entry's operators already occupy show pre-checked and locked.

Bundled Operators

Keymapper ships with a few operators of its own — extra tools that Blender doesn't have, ready to be bound like any other operator. You'll find them in Browse Operators under Keymapper's own subcategory in the category "Addon Operators".

• Marking Menu — a pie menu for fast access to common actions.

  

• Tool-Select Menu — a pie menu for switching the selection tool.

  

• Pivot Transform — ability to easily edit the pivot point of an object.

  

• Open Asset Browser Window — opens the Asset Browser in its own separate window.

  

All of the bundled operators are included in the shortcut presets, so they work the moment you apply those — see Folders & Presets.

Folders & Presets

Folders

Entries are organized into folders. Use the toolbar to create, remove, rename or move folders up/down. You can also move entries up/down, duplicate, and copy/paste entries between folders. The folder icon on the right side of the toolbar is specifically for moving entries to other folders.

Shortcut Presets

The Shortcut Presets popup offers curated folders of ready-made shortcuts — navigation, selection, tools, pie menus and more. Apply everything with Add All, a single folder, or individual entries. Some presets bind Keymapper's own bundled operators — the marking menu, tool-select pie, pivot editing, and asset browser window — so they work the moment you apply them.

Applied preset entries remember where they came from: if you edit one, a Restore button lets you revert it to the original preset definition at any time.

Conflict Detection

Keymapper checks your entries against three kinds of conflicts:

• Against Blender's defaults — shortcut conflicts (a default doing the same thing) and keybind conflicts (a different action already on your key).
• Against other addons — keymap items registered by other addons get their own Addon Conflicts dropdown, separate from Shortcut and Keybind conflicts.
• Between your own entries — duplicates, shared keys, and overlapping operators, marked with a warning icon on the entry card.

Clicking an entry's conflict icon enters focus mode, dimming everything not involved in that conflict so you can see exactly which entries collide.

An entry that is identical to a default keybinding shows a dimmed blue mirror icon. Instead of creating a duplicate, Keymapper takes control of the existing default — and returns it to its original state when the entry is removed or edited away from being identical.

Turning the overriding off

By default, when one of your shortcuts conflicts with a built-in binding, Keymapper overrides it — the colliding default is disabled so your shortcut wins. If you'd rather keep certain defaults active, this can be switched off per conflict type in the addon preferences, under Conflict Detection > Conflict Overrides:

• Override Shortcut Conflicts — controls whether defaults that do the same thing as your entry get disabled, with a sub-toggle for defaults whose operator properties differ.
• Override Keybind Conflicts — controls whether defaults sitting on the same key get disabled, with a per-action-value matrix (Press, Release, Click, Double Click, Click Drag) for fine-grained control over which event types count.

With an override switched off, conflicts of that type are still detected and shown on the entry — but the default keybinding is left untouched.

What counts as a conflict is configurable in the addon preferences — including which keyconfig layers are scanned and how property and action values are compared.

Overrides can also be controlled per entry. An entry's conflict list shows every default it currently overrides, each with its own checkbox — untick one, and that specific default stays enabled while the rest of the entry works as normal. Handy when you want your key everywhere except in a few contexts.

Import / Export

The export button in the toolbar saves your complete setup — folders, entries, keybinds, and operator properties — to a single JSON file. Import merges a JSON file back in, recreating folders and entries and registering their shortcuts immediately.

This is also the easiest way to move your shortcuts between Blender and Bforartists, between machines, or to share a setup with someone else.

Settings

The addon preferences (Edit > Preferences > Add-ons > Keymapper) contain:

• Panel Visibility — choose where the Keymapper panel appears (N-panel, addon preferences — the Keymap location is always enabled), and where the right-click popup's edit button redirects to.
• Conflict Detection — which keyconfig layers are scanned (Factory / User / Addon) and override rules for shortcut and keybind conflicts, including a per-action-value detection matrix.
• Other — Changelog and extra options such as enabling the Factory browse mode.

Every checkbox shows a restore button whenever its value differs from the default, so you can always get back to stock behavior.