Korean Byte Calculator
Compare how many bytes Korean text takes in UTF-8 versus EUC-KR at a glance.
The EUC-KR value is an approximation. Verify in the actual input box before an important submission.
How do UTF-8 and EUC-KR differ?
The bytes a Korean character takes depend on the encoding. In the web-standard UTF-8, Korean is 3 bytes; in the older EUC-KR, it is 2 bytes. English and digits are 1 byte in both. This tool measures the same text against both so you can meet any limit.
When to use it
- Legacy boards/forms: check whether an input with an EUC-KR ('Korean = 2 bytes') limit is exceeded.
- SMS copy: gauge the single/long message boundary at the EUC-KR 90-byte (45 Korean chars) basis.
- DB/API design: check the required byte length in both UTF-8 and EUC-KR depending on storage encoding.
Things to note
- The EUC-KR count is an approximation based on the completed-form set; some archaic Hangul or special characters may differ from real stored bytes.
- Emoji and some special characters can't be represented in EUC-KR and may break on systems using that encoding.
- Check which encoding a limit refers to in the posting or guide first.
Your text is measured only in your browser and is never sent to or stored on a server. Nothing remains after the calculation.
Read the Privacy Policy →Frequently asked questions
How many bytes is Korean in UTF-8?
In UTF-8, a Korean character is 3 bytes and English/digits are 1 byte. In EUC-KR, Korean is 2 bytes. So the same text totals differently depending on the basis.
Why show both bases together?
Most modern services use UTF-8, but older boards and SMS systems sometimes use the EUC-KR (Korean = 2 bytes) basis. When you're unsure, seeing both values lets you meet the limit safely.
How many bytes is a single SMS?
A domestic single SMS is usually based on EUC-KR 90 bytes (45 Korean or 90 English characters); beyond that it becomes an LMS (long message). Confirm the exact limit with your sending provider.
Is my input stored?
No. Calculation happens only in your browser and your text is never sent to or stored on a server.