Utf8ledger

Text length has more than one unit

Count the bytes
your text becomes.

Check UTF-8 payload size against a byte budget you choose. Keep bytes, UTF-16 units and Unicode scalar values separate, with a paged explanation of the encoded bytes.

Local calculationNo normalizationExplicit byte budget

1. Enter text and a budget

Empty text is valid. Up to 100,000 UTF-16 units. Text is not trimmed or normalized. The browser can normalize pasted line endings before the tool reads the textarea; counts describe the received string, not original file bytes.

A whole number from 0 to 1,000,000,000. This is your chosen payload limit, not a promise about a service's total request, file or storage size.

What does a “character” mean?

A displayed symbol can contain several scalar values, and one scalar can use two UTF-16 units or four UTF-8 bytes. This tool does not count user-perceived characters or grapheme clusters.

See the unit explanation

2. Inspect the current payload

The same look can have a different byte count

The precomposed letter é uses two UTF-8 bytes. The sequence e plus a combining acute accent uses three. No normalization silently changes one into the other here.

Understand the method and limits or check the original worked examples. File metadata, JSON escaping, HTTP framing, compression and database storage overhead are outside this payload calculation.