Free Unicode Inspector.

Code points, invisible characters and normalization suggestions.

Investigate puzzling text mismatches with the exact characters visible, helping you choose an appropriate normalization rule.

Install WebAct — use it free See the completed example ↓

Chrome extension + account required.
25 free automation tasks/month across tools. Browser-provider limits apply.

WHAT TO HAVE READY

Text with unexpected characters.

YOUR STARTING POINT

A task you can make yours.

Edit the prompt, then copy it.

Copy it here. Paste it into WebAct when you are ready.

This page prepares your prompt. The task runs in WebAct.

Make the task yours.

Review the prompt above. Add your goal and any requirements that matter.

Bring it to WebAct.

Open WebAct, paste the task and provide the data and rules. Review any proposed calculation or code action before approving it, then check a known example.

Check the useful part.

Check formulas, code and calculations against known inputs in the appropriate runtime. Review actions before execution and keep the original data available.

A PRACTICAL GUIDE

How to use the Unicode Inspector.

Inspect code points when text looks identical but behaves differently. Normalize only when the destination's rules allow it.

Make the workflow fit your task.

Inspect the actual characters, listing code points and positions rather than relying on appearance. Identify combining marks, lookalike symbols and invisible characters. Compare normalized forms only under an agreed rule and retain originals when exact identifiers or bytes matter.

What you provide: Text with unexpected characters.
What you get: Code points, invisible characters and normalization suggestions.

See the input and the result.

Illustrative input and output · a teaching example, not a live WebAct run

Example input

Inspect these two strings: café and café. Compare their code points and their NFC-normalized values.

Completed example

café: U+0063 U+0061 U+0066 U+00E9 (4 code points).
café: U+0063 U+0061 U+0066 U+0065 U+0301 (5 code points).
Both normalize to café under NFC. Their original sequences differ; preserve originals when exact byte identity matters.

Download this example

Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.

Decisions and troubleshooting.

Can visually identical Unicode strings have different lengths?

Yes. A visible character can be represented by one code point or several, and byte length adds another distinct measure.

Why did normalization fail to make two lookalike letters equal?

They may be different characters from different scripts rather than alternative representations of the same character. Inspect their code points.

Reference for this workflow.

MDN: Unicode normalization in JavaScript

Try it with your own source.

Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.

Customize and copy the task ↑

BEFORE YOU BEGIN

Using WebAct.

The prompt and example are available here. Run your task in the WebAct Chrome extension.

Is this tool free?

You can copy and edit the prompt here for free. To use it with WebAct, install the Chrome extension, create and verify your account, and connect an available browser ChatGPT session. The Free plan includes 25 user-started automation tasks per calendar month, shared across tools. Ordinary browser Chat is separate; provider limits apply.

Learn about shared context in our privacy policy and choosing Chat or Task.

FROM A PROMPT TO YOUR OWN WORK

Bring the task to your page.

Install WebAct, add your source material and make the result yours.

Install WebAct