STEAMVR INPUT MAPPING

OpenVR2Key

Turn VR Controller Inputs Into Keyboard Commands

OpenVR2Key lets SteamVR controller actions trigger keyboard keys, shortcuts, and key combinations on Windows. Explore setup instructions, controller bindings, key mapping, troubleshooting, and OpenVR2Key resources.

WindowsSteamVRKeyboard MappingVR Controller Input

VR Input

Controller button, trigger, grip or chord

TriggerGripChord

OpenVR2Key

Matches the action and loads your mapping

INPUTMAPOUTPUT

Keyboard Output

A simulated key press reaches Windows

CTRL + SHIFT + MF9

SteamVR Input

Controller actions are read through the SteamVR input system.

Keyboard Simulation

Mapped actions are sent to Windows as simulated key presses.

Custom Key Mapping

Decide which key or shortcut belongs to each controller action.

Key Chords

Combine buttons so a shortcut only fires when you mean it.

What Is OpenVR2Key?

OpenVR2Key is a small Windows utility that sits between SteamVR and your desktop. Instead of adding new features to a VR game, it does one focused job: it listens for controller actions you have registered through SteamVR, and when one of those actions fires it sends a simulated keyboard event to Windows — exactly as if your fingers had hit the key on a physical keyboard.

That single idea solves a very practical problem. Once a headset is on your face, the keyboard is invisible. Recording software, voice chat, overlays, streaming tools, and plenty of PC games still expect a keystroke such as F9 or Ctrl + Shift + M. With OpenVR2Key running, a grip squeeze or a trigger pull can produce that keystroke without ever taking the headset off.

The workflow has two distinct layers, and understanding the split makes everything else easier. The first layer lives in SteamVR controller bindings, where you choose which physical control — trigger, grip, face button, joystick click, or a combination of them — is attached to an OpenVR2Key action slot. The second layer lives inside OpenVR2Key itself, where each action slot is given a key or key combination to output.

Because the two layers are separate, you can change the physical button in SteamVR without touching your keyboard mapping, or swap the keyboard output without re-binding a controller. People typically use OpenVR2Key for hands-free hotkeys while gaming, for triggering recording and streaming shortcuts, for driving desktop applications from inside VR, and for building per-title mapping sets that follow the way they actually play.

Mapping Examples

TriggerOpenVR2KeySPACE

GripOpenVR2KeyCTRL + R

Button AOpenVR2KeyF9

ChordOpenVR2KeyCTRL + SHIFT + M

Illustrative examples only — every mapping is defined by you inside SteamVR bindings and OpenVR2Key.

PROCESS

How OpenVR2Key Works

SteamVR handles the physical controller binding. OpenVR2Key handles the keyboard mapping. Keeping those two layers separate makes the workflow easier to understand and troubleshoot.

STEP 01

SteamVR Reads the Controller

SteamVR detects the physical input from your VR controller and applies the binding you created for OpenVR2Key.

Input: Trigger, Grip, Button, Joystick Click or Chord

STEP 02

The Binding Fires an Action

That SteamVR binding triggers one of OpenVR2Key's action slots. This is the bridge between the physical controller and the utility.

Layer: SteamVR Controller Binding

STEP 03

OpenVR2Key Loads the Key Map

OpenVR2Key looks up the keyboard key or key combination you assigned to that action slot.

Example: Action 3 → CTRL + R

STEP 04

Windows Receives the Keystroke

OpenVR2Key sends the simulated keyboard event to Windows, where the focused application or a global hotkey can react.

Output: F9, SPACE, CTRL + R, etc.

Flow: VR Controller → SteamVR Binding → OpenVR2Key Action → Keyboard Mapping → Windows Application

CAPABILITIES

OpenVR2Key Features

The building blocks that make VR-to-keyboard mapping practical on a Windows PC.

SteamVR Controller Input

Actions are read through the SteamVR input system, so anything SteamVR recognises can be bound.

Keyboard Key Simulation

Each action produces a simulated key press that Windows treats like real keyboard input.

Custom Key Mapping

You choose the output for every slot, from a single function key to a modifier-heavy shortcut.

