jakup

Characters (with spaces)

0chars

Without spaces 0 · 0 pages (200 chars)

Details

With spaces

0chars

Without spaces

0chars

Words

0

Sentences

0

Paragraphs

0

Lines

0

Pages (200)

0pages

Est. reading 0s · speaking 0s silent 500 cpm · spoken 350 cpm

Character types

Korean

0

Latin

0

Digits

0

Spaces

0

Symbols

0

Bytes

UTF-8 web standard0 bytes
EUC-KR Korean legacy0 bytes
UTF-16 0 bytes

Korean forms that say "within N bytes" usually count in EUC-KR — a Korean character = 2 bytes, letters/digits = 1 byte. In UTF-8 a Korean character counts as 3 bytes.

Character / byte limit

chars

Enter a target to see progress and how much is left or over.

Frequently asked questions

How do I meet a “within ○○ bytes” limit?

By EUC-KR (Korean) counting, one Korean character = 2 bytes and English/digits/spaces = 1 byte. Paste your text to see both EUC-KR and UTF-8 bytes, then enter a target in the limit checker below to see how much is left.

How many characters is a 200 / 1000 / 4000 byte limit?

For all-Korean text (EUC-KR), divide the byte limit by 2 — 200 bytes ≈ 100 Korean chars, 1000 ≈ 500, 4000 ≈ 2000. Mixing in English, digits, or spaces lets you fit more.

Is the count with or without spaces?

Both are shown at once — use the number that matches the rule for your submission (with or without spaces).

Does it count Korean, Latin, and emoji correctly?

Yes. Korean, Latin letters, digits, and symbols — and even emoji — are each counted as one character, with a per-type breakdown too.

Why do UTF-8 and EUC-KR byte counts differ?

Different encodings. One Korean character is 3 bytes in UTF-8 but 2 bytes in EUC-KR, while English and digits are 1 byte in both. Korean résumé byte limits are usually EUC-KR based.