What Is Text Size in Bytes and Why It Matters for Developers

The size of text in bytes is not the same as the number of characters. For plain ASCII text they happen to match. But for Unicode text — anything with accented characters, non-Latin scripts, emoji, or special symbols — the byte size can be 2 to 4 times the character count. This difference matters when sizing database columns, setting API payload limits, calculating SMS segment costs, and handling file storage planning.

Calculate the exact byte size of any text with our free Text Size Calculator tool. For counting characters and words, use our Character Counter. For understanding character-to-code relationships, our ASCII Converter and Binary Converter tools explain the underlying encoding.

UTF-8 is the dominant encoding for web and modern applications. It uses variable-width encoding where the number of bytes per character depends on the character:

1 byte: standard ASCII characters (English letters, digits, common punctuation) — U+0000 to U+007F. "Hello World" is 11 characters and 11 bytes. 2 bytes: extended Latin, Greek, Cyrillic, Hebrew, Arabic — U+0080 to U+07FF. The e-with-accent character (U+00E9) is 1 character but 2 bytes. 3 bytes: most other scripts including Chinese, Japanese, Korean, mathematical symbols — U+0800 to U+FFFF. A Chinese character is 1 character but 3 bytes. 4 bytes: emoji, less common symbols, historical scripts — U+10000 to U+10FFFF. A grinning face emoji is 1 character but 4 bytes.

A string of 100 Chinese characters is 100 characters but 300 bytes in UTF-8. The word "cafe" is 4 characters and 4 bytes. The word "cafe" with an e-accent is 4 characters but 5 bytes. A single emoji adds 4 bytes regardless of how short the surrounding text is.

MySQL VARCHAR(n) in utf8mb4 stores up to n characters but up to 4n bytes. A VARCHAR(255) in utf8mb4 can be up to 1020 bytes. InnoDB row size limits mean wide utf8mb4 columns can cause row size errors. Always plan schema with byte size in mind when storing international text or emoji. Test with our Text Size Calculator using realistic sample content from your target languages.

Many APIs enforce payload limits in bytes, not characters. A 1MB limit can be hit much faster than expected if the payload contains substantial CJK text or emoji. Calculate the actual byte size of your API payloads before assuming a character count is within limits.

SMS standard encoding uses 160 characters per segment for ASCII text. The moment any Unicode character appears — including a single emoji — encoding switches to UCS-2, dropping the limit to 70 characters per segment. A 100-character message with one emoji requires 2 segments and costs twice as much for bulk SMS. Use our Character Counter to keep messages within the 160-character ASCII limit for cost-efficient SMS.