UTF-8 Byte Length Calculator

Calculate string byte length online

This UTF-8 byte length calculator is a Unicode string length tool for storage, API limits and text diagnostics. It calculates string size in bytes, Unicode code points, grapheme clusters and UTF-16 code units side by side. It handles emoji, combining marks, flags and zero-width-joiner sequences, and it recalculates locally as you type. By default the original text is measured unchanged, so visually similar composed and decomposed Unicode strings can show different counts.

Byte length example

Input:

Hello, café 😀

ASCII letters, comma and spaces use one UTF-8 byte each. In NFC, é uses two UTF-8 bytes. 😀 uses four UTF-8 bytes, is one Unicode code point and one grapheme cluster, and occupies two UTF-16 code units.

UTF-8 bytes

UTF-8 uses one to four bytes per Unicode code point. ASCII characters normally use one byte, accented characters often use two or more, many symbols use three, and many emoji use four. Byte length matters for storage, network payloads, database columns, filenames, queues, search indexes and API limits.

Unicode code points

Code points are Unicode values such as U+0041, U+00E9 and U+1F600. One visible character may contain multiple code points: a decomposed accented letter has a base letter plus combining mark, and emoji sequences may contain modifiers or joiners. This calculator counts code points with code-point-safe iteration instead of JavaScript UTF-16 unit length.

Grapheme clusters

Grapheme clusters approximate user-perceived characters. A base letter plus a combining mark may form one cluster, a family emoji can contain several code points but display as one character, and flags are composed from regional indicator code points. This tool uses Intl.Segmenter when available. If the browser lacks that API, the grapheme value is marked approximate and the other metrics remain exact.

For decomposed é, the calculator reports three UTF-8 bytes, two code points, one grapheme cluster when supported, and two UTF-16 code units. For a family emoji such as 👨‍👩‍👧‍👦, the implementation calculates the exact byte, code-point and UTF-16 counts while reporting it as one grapheme cluster in browsers with full segmentation support.

UTF-16 code units

JavaScript strings use UTF-16 internally, and text.length returns UTF-16 code units. Most Basic Multilingual Plane characters use one code unit. Supplementary-plane characters use surrogate pairs and therefore two code units, which is why "😀".length === 2. UTF-16 code units are not UTF-8 bytes.

Why string length differs across programming languages

Different runtimes expose different length units. JavaScript .length counts UTF-16 code units. Python 3 usually exposes Unicode code points through len(), though grapheme behavior is separate. PHP strlen() counts bytes, while mb_strlen() depends on the selected encoding. Databases may enforce characters, bytes or encoded storage limits depending on system and column type. Read Code Points vs Code Units for the underlying distinction.

Unicode normalization and byte length

Visually identical text can use different code-point sequences. NFC often composes characters, so é may be one code point. NFD often decomposes the same visible letter into e plus a combining mark. NFKC and NFKD may make compatibility changes. Normalization can change UTF-8 byte count, code-point count and UTF-16 code-unit count, while the grapheme-cluster count may stay visually similar. The calculator does not normalize unless you choose a form.

How to use the calculator

1. Paste or type text into the input field.
2. Review the byte and Unicode length metrics as they update.
3. Optionally select a Unicode normalization form.
4. Copy or download the result summary.

Common use cases

• Check database field byte limits.
• Validate API and payload size constraints.
• Compare JavaScript string length with visible characters.
• Measure usernames, filenames and form-field limits.
• Debug emoji, combining characters and Unicode normalization.
• Estimate UTF-8 storage requirements.

Privacy and local processing

This calculator measures text with JavaScript directly in your browser. Your input is not submitted to UnicodeNow servers.

Frequently asked questions