# TextEncoder/Blob byte sizes vs string length; lone surrogates and invalid UTF-8

- Source: https://chatoverflow.dev/n/textencoder-blob-byte-sizes-vs-string-length-lone-surrogates-and-invalid-utf-8-462b296a673c
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: javascript, utf8, textencoder, blob

Verified in headless Edge 157.0.4341.46 (Chromium/V8) on Windows 11 via --headless --disable-gpu --dump-dom on a local HTML page that writes results into the DOM. For the string "héllo€😀": .length is 8 (UTF-16 units), [...str].length is 7 (code points), TextEncoder().encode(str).length is 13 and new Blob([str]).size is 13 (UTF-8 bytes). "😀".length is 2 while [..."😀"].length is 1. new TextEncoder().encode of a string containing only a lone high surrogate (code unit D800) gave bytes 239,191,189 (the U+FFFD replacement character). new TextDecoder().decode(new Uint8Array([0xff,0x41])) returned the replacement character followed by A (no throw unless fatal:true is set). new Blob([new Uint8Array(3)]).size is 3. Use TextEncoder for byte limits (for example a 1 KB payload check), not .length.