Key Combinations

Ctrl, Alt, Shift and Win can be combined with a main key to reproduce application shortcuts.

Input Chords

Bind two controls together in SteamVR so a shortcut only fires when both are held.

Per-Application Configurations

Keep separate mapping sets and load the one that suits the title or workflow you are running.

SteamVR Controller Bindings

The binding UI stays in charge of the physical layout, so hardware changes need no remapping.

Windows Hotkey Workflows

Drive capture tools, overlays, media controls and desktop shortcuts without leaving VR.

SIGNAL PATH

From VR Input to Keyboard Output

This view separates the workflow into three clean stages so you can see exactly what SteamVR does, what OpenVR2Key does, and what Windows finally receives.

01 · VR INPUT

Physical Controller Input

A controller button, trigger, grip, joystick click, or chord is recognized by SteamVR.

Examples:
Trigger
Grip
Button A / B
Joystick Click
Custom Chord

02 · OPENVR2KEY ENGINE

Action → Key Mapping

The SteamVR-bound action reaches OpenVR2Key, which matches it against the keyboard command you configured.

Internal flow:
Detect Action → Find Mapping → Prepare Output

03 · KEYBOARD OUTPUT

Simulated Windows Key Event

OpenVR2Key sends the configured key or shortcut to Windows as a simulated keyboard event.

Examples:
SPACE
F9
CTRL + R
CTRL + SHIFT + M

Important: SteamVR chooses the action. OpenVR2Key chooses the keyboard output.

BENEFITS

Why Use OpenVR2Key?

Realistic reasons people add a VR-to-keyboard bridge to a SteamVR setup.

Control Games from VR

Send the keys a title already listens for without reaching outside the play space, which suits seated and room-scale sessions equally.

Trigger Global Hotkeys

Capture tools, overlays and media utilities that register system-wide hotkeys can respond to a controller press while another window has focus.

Reduce Keyboard Reach

Blind typing in a headset is slow and error prone. Moving the important keys onto a controller removes most of that friction.

Create Custom VR Shortcuts

Build a small personal shortcut set for the actions you repeat most often, then refine it as your setup changes.

Use Button Combinations

Requiring two controls at once keeps a rarely used command out of the way during normal play.

Build Per-Game Mapping Workflows

Keep one mapping set per title or task so switching context does not mean rebuilding everything from scratch.

STEP BY STEP

How to Set Up OpenVR2Key

Complete the SteamVR binding first, then configure the keyboard output in OpenVR2Key. Start with one simple button-to-key mapping before building more complex shortcuts or chords.

STEP 01

Download OpenVR2Key

Use a trusted project source or the original archived release page.

STEP 02

Extract & Launch

Extract the application to a normal Windows folder and start OpenVR2Key.

STEP 03

Start SteamVR

Confirm your headset and controllers are visible to SteamVR before configuring bindings.

STEP 04

Add to Steam if Needed

If OpenVR2Key is missing from bindings, add it to Steam as a non-Steam application.

STEP 05

Enable VR App Context

Where the Steam interface provides the option, include or mark the entry as a VR application.

STEP 06

Open Controller Bindings

Open SteamVR controller bindings and select OpenVR2Key as the application to configure.

STEP 07

Bind Controller Actions

Assign controller buttons, grips, triggers, or chords to OpenVR2Key action slots.

STEP 08

Map Actions to Keys

Inside OpenVR2Key, assign a keyboard key or key combination to each action you use.

STEP 09

Test the Mapping

Keep SteamVR and OpenVR2Key running, then test each mapping in the target game or Windows app.

Recommended first test: bind one controller action to an OpenVR2Key slot, map that slot to F9, and verify that the key is received before creating additional mappings.

Configuring SteamVR Controller Bindings

SteamVR controller bindings and OpenVR2Key mappings are two different things, and mixing them up is the single most common source of confusion. SteamVR decides which physical control counts as an action. OpenVR2Key decides which keyboard output that action produces.

Inside the SteamVR binding interface you select OpenVR2Key from the list of applications, then attach controls to the action slots it exposes. A trigger pull, a grip squeeze, a face button, a joystick click, or two controls held together as a chord can all be assigned. Custom bindings can be saved, edited later, and replaced without touching your keyboard mappings at all.

