TOML Formatter
Tidy a TOML file: consistent quoting, ordered tables, keys before headers.
Inspect any character: code point, block, category, UTF-8 bytes and escapes.
The Unicode Code Point Lookup breaks any text into characters and reports the code point, block, category, UTF-8 and UTF-16 bytes and every escape form — which is how you identify an invisible character that has got into a file.
Paste any text and every character is broken out with everything you might need to identify or escape it: the U+ code point in hex and decimal, the Unicode block it belongs to, its general category, and its exact bytes in UTF-8 and UTF-16.
It also gives the escape forms, which is usually the actual job. The HTML entity in decimal and hex, the CSS escape for a content property, the JavaScript escape including the brace form that astral characters need, and the percent-encoded bytes for a URL. It is the fastest way to identify an invisible character that has got into a file — a non-breaking space, a zero-width joiner, a byte order mark or a curly quote that should have been straight.
A non-breaking space, a zero-width joiner, a BOM or a curly quote is listed by name and code point instead of looking like nothing.
UTF-8 and UTF-16 representations side by side, which is what explains why a string length differs between languages.
HTML decimal and hex entities, the CSS escape, the JavaScript escape including the brace form, and percent-encoding.
Which Unicode block a character belongs to and what kind of character it is, from the real Unicode properties.
Characters above U+FFFF are marked, because that is why an emoji has a JavaScript length of 2.
One character or a whole string; every character is listed.
Code point, block, category and byte representations for each.
HTML, CSS, JavaScript and URL escapes are given for every character.
Non-breaking spaces, zero-width characters and BOMs all show up by name.
Paste the text here. Every character is listed with its code point and block, so a non-breaking space (U+00A0), a zero-width space (U+200B) or a BOM (U+FEFF) is immediately visible.
UTF-8 is variable width: ASCII takes one byte, most European and Middle Eastern scripts two, most CJK three, and emoji and rarer scripts four.
JavaScript strings are UTF-16, which stores any code point above U+FFFF as two 16-bit units. That is why an emoji has a .length of 2 in JavaScript despite being one character.
The \u{...} brace form for anything above U+FFFF, since the plain \uXXXX form cannot express it. Below that the two are equivalent and the plain form has wider support.
What people who use the Unicode Code Point Lookup 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 Unicode Code Point Lookup. It takes half a minute and no account.
Write the first reviewTidy a TOML file: consistent quoting, ordered tables, keys before headers.
Build and sign a JWT with HS256, HS384 or HS512 for testing.
Generate a CI workflow with caching, a version matrix and the right permissions.
Score a selector and find out which of two rules actually wins.
Generate plausible addresses in the format each country actually uses.
Run JSONPath expressions against a document and see every match live.
Identify a UUID's version and variant, and extract its timestamp.
Hash a password with bcrypt, or check one against an existing hash.