UTF-8 encode text to bytes

UTF-8 maps every Unicode character to a sequence of one to four bytes. Unlike fixed-width encodings, ASCII letters still use a single byte while emoji and accented letters expand to two, three, or four bytes. That variable length is why a string's character count rarely equals its byte count.

When you utf8 encode text online, you are not encrypting or compressing — you are revealing the raw bytes that HTTP, JSON, databases, and filesystems actually store. Developers paste strings here to compare against hexdump output from Wireshark, firmware logs, or a misbehaving API.

This utf8 encoder uses the browser's TextEncoder API, which always outputs standard UTF-8. That matches what Node.js Buffer.from(str, 'utf8'), Python str.encode('utf-8'), and Rust str.as_bytes() produce for the same input.

Treat the hex stream as the source of truth during debugging. If two systems disagree on a string but the UTF-8 bytes match, the bug is in display or decoding — not in the original text.

Type or paste text into the input panel. The output updates live — each pair of hex digits is one byte. The letter A encodes to 41, the word Hello to 48 65 6c 6c 6f, and emoji expand to longer sequences you can copy for unit tests.

Choose spaced hex when humans will read the output — packet captures and documentation usually separate bytes with spaces. Choose compact hex when pasting into dense logs, C array literals, or tools that reject whitespace. Decimal byte mode outputs values like 72, 101, 108 for consumers that expect numeric arrays.

Copy the result with one click and paste into your decoder, test fixture, or ticket. For round-trip verification, paste the same output into our UTF-8 Decoder and confirm the original string returns unchanged.

Large pasted documents are fine within browser memory limits. Extremely long strings may feel sluggish — split by section if you only need bytes for a header or signature field.

JavaScript strings are UTF-16 internally, so string.length counts code units — not UTF-8 bytes and not visible characters when surrogate pairs appear. This tool's byte count follows UTF-8 rules, which is what wire formats almost always use.

Do not confuse UTF-8 hex with UTF-16 code units. The UTF-16 encoding of Hello uses ten bytes (two per ASCII letter) while UTF-8 uses five. Always confirm which encoding your protocol specifies before comparing hex.

UTF-8 BOM bytes (EF BB BF) sometimes prefix Windows text files. This encoder does not add a BOM by default — include one manually in your source if your consumer requires it, or strip it on decode if the consumer rejects it.

Legacy single-byte encodings like Windows-1252 or ISO-8859-1 produce different hex for the same visual character. If decode fails or looks wrong, verify the source file was actually UTF-8.

API debugging: encode a known payload here, then compare the hex to raw response bytes in your network tab. A mismatch under charset=utf-8 often means gzip compression, double encoding, or a wrong Content-Type label.

Cryptography and signing: HMAC, SHA, and Ed25519 operate on bytes. Two visually identical strings can hash differently if one uses curly quotes (multi-byte UTF-8) and the other uses straight ASCII quotes. Encode both and diff the hex before blaming the signature algorithm.

Firmware and embedded docs: hardware teams document string tables as hex byte arrays. Export decimal or spaced hex directly into C headers, Rust const arrays, or Python bytes literals.

Test fixtures: store expected UTF-8 sequences as hex in JSON test files so CI asserts exact wire bytes, not just rendered glyphs that fonts might hide.

Spaced hex (48 65 6c 6c 6f) mirrors hexdump -C and Wireshark byte views. It is the easiest format for human review and code review comments.

Compact hex (48656c6c6f) removes whitespace for hash inputs, compact JSON fields, and regex-friendly logs. Decoders accept both forms — spaces are cosmetic.

Decimal bytes (72, 101, 108, 108, 111) suit spreadsheet imports, PLC configs, and teaching materials that reference numeric ASCII tables. Each value must stay in the 0–255 range.

Lowercase hex is the default output style. Uppercase hex represents identical bytes — case is never semantically meaningful.

TextEncoder runs locally in your browser. Passwords, tokens, customer names, and internal error messages never upload to a server. Clear the textarea when finished on shared machines.

Pair with our UTF-8 Decoder for reverse conversion. Use Base64 Encoder when you need to wrap bytes for JSON or email — Base64 is transport encoding, not raw byte display.

URL percent-encoding (%C3%A9 for é) is for addresses and query strings, not general byte inspection — use our URL Encoder for that layer. Use HTML Escape when the problem is markup escaping, not charset bytes.

Document the hex format you paste into tickets (spaced vs compact vs decimal) so teammates reproduce the same bytes without guessing.