Byte Calculator
See how many bytes your text takes and stay within submission limits.
What is a UTF-8 byte?
English, Korean, and emoji can take different numbers of bytes when stored. This tool uses the browser's TextEncoder to calculate against the web-standard UTF-8. In UTF-8, English and digits are 1 byte, Korean is 3 bytes, and emoji are 4 bytes or more.
When to use it
- Application fields: check whether a cover-letter field with a limit like “within 2,000 bytes” is exceeded.
- Notification & push copy: trim messages with length limits, such as app push notifications.
- DB field design: check real stored bytes before deciding a VARCHAR length.
Things to note
- If a service uses the EUC-KR basis (2 bytes per Korean character), it may differ from this tool's UTF-8 count (3 bytes per Korean character).
- Check which encoding a byte limit refers to in the posting or guide first.
- Before an important submission, verify once more in the actual input box.
Frequently asked questions
How many bytes is a Korean character?
In UTF-8, a Korean character is usually 3 bytes, and English/digits are 1 byte. In services using the EUC-KR basis, Korean may be counted as 2 bytes. This tool calculates against the web-standard UTF-8.
Why do UTF-8 and EUC-KR counts differ?
Because they store characters with different encodings. UTF-8 stores Korean as 3 bytes, EUC-KR as 2 bytes. Since forms and boards differ, it's good to confirm which encoding a “byte limit” refers to.
Can I use this for SMS byte limits?
You can use it as a reference. SMS in Korea is often based on a 90-byte EUC-KR limit (about 45 Korean characters), so also check your sending provider's guidance for the exact limit.
How many bytes is an emoji?
An emoji usually takes 4 bytes in UTF-8, and combined emoji can take more. In fields with tight byte limits, it's safer to reduce emoji use.
Is my input stored?
No. Calculation is done only with the browser's TextEncoder; the text you enter is never sent to or stored on a server.