What this tool does
Text Size calculates exactly how much space your text occupies — in bytes, kilobytes and characters — using UTF-8 encoding, the standard for the web and most modern systems. It is the tool you need when a limit is measured in bytes rather than characters, which is more common than people expect.
Why bytes differ from characters
In UTF-8, not every character is one byte. Plain English letters and digits take one byte each, so for simple text the byte count matches the character count. But accented letters take two bytes, many symbols and non-Latin characters take two or three, and emoji can take four. This means a 100-character string can be well over 100 bytes. When a system measures a limit in bytes, counting characters will mislead you — this tool shows the real byte size.
When byte size matters
Database fields are often defined with byte limits, so a value that fits as characters can still be rejected for exceeding the byte cap. Some APIs and protocols measure payloads in bytes. SMS messages, file size budgets, and certain form fields all care about bytes. Developers checking whether a value fits a column, or whether a payload is under a size limit, need the byte count, not the character count.
Reading the result
The tool shows three numbers updating as you type: the total bytes under UTF-8, the equivalent in kilobytes for larger text, and the plain character count for comparison. When the byte and character counts diverge, that gap is your text's non-ASCII content — the accents, symbols and emoji that each take more than one byte. Everything is calculated in your browser, so even sensitive text stays on your device.
Characters versus bytes
A character and a byte are not always the same thing. In plain ASCII, one character is one byte, but in UTF-8 — the standard encoding of the web — accented letters, emoji and non-Latin characters take two, three or four bytes each. This tool measures both: the character count and the true size in bytes under UTF-8. The difference matters whenever a limit is defined in bytes rather than characters, which is more common than most people expect.
Why byte size matters
Database fields are often sized in bytes, so a VARCHAR limit can be reached by fewer characters than expected if the text contains multi-byte characters. Network payloads, message size limits and storage quotas are measured in bytes. Some APIs limit request bodies by byte size. If you have ever had text rejected for being "too long" when the character count looked fine, multi-byte characters and a byte-based limit were probably the cause. Measuring the byte size up front avoids that surprise.
UTF-8 and multi-byte characters
UTF-8 encodes the basic Latin letters and digits in a single byte each, so plain English text has equal character and byte counts. But "é" is two bytes, many Asian characters are three bytes, and emoji are typically four. So a 100-character string can be anywhere from 100 to 400 bytes depending on its content. This tool shows the exact byte size, the kilobyte size and the character count together, so you can see precisely how your text measures against any limit, whether it is defined in characters or bytes.