This separation is genuinely useful. Swap to a different controller and you only need to rebuild the SteamVR side. Change your mind about which shortcut a button should send and you only need to edit the OpenVR2Key side. If a control does nothing at all, check bindings first — an unbound action can never reach the mapping stage.

SteamVR Controller

SteamVR Binding

OpenVR2Key Action

Keyboard Mapping

REFERENCE

OpenVR2Key Key Mapping Guide

A key mapping connects an OpenVR2Key action to the Windows keyboard command you want to send. These examples are illustrative — the actual controller bindings and keys are chosen by you.

VR ACTION

Trigger

Keyboard output

SPACE

Simple game action

VR ACTION

Grip

Keyboard output

CTRL + R

Custom shortcut

VR ACTION

Button A

Keyboard output

F9

Tool or recording hotkey

VR ACTION

Button B

Keyboard output

ESC

Menu / cancel action

VR ACTION

Chord

Keyboard output

CTRL + SHIFT + M

Multi-key shortcut

VR ACTION

Joystick Click

Keyboard output

ALT + TAB

Desktop switching example

SteamVR Binding vs. OpenVR2Key Mapping

SteamVR Binding: decides which physical controller input fires an OpenVR2Key action.

OpenVR2Key Mapping: decides which keyboard key or shortcut that action sends to Windows.

Create Powerful VR Button Chords

A chord means two controls held together before an action counts as pressed. Instead of a single grip squeeze firing your shortcut, the binding waits until, for example, the left grip and the right trigger are both active at the same time.

The reason to bother is accidental activation. Grips and triggers get squeezed constantly during normal play, so any single-button shortcut attached to them will eventually fire when you did not intend it. Sending Ctrl + Shift + M to a voice chat client in the middle of a match is a small disaster that a chord quietly prevents.

Chords are configured on the SteamVR side, because SteamVR owns the physical layer. Once the chord exists as an action, OpenVR2Key treats it like any other slot and sends whatever keyboard output you assigned to it. Save chords for commands that are important, rarely used, or genuinely disruptive if triggered by mistake.

CHORD BUILDER

LEFT GRIP+RIGHT TRIGGER=CTRL + SHIFT + M

Both controls must be active before the keystroke is sent.

CONFIGURATIONS

Different Key Maps for Different VR Apps

Separate configurations keep each mapping set small and memorable. The examples below are illustrative and are not official defaults.

VR GAME A

Action-Oriented Layout

A simple profile can keep frequently used game actions on easy-to-reach controller inputs.

Example
Trigger → SPACE
Grip → R

SIMULATOR

Function-Key Layout

A simulator may benefit from direct access to function keys or panel shortcuts.

Example
Button A → F1
Button B → F2

MEDIA / TOOL

Utility Shortcut Layout

A media or capture workflow can reserve chords for shortcuts that should not fire accidentally.

Example
Grip + Trigger → CTRL + SHIFT + M

Tip: use clear configuration names so you can quickly identify which mapping set belongs to each game or workflow.

SUPPORT

OpenVR2Key Compatibility

What the utility expects from your system, described honestly.

Windows

Built as a Windows desktop utility. It runs alongside SteamVR rather than inside a headset app.

SteamVR

SteamVR must be running. It supplies the input system, the action slots and the binding interface.

VR Controllers

Controllers that SteamVR recognises and exposes in the binding interface can generally be bound.

Keyboard-Based Games

Titles that already respond to keyboard input are the natural fit, since the output is a key press.

Desktop Applications

Any Windows application listening for a shortcut can receive one, subject to which window has focus.

Global Hotkeys

Applications that register a system-wide hotkey respond most reliably from inside VR.

An important limitation. No claim is made here that every headset, every controller or every game will work. Behaviour depends on SteamVR recognising your hardware, on the action bindings you save, and on how the target application handles keyboard input. The reliable way to know is to test a harmless mapping first.

FIXES

Common OpenVR2Key Problems & Fixes

Conservative OpenVR2Key troubleshooting steps that rule out the usual causes first.

