Korean/English Typo Fixer
Fix text typed in the wrong keyboard layout.
Type text broken by a wrong keyboard layout to fix it in real time.
Result
-
Please enter some text.
What is this tool?
The Korean/English typo fixer restores text that got garbled (e.g. gksrmf) because the keyboard was in the wrong input mode, converting it back into the intended Korean text (한글). It can also convert Korean text into the English keystrokes you would type on a 2-beolsik layout. Everything runs in your browser, so nothing you type is sent to a server.
How it works
Each character is mapped to a Hangul jamo (initial/medial/final) using the 2-beolsik keyboard layout, then the jamo are composed into syllables in initial + medial + final order. Double consonants (Shift), compound finals, and diphthongs are handled by the standard composition rules.
e.g. gksrmf → 한글, dkssud → 안녕. The Korean → English direction reverses this process.
The 2-beolsik keyboard mapping table
This tool follows the standard 2-beolsik keyboard layout exactly. The consonant column handled by the left hand and the vowel column handled by the right hand are fixed, so knowing the mapping below lets you predict which letter comes from which key.
| Key | Jamo | Key | Jamo |
|---|---|---|---|
| q | ㅂ | k | ㅏ |
| w | ㅈ | l | ㅣ |
| e | ㄷ | h | ㅗ |
| r | ㄱ | j | ㅓ |
| a | ㅁ | n | ㅜ |
| s | ㄴ | m | ㅡ |
| d | ㅇ | y | ㅛ |
| f | ㄹ | u | ㅕ |
| g | ㅎ | b | ㅠ |
Shift-combined keys produce double consonants (Q→ㅃ, W→ㅉ, E→ㄸ, R→ㄲ, T→ㅆ); the rest work without Shift. This tool's conversion logic keeps this exact same mapping as a constant in code, maps each input letter to its jamo, then composes syllables using initial/medial/final rules.
Common typo patterns, verified
Here are a few garbled strings that commonly result from a missed input-mode switch, verified against their intended meaning.
| Input | Intended Korean | Breakdown |
|---|---|---|
| dkssud | 안녕 (hello) | d(ㅇ)+k(ㅏ)+s(ㄴ)+s(ㄴ)+u(ㅕ)+d(ㅇ) → 안+녕 |
| gksrmf | 한글 (Hangul) | g(ㅎ)+k(ㅏ)+s(ㄴ)+r(ㄱ)+m(ㅡ)+f(ㄹ) → 한+글 |
| tkfkdgo | 사랑해 (I love you) | t(ㅅ)+k(ㅏ)+f(ㄹ)+k(ㅏ)+d(ㅇ)+g(ㅎ)+o(ㅐ) → 사+랑+해 |
Limits — why bidirectional conversion isn't always unambiguous
Because this tool mechanically applies the standard 2-beolsik mapping, it has a couple of structural limits. First, feeding an already-correct English word (like "hello") through the "English keys → Korean" direction produces a meaningless Hangul combination — a person can tell from context that the input was really English, but this tool converts character by character with no way to tell whether the input is genuinely garbled Korean or a normal English word. Second, while "Korean → English keys" always resolves to one answer, the reverse direction can be ambiguous when a consonant follows a final consonant (batchim): it isn't always clear whether that letter is the next syllable's initial consonant or part of a compound final for the current syllable, so the result can differ from what the person actually intended. If a conversion looks off, check the original text and manually fix the parts that need it.
When is this useful?
- You typed into the wrong app without switching input mode and got garbled text
- You want to decode garbled text someone sent by mistake
- You want to preview which keys to press on a 2-beolsik layout