09 / OTTERDAY
Character counter
Count characters, bytes and words, and check your goal locally without saving your text.
Files and text stay in this tab’s memory. No uploads or automatic saves; reloading clears them. Site and advertising requests are separate and do not include your files or entered text.
Up to 200,000 UTF-16 units. No automatic saves; reloading clears your text.
Counting rules and application forms
Characters are Unicode code points (😀=1; joined emoji can count as several). Excluding spaces removes spaces, tabs and line breaks. CRLF/CR count as one LF character; only byte counts use your selected line ending. Words and sentences use Intl.Segmenter in the UI language. Blank lines separate paragraphs. Manuscript pages round characters with spaces up to the next 200, not actual typeset pages. Reading time is an estimate.
UTF-8 usually uses 3 bytes per Korean syllable and 4 for 😀. EUC-KR (web CP949) uses 2 bytes for supported Korean characters; unsupported characters such as emoji prevent a byte total. Saramin and JobKorea use different rules, including 1/2-byte approximations and UTF-16 character counts. Always check the destination form.
Application form sources: Saramin · JobKorea · WHATWG EUC-KR
A few helpful answers
Is my text saved automatically?
No. Text is counted in tab memory and cleared on reload. It is not sent to storage or a server.
Why do application sites show different byte counts?
UTF-8, EUC-KR, line endings and character counting rules differ. This tool lets you choose encoding and flags unsupported characters. Use the destination form’s own count as the final check.
Are manuscript pages and reading time exact?
Manuscript pages round the character count with spaces up to the next 200. Reading time estimates your selected speed. Actual typesetting and reading speed vary.