Characters, Spaces and Line Breaks: Understand the Count You Copy

A field may limit characters, bytes, words or visible symbols. Those are different quantities. Start with the recipient's stated rule and count the same text, including any spaces or line breaks that will actually be submitted.

Character Counter reports total characters, characters without spaces and lines. In the current implementation, ‘characters’ means UTF-16 code units. This is a useful technical count, but it is not a promise about every form, messaging app or editor.

The input column uses escaped notation: \t represents a tab and \n represents a single LF newline. The empty pair of quotation marks represents an empty input. Do not include the surrounding notation quotes when reproducing a sample.

Both accented examples can look similar. The composed é is one code unit; e followed by a combining acute accent is two. The emoji example is also two code units even though it appears as one symbol. Copying by appearance alone can miss that distinction.

For a b, a tab between a and b, or an LF newline between them, the total is three code units and the whitespace-removed total is two. That second number removes the separator for counting; the tool does not rewrite your source text.

Removing spaces from a count is not the same as meeting a recipient's character limit. If their limit includes whitespace, use the appropriate total instead. Likewise, a UTF-8 byte limit requires a byte measurement rather than either character result shown here.

A long sentence can wrap onto several visible rows on a phone without containing any newline. It remains one logical line here. A newline at the end of a adds an empty second line, so the input a followed by LF has two total code units and two lines.

Raw CRLF is two code units but one line-break sequence. At the function level, a + CRLF + b has total four, whitespace-removed two and lines two. Browser textareas commonly normalize line endings to LF, so a pasted Windows line break may show total three in the actual input. The eight main examples use the text as read by the control.

An empty input has zero lines in this tool. One explicit line break is different from empty text: it separates two empty logical lines. Do not use the visible height of the input box as evidence of the count.

If totals disagree, compare a short sanitized excerpt and identify its exact spaces, line breaks and Unicode representation. Do not delete punctuation or accents just to make two unrelated counters agree. Preserve meaning and use the receiving system's documented counting rule.

For word totals, use Word Counter and its whitespace-boundary guide. For a form submission, check the final text in that form because its normalization and limits may differ. This guide explains the local result and does not test or guarantee any named platform's acceptance.