Byte size counter
Paste any text to see its exact byte size in UTF-8 encoding — useful for payloads, headers, storage limits, and API constraints.
About this tool
Paste any text to see its exact size in bytes, KB, and MB (UTF-8). Useful for SMS limits, cookie size, and payload checks — runs in your browser.
Paste any text to see its exact byte size in UTF-8 encoding — useful for payloads, headers, storage limits, and API constraints.
- 1
Paste or type your string into the input field.
- 2
The byte size in UTF-8 encoding is calculated and displayed instantly.
- 3
Compare the character count vs byte count — they differ for non-ASCII characters like emoji or accented letters.
Check payload size before sending API requests with byte-limit headers.
Verify that a message or token fits within storage or transmission constraints.
Understand how multi-byte Unicode characters affect the actual byte length of a string.
ASCII string
hello5 bytes (5 characters)Unicode string
नमस्ते18 bytes (6 characters)Emoji
Hello 👋10 bytes (7 characters)These answers explain common byte size counter tasks, expected input formats, and edge cases so both visitors and search engines can understand what this tool does.
Why does character count differ from byte count?
In UTF-8 encoding, characters outside the basic ASCII range (such as emoji or accented letters) use multiple bytes. A single emoji can be 3 or 4 bytes, so byte count is always equal to or greater than character count.
What encoding does this tool use?
This tool measures byte size using UTF-8 encoding, which is the standard for the web and most modern APIs and databases.
Why would I need to know the byte size of a string?
Many systems enforce byte-based limits rather than character limits — including HTTP headers, message queues, database columns, and JWT token size restrictions.
What limits commonly use byte size rather than character count?
MySQL VARCHAR and TEXT columns, Redis string values, HTTP headers (typically 8 KB), cookie size limits (4 KB per cookie), and message queue payload caps all enforce byte limits. Using character count alone can cause silent truncation when your string contains multi-byte characters like emoji or CJK glyphs.
Why does an emoji count as more than one byte?
Emoji and many non-Latin characters require multiple bytes in UTF-8. A common emoji uses 4 bytes, a Chinese or Arabic character typically uses 3 bytes, and an accented Latin character uses 2 bytes. Only the basic ASCII set uses exactly 1 byte per character.