You're filling out an application form that says "1000 characters including spaces" and you have no idea whether the text you've already written fits. Or you're drafting a text message that keeps silently splitting into two messages and costing more, because it quietly crossed a byte limit you didn't know existed. Character and byte limits aren't one universal number — the counting rules genuinely differ by platform, so using the right basis for the situation matters.
What Dagochim's character counter shows you at once
- Characters with spaces / without spaces: the two baseline numbers shown prominently at the top.
- UTF-8 bytes: the encoding used across most of the modern web and email, where each non-Latin character (like Korean, Japanese or many emoji) can take 3-4 bytes.
- Legacy 2-byte encoding (EUC-KR style): the same basis many SMS text message limits still use, where a non-Latin character counts as 2 bytes and Latin letters/numbers count as 1 byte.
- NEIS-style byte count: the convention used by South Korea's school records system, where non-Latin characters count as 3 bytes and line breaks count as 2 bytes.
- Word count, line count, paragraph count, and manuscript-page equivalent: useful for checking assignment length or draft length against a target.
- Estimated reading and speaking time: handy for gauging how long a speech script or blog post will actually take to read aloud.
How to count against a specific limit
- Open the Character Counter tool.
- Paste or type your text into the large text box. The numbers update live as you type.
- Under Limit, pick a preset that matches your situation — common application-form limits, a 160-character (or 70 for non-Latin) single SMS, a long message (LMS) limit, or a school-records byte limit. Choose "Custom" to set your own number and basis.
- Once a limit is selected, a progress bar and remaining count (or over-limit amount) appear immediately, turning red if you've gone over.
- Use the trim-extra-spaces, merge-line-breaks, copy, and clear-all buttons to tidy up the text right there.
Why there are so many different counting rules
The question "how many bytes is one character" doesn't have a single universal answer, because different systems were built on different text encodings at different times. UTF-8, used by most of today's websites, represents a single Korean character in 3 bytes. EUC-KR, an older encoding that dates back to early PC and mobile text systems, instead represents the same character in 2 bytes, with Latin letters and digits staying at 1 byte. Many carriers' single SMS message limits are still calculated using that older 2-byte convention even today, simply because the underlying telecom standards were built around it decades ago and never fully migrated. A school records system can use yet another convention, where non-Latin text costs 3 bytes but a line break costs 2 bytes instead of 1. Knowing which limit you're actually up against — and picking the matching counting basis — avoids the frustrating experience of a form rejecting text you were sure fit.
Counting accurately: emoji and special characters as one unit
Older, naive character-counting methods often miscount emoji or certain special symbols as two characters instead of one, because those characters are internally represented using what's called a "surrogate pair" in UTF-16-based systems like JavaScript strings. This tool uses the modern browser text-segmentation API (Intl.Segmenter) to count what a person actually sees as a single character — a real grapheme — rather than counting the underlying code units. On the rare older browser that doesn't support this API, it falls back to a reasonable alternative method.
A closer look: with-space vs. without-space counts, and why both matter
Spaces might feel like they "shouldn't count," but whether they do is entirely a convention set by whoever defined the limit, not a universal rule. Some application forms specifically exclude spaces from their limit to avoid penalizing naturally wordy writing, while others count every character including spaces because that's simpler to implement and verify. When a limit's rules aren't stated explicitly, defaulting to the stricter with-spaces count is the safer assumption, since it's rare for a with-spaces count to accidentally make your text look too long when the real rule was actually more lenient (without spaces) — but the reverse mistake, assuming a lenient rule when the real one is strict, can get a submission rejected.
Is my text kept private?
Yes. All counting happens entirely inside this browser and is never sent to a server. For your convenience, the text is automatically saved to this browser's local storage so you can close the tab and continue later without losing your draft. If you used a shared or public computer (a library, an internet cafe), it's worth clicking the Clear button before you leave so the next person doesn't see your draft.
Common problems and how to fix them
- The count doesn't match what the form site shows: check whether that site counts with or without spaces, and which byte encoding it uses if it enforces a byte limit rather than a character limit. This tool lets you compare several bases side by side to find the match.
- My text messages keep splitting into multiple parts: crossing roughly 70 non-Latin characters (or 160 Latin characters) under the legacy SMS byte convention typically triggers an automatic switch to a longer multi-part message format, sometimes at extra cost. Check the SMS preset to see your byte count against that specific limit.
- I'm not sure whether line breaks should count as characters: some systems (like certain school-records conventions) count a line break as 2 bytes rather than the usual 1. A checkbox below the counter lets you toggle whether line breaks are included in the character count, so you can match either convention.
- Pasted text shows a different count than I expected from a word processor: word processors sometimes report "words" using their own internal rules (hyphenated words, numbers, etc. can be counted differently), so small discrepancies between tools are normal and don't indicate an error.
Frequently asked questions
Should I count with or without spaces for an application form?
It depends on the form. Many job or school applications explicitly state whether a limit like 1000 characters includes spaces, so check the instructions first. If nothing is specified, counting with spaces included is the safer default. This tool shows both numbers side by side so you can check either instantly.
Why do SMS byte limits count 2 bytes per character for non-Latin scripts?
Many mobile carriers still calculate single text message limits using an older encoding scheme that counts non-Latin characters (like Korean, Japanese, or Chinese) as 2 bytes and Latin letters/numbers as 1 byte, instead of the UTF-8 encoding used across most of the modern web (which uses 3 bytes for a Korean character). Because the SMS limit is based on the older scheme, you need to check byte counts using that specific basis rather than standard UTF-8.
Is the text I type saved or sent anywhere?
No, the counting itself happens entirely inside this browser and nothing is sent to a server. For convenience, your text is automatically saved to this browser's local storage so you can pick up where you left off. If you're on a shared or public computer, use the Clear button when you're done.