Unicode gives characters code points. Looking at those code points helps when text looks identical but behaves differently.

The Text to Unicode tool helps with the mechanical part, but I still check the result before using it somewhere real.

The simple idea

Unicode gives characters code points. Looking at those code points helps when text looks identical but behaves differently.

I use the tool to make the transformation visible: input on one side, output on the other, and a quick sanity check before I copy anything.

Step 1: Paste the suspicious text

Paste the suspicious text.

Step 2: Inspect each character’s code point

Inspect each character’s code point.

Step 3: Look for invisible spaces or control characters

Look for invisible spaces or control characters.

Step 4: Compare similar-looking letters from different scripts

Compare similar-looking letters from different scripts.

Step 5: Check emoji and accented characters carefully

Check emoji and accented characters carefully.

Step 6: Rebuild text from code points only when you trust the values

Rebuild text from code points only when you trust the values.

Step 7: Use this for debugging, not for judging language or identity

Use this for debugging, not for judging language or identity.

My checklist

Before I trust the result, I check:

  • Paste the suspicious text.
  • Inspect each character’s code point.
  • Look for invisible spaces or control characters.
  • Compare similar-looking letters from different scripts.
  • Check emoji and accented characters carefully.
  • Rebuild text from code points only when you trust the values.
  • Use this for debugging, not for judging language or identity.

Small utilities are useful because they remove repetitive work. They are safest when the output is still reviewed.

Comments

Comments are welcome — please read the comment policy first. Powered by giscus and GitHub Discussions.