Runs in your browser

UTF-8 byte counter.

See the difference between visible characters and actual UTF-8 bytes, especially with emoji and non-English text.

0

Characters

0

Words

0 min

Reading time

Paste text to start.

Selected limit

UTF-8 bytes

Paste text to start.

Paste text before shortening.

Why this page exists

Byte limits are different from character limits.

Databases, APIs, forms, and SMS systems often care about encoded size, not only what people see.

One byte

Basic ASCII characters usually use one UTF-8 byte.

Multiple bytes

Emoji, accented letters, and many scripts use more.

Safer copying

Check bytes before pasting text into strict technical fields.

Practical guide

Measure the UTF-8 size a system actually stores.

Character limits describe visible text; byte limits describe encoded data. TextLimit uses the browser's UTF-8 encoder so you can test the exact string that will be sent to an API, database, import, or form.

ASCII is usually one byte

Basic English letters, digits, spaces, and common punctuation normally use one UTF-8 byte each. That is why character and byte totals often match for simple plain text.

Unicode uses variable width

Accented letters, non-Latin scripts, and emoji can use multiple bytes. A string can fit a character limit while exceeding a database column, request field, or legacy integration's byte limit.

Visually identical text can differ

Unicode can represent some visible symbols with either a precomposed character or a base character plus combining marks. Those strings can look alike while producing different character and byte totals.

Measure the serialized value

Prefixes, separators, line endings, and escaping can add bytes outside the text itself. This counter measures the pasted string; include any literal formatting that belongs to the stored field.

Before sending text to a byte-limited system

  1. Confirm that the documented limit is bytes rather than characters.
  2. Paste representative international text and emoji, not only ASCII samples.
  3. Include separators and line endings stored in the same field.
  4. Test the final serialized payload when escaping or normalization is involved.