Keyboard Typing the Wrong Letters

Match the symptom to a useful first check

Use a blank document or a plain text field and harmless sample text. Repeat the same short sequence in a second application. Record the selected input source and any keyboard profile so you can compare one change at a time.

• A and Q, or Y and Z, appear swapped consistently: compare the active layout with the legends on your keycaps. QWERTY, AZERTY and QWERTZ assign different letters to some of the same positions.
• A group of letter keys produces numbers: look for small number legends and check the keyboard's embedded numeric keypad or Num Lock state.
• Quotes, @, punctuation or accented letters differ: check the exact layout variant and active input method, including international or dead-key layouts.
• Characters change only in one app, game or remote session: check that context's input source, shortcuts, text replacement and remapping before changing the whole system.
• A key is missing, repeats unexpectedly or fails intermittently across apps: collect a separate event test and compare another keyboard or connection. That pattern needs more than a layout change.

Compare the key event with the text you receive

Open the keyboard tester and start its capture area. Press the suspect key alone, release it, then repeat slowly. Read the displayed event key and code alongside the highlighted position. Stop capture before using normal browser shortcuts or changing system settings.

The browser's code describes a key position using identifiers such as KeyQ. Its key value reflects the active layout and modifiers. On an AZERTY layout, a key reported as code KeyQ can produce key a. That combination alone does not show a broken switch. MDN documents this distinction in the sources below.

An input method can compose or replace text after several key events. Compare its final text in a normal editor too; a key history is not a transcript of the committed text. A missing browser event also cannot identify whether the cause is hardware, focus, an operating-system shortcut or software interception.

Choosing ANSI or ISO changes the tester's physical diagram. Choosing a website language changes its interface. Neither changes your operating system's input layout. Select the diagram that resembles your hardware and change the input source in the system when the character mapping is wrong.

• Open the keyboard tester

Check the active layout in Windows

Microsoft documents input layouts separately from the Windows display language. You can keep the interface language you prefer while selecting the layout that matches your keyboard.

1. Select the input-language indicator in the taskbar and choose the intended keyboard layout. Windows + Space also cycles through installed layouts.
2. If the layout is missing, open Settings → Time & language → Language & region. Open the relevant language's menu, choose Language options, and inspect Installed keyboards. Add the specific layout you need.
3. Return to your plain text sample and repeat the same keys. Check punctuation as well as letters; two layouts can share most letters while assigning symbols differently.
4. After confirming the replacement works, remove an unwanted layout from that language's options if you no longer use it. Keep any layouts required by other users or tasks.

These steps follow Microsoft's current Windows 11 guidance. Labels can differ by version. Check the selected input source in the affected application or remote session again if the problem returns when you switch contexts.

Check the input source and Keyboard Viewer on Mac

1. Open Apple menu → System Settings → Keyboard. Under Text Input, choose Edit and inspect your input sources.
2. Select the source that matches the characters you intend to type and inspect its layout preview.
3. Enable Show Input menu in menu bar if needed, then use that menu to select the intended source and open Show Keyboard Viewer.
4. Compare the viewer with a short sample in a text editor; Shift and Option reveal alternate characters. If the viewer shows the expected character but one application inserts something else, check that app's replacements, shortcuts or input settings.

Apple's Input Sources settings and Keyboard Viewer pages explain these controls. A physical diagram and a software input source describe different parts of the setup; an ISO-shaped keyboard can still be used with several language layouts.

Check Num Lock, modifiers and keyboard profiles

Some compact laptops reuse letter positions as a numeric keypad. Samsung's support guidance identifies Num Lock as a cause of letters turning into numbers on such models. Look for the keyboard's Num Lock marking and follow the model manual; some keyboards require Fn with that marked key. There is no universal Fn shortcut for every laptop.

If symbols or capitals appear unexpectedly, release both Shift keys, check Caps Lock, and inspect any modifier remapping or accessibility setting you intentionally use. On a programmable keyboard, compare the active layer or profile with the expected one. Save or note your configuration before changing it.

Retest the same sample after each change. If only the numeric keypad changes behavior, that may be the normal Num Lock function rather than an embedded letter-key layer.

Separate composition, text replacement and remapping

When an input method is active, allow the composition to finish before judging the result. An accent key or a sequence used to build one character need not insert a standalone character at every step. If you intend plain Latin text, temporarily choose the matching direct-input source and repeat the sample.

Compare a local editor with the affected browser field. If only one field differs, inspect that app's text replacement, extensions, game bindings or remote-desktop mapping. Temporarily pause a relevant remapping profile only if you know how to restore it; record whether the symptom follows that change.

If the mismatch follows one keyboard across applications, compare another keyboard on the same system. If possible, try the affected keyboard on a second system with the same intended layout. These comparisons help isolate a device, profile or system-specific pattern; no single browser result proves the hardware is healthy or faulty.

Retest and keep a useful record

Keep a short before-and-after note: physical key legend, browser key/code when available, committed character, active input source, keyboard model and affected app. Include whether the behavior was consistent or intermittent. This is more useful for support than a claim that the keyboard is simply wrong.

• If the mapping now matches, repeat letters, numbers and punctuation in both applications.
• If presses are absent rather than mapped to the wrong character, follow the unresponsive-key checklist.
• If one press appears to produce repeated inputs, use the key chatter tool to review event timing, then compare the same behavior in another app. It cannot certify switch damage.
• If the same problem persists across known-good settings and another system, share the recorded examples with the manufacturer or repair service.

• Retest keyboard input
• Inspect repeated key inputs
• Troubleshoot unresponsive keys