OpenVR2Key Does Not Detect Input

Confirm SteamVR is running and that your controllers are awake and tracked. Then reopen the SteamVR binding interface and check that an action slot really is attached to a physical control. An empty binding is silent, and looks identical to a broken install.

Key Press Does Not Work

Check which window had focus when you pressed the control. If the target only responds to its own window, the keystroke has to arrive while that window is active. Testing in a plain text editor tells you quickly whether the key is being sent at all.

OpenVR2Key Missing from SteamVR Bindings

Applications usually appear in the binding list once SteamVR has seen them run. Start the utility while SteamVR is active, and if it still does not appear, adding the executable to Steam as a non-Steam application is the common workaround.

Application Appears to Already Be Running

A previous instance may still be alive in the background or in the system tray. Close it there first, and if nothing is visible, check the task list for a leftover process before launching a new copy.

Wrong Key Is Triggered

This is nearly always two slots pointing at overlapping controls, or a chord whose components are also bound individually. Review the SteamVR binding for duplicates, then confirm each mapping in OpenVR2Key one slot at a time.

Controller Binding Does Not Save

Make sure you complete the save step inside the binding interface rather than closing the panel, and that you are editing a binding you are allowed to modify. Creating a fresh personal binding instead of editing a default one often resolves it.

Hotkey Works Only in Some Applications

Expected behaviour rather than a fault. Only shortcuts registered globally by the target application work regardless of focus. Everything else needs its window in front when the key arrives.

OpenVR2Key Does Not Start with SteamVR

Auto-start depends on how the entry was added to Steam and on your SteamVR startup settings. Review those options, and if automatic launch stays unreliable, starting it manually after SteamVR is the dependable fallback.

END TO END

Your OpenVR2Key Workflow

Every mapped press travels the same path, from a controller in your hand to an application on your desktop.

VR Controller

You press a bound control inside the headset.

SteamVR

The binding turns that press into a registered action.

OpenVR2Key Input Action

The action slot is received by the utility.

Key Mapping

The slot is matched to the key or combination you saved.

Windows Keyboard Event

A simulated keystroke is delivered to the system.

Game / Application

The focused or listening application reacts to it.

RESOURCES

OpenVR2Key Download & Resources

Where to look for OpenVR2Key downloads, documentation and background information.

This site does not host software. The buttons below are placeholders for the destinations you choose to link to, so that visitors are always sent to a source you have checked yourself.

Before you download

The original OpenVR2Key repository has been archived. Users should review the project status and release notes before downloading or installing software. Always obtain releases from the project's own source rather than from mirrors or repackaged archives, and treat any site offering an “official installer” with caution.

OpenVR2Key Project Status

The original OpenVR2Key repository was archived by its owner in May 2026. The project documentation states that its functionality is intended to transition toward BOLL’s VR Toolkit (BVRTK).

An archived repository stays readable and its existing releases remain available, but new development is not expected there. Nothing about that changes how the utility works today — it simply means you should check the project page for current status before relying on it for anything important, and keep an eye on where the maintainer has directed users next.

OpenVR2Key.com is an independent resource. We document setup, bindings, key mapping and troubleshooting so that the knowledge stays easy to find, and we link back to the original project rather than replacing it.

QUESTIONS

OpenVR2Key FAQs

Short, direct answers to the questions people ask most often about OpenVR2Key.

OpenVR2Key is a Windows utility for SteamVR, originally created by BOLL7708. It listens for VR controller actions registered through the SteamVR input system and converts them into simulated keyboard input on the desktop, so a controller press can produce a key or a full keyboard shortcut without you touching a keyboard.

It bridges VR input and Windows keyboard input. You bind controller actions in SteamVR, then assign a key or combination to each action inside OpenVR2Key. When the action fires, the mapped keystroke is delivered to Windows and handled by whichever application currently has focus or has registered a global hotkey.

The original project was published as a free, open-source utility with public releases. Because the repository is now archived, the accurate answer is to check the project page itself for the current licence and for which releases are still available before downloading anything.

