Which system
This page follows the Revised Romanization of Korean, the system notified by the Ministry of Culture and Tourism in 2000. Vowels such as eo and eu, and consonants with position-based g/k, d/t, b/p forms, match that system.
Korean writing toolkit
Korean romanizer
Convert Hangul into the Revised Romanization of Korean. The converter applies base letter mappings plus common sound changes such as liaison, nasalization, and palatalization (d/t before i).
Input
Hangul text
Output
Romanization
Useful cases
Use it for draft place names, personal-name sketches, and UI copy where RR is expected. Always double-check official romanizations for legal names, passports, and road signs — institutions may keep an established spelling.
Privacy
Conversion runs in the page. The text is not uploaded to modu.tools.
Limits
The converter covers common sound-change cases used in official examples (liaison, l/n assimilation, nasalization, and palatalization). It does not apply n-insertion, so a word that gains an extra n sound in speech is romanized without it. It also keeps h after k, t, and p, as RR does for nouns (Mukho), so verb forms need a manual check.
This romanizer follows the Revised Romanization of Korean (Ministry of Culture notice). It converts by pronunciation context rather than letter-by-letter substitution, including common sound changes. All processing stays in the browser.
Verified examples
| Input | Output | Rule in play |
|---|---|---|
| 신라 | silla | n+l → ll |
| 대관령 | daegwallyeong | pronunciation assimilation |
| 같이 | gachi | palatalization |
| 광희문 | gwanghuimun | ㅢ written ui |
| 압구정 | apgujeong | tensification not written |
| 묵호 | mukho | ㅎ kept after ㄱ in that pattern |
Good fits
- English business cards and venue addresses
- Shipping labels and hotel booking fields
- Rough pronunciation hints for teammates
- ASCII-friendly slugs when you still want RR as a base
When not to paste blindly
Personal names. The standard treats given names differently from ordinary words. Split surname and given name, then verify customary spellings (many families keep established Latin forms).
Administrative suffixes. Units like -gu use a hyphen and suppress some boundary changes. Split the stem and the unit, convert, then join with a hyphen.
Context-heavy changes. Some words need part-of-speech knowledge (extra n insertion, ㅎ behavior). Official documents should be checked against the gazette text, not only this output.
Established brands. Existing Latin trademarks win over fresh conversion.
Treat the result as a draft: capitalize, hyphenate and proof against the authority that will print the string.
Review workflow for shipping strings
- Decide whether the string is a place name, a personal name, or ordinary vocabulary.
- Convert Hangul-only segments; leave existing Latin trademarks untouched.
- Compare against a short allowlist of known sound-change examples (신라→silla, 같이→gachi).
- Apply capitalization and hyphens required by your style guide or map vendor.
- For anything legal or governmental, cross-check the official romanization text rather than trusting a single tool pass.
Revised Romanization is a public standard, not a brand voice. Product marketing teams often keep legacy spellings for recognition. Engineering teams building search indexes may want a second, looser key. This page optimizes for the standard spelling rules, not for fuzzy search keys.
Because non-Hangul passes through, mixed strings like Room 1204, 압구정로 only transform the Hangul run. Clean spaces and punctuation after conversion if your downstream schema is picky.
Engineering uses versus editorial uses
Search indexes sometimes store a romanized secondary key. Do not assume that key equals the marketing spelling on a billboard. Keep two fields if you need both recall and brand fidelity. For file names and URL slugs, decide whether you want strict Revised Romanization or a simplified ASCII fold; this tool targets the former.
Batch conversions still deserve spot checks on boundary cases involving ㄹ/ㄴ assimilation and ㅎ. Automated pipelines should unit-test a fixture table rather than trusting a single online pass forever.
FAQ
Can I put this output on a passport?
Use it as a draft only. Personal names often follow customary spellings and may ignore some sound-change rules. Follow the passport authority guidance.
Why is the first letter lowercase?
The tool cannot tell common nouns from proper nouns, so it emits lowercase. Capitalize place and personal names yourself.
Why is 압구정 Apgujeong instead of Apkkujeong?
Revised Romanization does not reflect tensification in spelling. That result is expected.
What happens to non-Hangul?
Latin letters, digits, spaces and punctuation pass through. Only Hangul syllables are converted.