# How to deal with keyboard layouts?

**URL:** <https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539>\
**Category:** C++\
**Tags:** unreal-engine, CPP, Blueprint, question\
**Created:** [May 11, 2025, 10:55pm UTC](https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539 "2025-05-11T22:55:57Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adamen111](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Adamen111](https://forums.unrealengine.com/u/Adamen111)\
**Post date:** [May 11, 2025, 10:55pm UTC](https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539/1 "2025-05-11T22:55:57Z")

</div>

# Keyboard Localization Issue in Unreal Engine

Hello,

I have an issue that’s driving me crazy, and its keyboard localization for input handling.

**I am a beginner in Unreal Engine (love it so far), so please go easy on me.**

## The Problem

Some countries have different keyboard layouts.

Problematic layouts are for example: **QWERTZ, AZERTY, QZERTY, Dvorak, Colemak and more**

Let’s take the number keys on top of the keyboard as an example. Here is a list of how the `1-0` keys are localized in some countries:

| Country | Key Layout |
| --- | --- |
| **Czech** | `+ěščřžýáíé=´` |
| **Slovak** | `+ľščťžýáíé=´` |
| **Hungarian** | `0'-.,§!"+%/=` |
| **Slovenian** | `+čščđžqwertz` |
| **Croatian** | `+čćžđšđžćč-'` |

When using these localizations, Unreal Engine mappings for 1-0 keys stop working as expected.

### Blueprint with Enhanced Input

- You have **InputActions** for your actions.
- You have an **InputMappingContext** with these actions set to keys.
- If you set an input action within the context to a key like `1`, it does not work on localized keyboards.

### C++ Key Binding

The same issue occurs with C++ key bindings. For example:

```cpp
InputComponent->BindKey(EKeys::One, IE_Pressed, this, &AGamePlayerController::LogNumKey<1>());

```

This works with English keyboards but not with the localized variants mentioned above.

## Possible (but not ideal) solution

There is an easy way to fix this using a plugin called [Loonyware - Keyboard Layout-Independent Input](https://www.fab.com/sellers/loonyware). However, this is a paid plugin and adds another dependency to your project. I wish to avoid using it and fix it via native Unreal Engine functionality.

I have tried finding a solution for this issue, but I could not find any useful resources or information on the matter.

Please help me out. I am sure there must be a easy way to do this that I am missing.

Thank you

---

<div class="post-metadata">

**Author:** ![nande](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/nande/32/1057698_2.png) [@nande](https://forums.unrealengine.com/u/nande)\
**Post date:** [May 11, 2025, 11:50pm UTC](https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539/2 "2025-05-11T23:50:36Z")

</div>

i’ve been using dvorak for more than 15 years. i’d also would like to know.  
i’m not entirely sure i haven’t dived into this myself yet.

with the enhanced input system you can have different imcs depending on the layout. you might need to specify each layout separately though.

> [@How to change between multiple Input Mapping Contexts?](https://forums.unrealengine.com/t/how-to-change-between-multiple-input-mapping-contexts/1146354/2):
>
> look in the example third or first person. They assign a mapping context on begin play. You can just copy paste those couple nodes to do the same thing. One confusing thing though is that multiple mapping context can be active simultaneously. They have a priority that you can assign. But you might want for only one to be active. In that case, you may want to use Remove Mapping Context:

---

<div class="post-metadata">

**Author:** ![L.F.A](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/l.f.a/32/1194525_2.png) [@L.F.A](https://forums.unrealengine.com/u/L.F.A)\
**Post date:** [May 12, 2025, 2:33am UTC](https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539/3 "2025-05-12T02:33:42Z")

</div>

What if you map to num pad keys and give player the option to remap the other keyboard keys?

Have you seen these websites?

[Keyboard Layout Info](https://kbdlayout.info/)

[GitHub - bscotch/keyboard-layouts: Data related to keyboard layouts and virtual keys, for use in mapping inputs for games.](https://github.com/bscotch/keyboard-layouts?tab=readme-ov-file)

---

<div class="post-metadata">

**Author:** ![weston\_josaf](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@weston\_josaf](https://forums.unrealengine.com/u/weston_josaf)\
**Post date:** [September 26, 2025, 11:34am UTC](https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539/4 "2025-09-26T11:34:12Z")

</div>

Keyboard localization differences really highlight how input handling can be inconsistent across regions. For testing, especially with repeated keystrokes like the spacebar, tools such as [Spacebar Clicker](https://space-bar-clicker.github.io/) can show how various layouts respond in practice. It becomes clear how much reliability depends on proper mapping rather than layout quirks.

---

<div class="post-metadata">

**Author:** ![ShadowBr0kerz](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/shadowbr0kerz/32/1201558_2.png) [@ShadowBr0kerz](https://forums.unrealengine.com/u/ShadowBr0kerz)\
**Post date:** [September 10, 2026, 12:30pm UTC](https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539/5 "2026-09-10T12:30:43Z")

</div>

practical options: ship an IMC per layout family and pick at boot, or simpler, let players remap. most games do the second because you cant hand-cover dvorak, colemak, azerty number rows and laptopless numpads. defaults will always be wrong somewhere, remapping solves all of them at once.

Advanced Input Rebinding System, a runtime key-rebinding system for Unreal Engine 5: capture + conflict detection + save profiles: [Advanced Input Rebinding System](https://www.fab.com/listings/e8a77976-b4d4-4e8f-a4b4-c6a71a98554d). on sale ($32.71).

---

<div class="post-metadata">

**Author:** ![jameswatsonn](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jameswatsonn](https://forums.unrealengine.com/u/jameswatsonn)\
**Post date:** [September 10, 2026, 5:50pm UTC](https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539/6 "2026-09-10T17:50:47Z")

</div>

i’m not sure i haven’t dived into this myself yet

---

<div class="post-metadata">

**Author:** ![L.F.A](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/l.f.a/32/1194525_2.png) [@L.F.A](https://forums.unrealengine.com/u/L.F.A)\
**Post date:** [November 4, 2026, 8:50am UTC](https://forums.unrealengine.com/t/how-to-deal-with-keyboard-layouts/2504539/7 "2026-11-04T08:50:35Z")

</div>

I only tested the first plugin mentioned in this post and it works.  
[Keyboard Layout-Independent Input | Fab](https://www.fab.com/listings/97745184-2b76-48c6-b29e-dc8d4f1df14b)

The setup is simple and it comes with example projects, there are just two nodes to “convert to” or “convert from” US QUERTY. A custom Input remap widget is also provided and it works with UE4 and UE5 systems (Legacy and Enhanced input).

For Windows users wanting to test it out, just add a language, let’s say German, then add the German QWERTZ keyboard layout and change the language to current (pressing Windows key + space). The physical keys are preserved and the conversion nodes do the job of remapping to the correspondent physical key in whatever language-keyboard you chose.

With the help of that plugin, if your game was shipped using US QUERTY assigning the Y key to an input action, any player using a German-QUERTZ keyboard would see that action assigned to the Z key, the correspondent physical position instead of the original Y key at the bottom left of the GE-QWERTZ keyboard, without any setup. That means not only the physical position is preserved, the key display is also correct, let’s say, especial characters are recovered and properly displayed. This also avoids the awkward WASD remapping from US-QUERTY that would become scattered in other keyboard layouts, having the intended WASD assuming very different physical positions. To make matters worse, if your game had an default input key remapping widget, the user would see the wrong characters being displayed, those from US QWERTY, making inconvenient to play your game.

The biggest difference happens on the right side of the keyboard, those keys with especial characters closer to the Enter key.
