Word Definition
Look up definitions for common English words, offline.
See the exact UTF-8 bytes behind any text.
| Character | Code point | UTF-8 bytes | Bytes |
|---|
The UTF-8 Encoder shows the exact bytes behind your text, character by character, with the code point each produces. It makes visible the gap between a string's length in characters and in bytes, which is where most encoding bugs actually live.
UTF-8 is how virtually all text is stored and transmitted, and its defining property is that it is variable width. A plain ASCII character takes one byte, an accented letter two, most CJK characters three and an emoji four. Almost every encoding bug traces back to something assuming otherwise.
This shows the exact bytes. Each character is listed with its code point and the bytes it produces, in hexadecimal, decimal or percent-encoded form, so you can see precisely where the length of a string in characters and its length in bytes diverge. That divergence is the reason a name fits a form but fails a database insert, and seeing it laid out is usually enough to explain the whole bug.
Each character with its code point and the bytes it produces, so the variable width is visible.
Hexadecimal for hex editors, decimal for arithmetic, percent-encoded for URLs.
Both figures side by side, which is exactly the gap that breaks a database insert.
The EF BB BF prefix that breaks CSV imports and shell scripts is flagged if present.
Why an accent is two bytes and an emoji four, rather than presenting the numbers without context.
A value, a name or any string you are debugging.
Hexadecimal, decimal or percent-encoded, depending on what you are comparing against.
Each character with its code point and the bytes it produces.
Characters versus bytes, which is where most encoding bugs live.
One for ASCII, two for Latin accents, Greek, Cyrillic, Hebrew and Arabic, three for most CJK characters and the general symbol ranges, and four for emoji and rarer scripts.
Because the form counted characters and the database counted bytes. A twenty-character name with accents can be twenty-five bytes, which will not fit a column sized in bytes.
A three-byte sequence, EF BB BF, that some editors put at the start of a UTF-8 file. It is unnecessary in UTF-8 and causes real problems in CSV imports and shell scripts. The tool flags it if it finds one.
No. Unicode assigns a number to every character; UTF-8 is one way of turning those numbers into bytes. UTF-16 and UTF-32 are others, and they produce completely different byte sequences for the same text.
What people who use the UTF-8 Encoder think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the UTF-8 Encoder. It takes half a minute and no account.
Write the first reviewLook up definitions for common English words, offline.
Turn text into ꜱᴍᴀʟʟ ᴄᴀᴘꜱ that paste anywhere.
Strip or mask email addresses before you share a document.
Randomise word order, across the text or within each line.
Write in aLtErNaTiNg cApS for the mocking SpongeBob effect.
Generate filler text to an exact character or word budget.
Remove hard line breaks so paragraphs flow again.
Rewrite text so only sentence starts and proper nouns are capitalised.