Developers

Invisible Characters in Code

Zero-width and blank characters in source code — where they come from, what they break, and how to strip them. Covers 2 contexts.

Why hidden characters in code matter

They break exact matching, and almost everything downstream depends on it. Invisible characters programming problems all share this root: an identifier that looks correct and does not resolve. Two strings that look identical stop being equal, and every comparison built on that inherits the failure.

The characters arrive through the clipboard rather than the keyboard. A PDF export substitutes U+00A0 for spaces to hold its layout. A web page carries U+200B for line-break control. Newer AI models emit U+202F in place of ordinary spaces. None is deliberate, and all of them travel with the text.

Why trimming does not fix it

Trimming removes only the characters whose Unicode propertyWhite_Space is Yes. That covers the 17 space separators and none of the zero-width characters.

Every Cf character — U+200B, U+200C, U+200D, U+2060, U+FEFF — hasWhite_Space=No, so trim(), TRIM() and the regex class\s all leave them in place. This is why the obvious fix appears to do nothing.

Match the category instead. Full property data for all 29 characters is on the Unicode invisible characters table.

Choose your tool

Each guide covers one application: how to see the characters there, how to remove them, and what they break in that context.

Frequently asked questions

01

Where do invisible characters in Developers come from?

They arrive through the clipboard, not the keyboard. Text copied from a PDF, a web page, a spreadsheet or an AI assistant carries U+00A0 and U+200B from the source formatting, and neither is inserted deliberately.

02

How do I find them?

Match by Unicode category rather than by codepoint. The classes \p{Cf} and \p{Zs} cover almost every invisible character and keep working across Unicode releases, where a codepoint list goes stale.

03

Why does TRIM or trim() not remove them?

Because trimming only removes characters whose Unicode property White_Space is Yes. Every Cf character — the zero-width ones — has White_Space=No and survives untouched.

04

What breaks when they are present?

Exact matching, and everything built on it. Search fails, lookups return nothing, identifiers do not resolve, numeric columns parse as text, and version control shows phantom whitespace diffs.

Written by , developer and writer.

Last reviewed