This article is also available in:

Map Inputs to Keyboard Actions

Keyboard actions can send letters, numbers, function keys, arrows, modifiers, navigation keys, punctuation, and supported media keys. You can map one key to one trigger or create a simultaneous key combination.

Before you begin

Load an editable profile.
Choose a safe application, such as an empty text document, for the first test.
Make sure the target game or application accepts simulated keyboard input.

Map one keyboard key

Open Mapping and confirm the intended profile is active.
Select Add actions.
Select Keyboard.
Select the key you want PlayAbility to send.
Select the Add button showing the number of selected actions.
On the new row, select Select a trigger.
Choose an existing compatible trigger, or select Create a new trigger + and configure one.
Select an Action Mode:
- Default holds the key while the trigger remains active.
- Toggle alternates between holding and releasing the key.
- Short Press sends a 100 ms key press.
- Long Press sends a 300 ms key press.
- Double Press or Triple Press sends repeated quick presses.
Select Save.

Use Default for controls that must be held, such as movement. Use Short Press for a single action such as jump, reload, or menu confirmation.

Create a keyboard combination

Use a combo when one trigger should press several keys at the same time, such as Ctrl+C or Alt+Tab.

Select Add actions, then select Keyboard.
Select every key required by the combination.
Select Add as Combo.
On the resulting combo row, select Select a trigger.
Choose or create the trigger.
Select the action mode and then select Save.

Selecting the regular Add button creates separate mapping rows. It does not create a key combination.

Verify keyboard output

Turn on Main Output using PlayAbility's play/pause control.
Confirm that Keyboard Out is active in the Controls area.
Focus the safe test application.
Activate the trigger once.
Confirm that the expected key or combination is received and then released.
Test the mapping in the target game or application.

Keyboard actions do not depend on the virtual-gamepad driver. A virtual-gamepad alert does not by itself prevent keyboard output.

Troubleshooting and limitations

The mapping responds but no key is received

Confirm the intended profile is active.
Turn on Main Output and Keyboard Out.
Check whether foreground-app rules are blocking effective output.
Focus the target application before activating the trigger.
Test a simple letter in a text field to isolate an application-specific problem.

A shortcut does not work

Confirm that all required modifier keys are part of the same combo.
Recreate the output with Add as Combo, not as separate rows.
Try Short Press or Long Press if the application requires a distinct press duration.
Some applications use low-level or raw input and may reject simulated keys.

A key remains held

Run Release All. If the mapping uses Toggle, activate it again or change it to Default or a press mode.

Turning off Keyboard Out or Main Output also releases keyboard keys that PlayAbility is holding.

The original physical key also reaches the game

Mapping a physical key does not normally block that original input. Mute input is a separate, opt-in Windows feature. It uses a low-level hook, may not work with Raw Input, and may be flagged by anti-cheat software. Review the dedicated mute-input safety guide before enabling it.

The wrong character appears

PlayAbility sends keys, while the operating system and application apply the active keyboard layout. Check the selected layout and test the key in a text field.

A system shortcut has an unexpected effect

Combos containing Windows, Alt, Control, or function keys can invoke operating-system or application commands. Configure and test them outside a game first, and avoid mapping a shortcut that could lock, close, or interrupt the session unintentionally.

Updated on: 30/07/2026

Was this article helpful?

Thank you!