Yes, and SteamVR is required rather than optional. OpenVR2Key uses the SteamVR input system, so SteamVR must be running and your controller actions must be bound through the SteamVR controller binding interface before any keyboard mapping can fire.

In two layers. SteamVR binds a physical control such as a trigger, grip, face button or joystick click to an OpenVR2Key action slot. OpenVR2Key then stores which keyboard key or combination belongs to that slot, and simulates it whenever SteamVR reports the action.

It was built as a Windows desktop application and generally behaves the same on modern Windows versions, including Windows 11, provided SteamVR runs normally. Since the project is archived, no guarantee can be offered, so test a harmless mapping before depending on it.

Yes. A mapping is not limited to a single key. Modifier keys such as Ctrl, Alt, Shift and Win can be combined with a main key so that a controller press reproduces the same shortcut a game or desktop application already listens for.

A chord is a controller combination that requires two controls to be active together before the action counts as pressed, such as holding a grip while pulling a trigger. Chords are configured on the SteamVR binding side and are useful for commands that must not fire by accident.

Yes. Modifier combinations are one of the main reasons people use the utility, because most useful desktop shortcuts include at least one modifier. A single controller action can output something like Ctrl + Shift + M as one complete keystroke.

It can control games that already respond to keyboard input, since the output is an ordinary simulated key press. Whether the game reacts depends on it having focus at that moment and on the key being one the title actually listens for.

Yes, when the target application has registered its shortcut globally with Windows. Those hotkeys respond regardless of which window is in front, which makes them the most reliable choice for capture tools, overlays and voice chat clients.

Start with SteamVR: confirm it is running and that the controllers are awake and tracked. Then reopen the binding interface and verify that an action slot is actually attached to a physical control. An unbound action produces no input at all and is easy to overlook.

Check focus first. A keystroke sent while a different window is active goes to that window instead of your intended target. Test the mapping in a plain text editor to confirm the key is being produced, then look at whether the target application uses a global hotkey.

Applications normally appear in the binding list after SteamVR has seen them run. Launch the utility while SteamVR is active, and if it still does not show up, adding the executable to Steam as a non-Steam application is the usual way to make it visible.

No such promise can be made. Support depends on SteamVR recognising your controller and exposing its controls in the binding interface. Widely supported controllers are generally straightforward, but unusual hardware may expose fewer inputs or behave differently.

Yes. Keeping separate configurations for different titles or workflows is a common way to use the utility, so a simulator can use function keys while another game uses movement keys. You load the configuration that matches what you are running.

Yes. Without SteamVR there is no input system delivering controller actions, so nothing reaches the mapping stage. The utility is a bridge rather than a standalone driver, and it has nothing to listen to when SteamVR is closed.

It can in many setups, depending on how the entry was added to Steam and on your SteamVR startup settings. If automatic launch turns out to be inconsistent, starting the utility manually once SteamVR is up remains a dependable fallback.

Only from the project’s own source. Avoid mirrors, repackaged archives and any site advertising an unofficial installer. Because the repository is archived, read the release notes and the project status before installing, and scan anything you download.

The original repository was archived by its owner in May 2026, and the project documentation indicates that its functionality is intended to move toward BOLL’s VR Toolkit (BVRTK). Existing releases remain readable and downloadable, but new development is not expected in the archived repository.

SteamVR bindings decide which physical control counts as an action. OpenVR2Key mappings decide which keyboard output that action produces. Keeping the two separate means you can change a controller layout without redoing your shortcuts, and the reverse.

It is designed around key combinations, meaning modifiers plus a main key sent together as one keystroke. That covers the vast majority of application shortcuts. It is not intended as a general macro recorder for long timed sequences of separate presses.

SIGNAL READY

Turn VR Input Into the Commands You Need

Explore OpenVR2Key setup guides, SteamVR controller bindings, keyboard mapping, troubleshooting, and project resources.

OpenVR2Key.com

Independent OpenVR2Key information, setup, mapping, and troubleshooting resource.

OpenVR2Key.com is an independent informational website and is not the official website of BOLL7708, Valve, SteamVR, or associated hardware/software companies. All product names, trademarks and registered trademarks are the property of their respective owners.

Scroll to Top