Copy, repeat, and inspect Unicode

Invisible Character Copy & Blank Text Detector

Copy a documented invisible character, generate blank-looking text, or reveal hidden Unicode by code point, name, and exact position. Everything entered in the detector stays in this browser tab.

Short answer: an invisible character is Unicode data that renders with no obvious mark or as a blank glyph. It is not truly empty, and no character is guaranteed to work in every username, bio, game, or messaging app.

Copy blank text

These buttons copy U+2800 BRAILLE PATTERN BLANK. The shaded boxes show how many real Unicode characters will be placed on your clipboard.

Choose an invisible character

These characters are not interchangeable. Read the purpose and limitation before copying one.

BRAILLE PATTERN BLANK

U+2800 · blank glyph

A blank-looking Braille cell with a measurable character width.

Useful for: A visible blank placeholder when an ordinary space is collapsed.
Limitation: It is not whitespace. Some forms reject it, and assistive technology may identify it as a Braille character.

HANGUL FILLER

U+3164 · blank glyph

A compatibility Hangul filler that usually renders as an empty-width glyph.

Useful for: A blank-looking separator when the receiving app preserves the character.
Limitation: Acceptance and width vary by font and platform. It should not be used to impersonate another account.

NO-BREAK SPACE

U+00A0 · space

A space that asks text layout engines not to wrap at that position.

Useful for: Keeping a short phrase, number, or symbol together on one line.
Limitation: Many forms normalize it to a regular space, so it is unreliable for blank names or messages.

ZERO WIDTH SPACE

U+200B · zero-width

An invisible optional line-break point with no advance width.

Useful for: Adding a possible break inside a long token in systems that support it.
Limitation: Sanitizers often remove it. It can make searching, cursor movement, and screen-reader output confusing.

WORD JOINER

U+2060 · zero-width

A zero-width formatting character that prevents a line break.

Useful for: Keeping text together without adding a visible space.
Limitation: Apps may strip it, and hidden formatting can make text harder to edit or audit.

ZERO WIDTH NON-JOINER

U+200C · format control

A shaping control that prevents adjacent characters from joining in scripts that use joining.

Useful for: Correct typography in languages such as Persian and other joining scripts.
Limitation: This is not a general-purpose blank character. Removing or inserting it can change spelling and rendering.

Generate repeated blank text

Repeat BRAILLE PATTERN BLANK from 1 to 100 times. The preview uses visible boxes so you can verify the count; the clipboard receives the actual invisible characters.

Character

Count

Counted preview

□□□

Invisible character detector and viewer

Paste text to reveal blank spaces, zero-width characters, direction controls, variation selectors, and other known non-printing code points. Analysis happens in this browser tab.

Original editorial illustration of a magnifying glass revealing otherwise invisible character cells — Original PasteMoji editorial artwork. The detector—not the illustration—identifies Unicode names, code points, and positions; blank-looking characters still contain data.

Which blank character should you use?

Comparison of common invisible and blank Unicode characters
Character	Code	Legitimate purpose	Important limitation
Braille Pattern Blank	U+2800	A blank-looking cell with character width.	Not whitespace; it can be announced or rejected.
Hangul Filler	U+3164	A compatibility filler that often renders blank.	Width and acceptance depend on the font and app.
No-Break Space	U+00A0	Keeps adjacent text together on a line.	Frequently normalized to an ordinary space.
Zero Width Space	U+200B	Adds an optional line-break opportunity.	Often stripped; it can hinder editing and search.
Word Joiner	U+2060	Prevents a break without adding visible width.	May be removed by sanitizers or text cleanup.
Zero Width Non-Joiner	U+200C	Controls joining behavior in applicable scripts.	It can change language rendering and is not a blank-space substitute.

How to copy and test invisible text

1
Choose by purpose
Use a blank glyph for a blank-looking placeholder, NBSP for non-breaking spacing, or ZWSP for an optional break.
2
Copy the smallest amount
Start with one character. Repeating hidden characters can make text hard to edit and more likely to be rejected.
3
Paste and verify
Test the destination, then paste the result back into the detector to confirm exactly what survived.

Platform compatibility and practical use cases

Platform behavior is a test result, not a permanent promise. Apps can change validation, normalization, fonts, or moderation rules at any time.

Instagram and TikTok

Bios and display-name fields may preserve some blank-looking characters, but validation can change without notice. Never use them to imitate another person or brand.

Discord

Message fields may preserve a character that the username system rejects or normalizes. Server rules still apply, and copied blank text is not a moderation bypass.

WhatsApp and messaging apps

A blank-looking message still contains data and can be revealed by copying or scanning it. It does not hide a message or provide privacy.

Games and community profiles

Many games block invisible characters in names. Repeated attempts may violate naming rules, so use an ordinary visible name when a character is rejected.

Web pages and documents

Use semantic layout tools for spacing. NO-BREAK SPACE, ZERO WIDTH SPACE, and WORD JOINER are appropriate only when their documented line-breaking behavior is needed.

Compatibility checklist for form fields and common operating-system families. These are verification instructions, not permanent support claims.
Environment	Current status	What can change	Safe verification
Plain text and textarea fields	Destination-specific; not guaranteed	Trimming, normalization, maximum length, and sanitization	Paste one character, submit only non-sensitive test content, then inspect the saved value.
Username and display-name fields	Not tested by PasteMoji	Account rules, impersonation controls, and allowed-character lists	Use a test profile only where permitted; keep a visible fallback and never imitate another identity.
Password, email, URL, and file-name fields	Do not use	Normalization and invisible differences can cause lockouts, spoofing, or broken links	Use visible, specification-compliant characters instead.
Windows browsers and apps	Not tested by PasteMoji	Windows build, browser/app version, font, and destination validation	Record those versions, paste once, save, reopen, and scan the result with this detector.
macOS browsers and apps	Not tested by PasteMoji	macOS build, browser/app version, font, and destination validation	Record those versions, paste once, save, reopen, and scan the result with this detector.
iOS and iPadOS apps	Not tested by PasteMoji	OS/app version, keyboard, font, field type, and server-side cleanup	Use non-sensitive text, record versions, reopen the saved value, and compare its code points.
Android apps	Not tested by PasteMoji	Android build, device font, keyboard, app version, and server-side cleanup	Use non-sensitive text, record versions, reopen the saved value, and compare its code points.
Linux and ChromeOS browsers	Not tested by PasteMoji	Distribution or OS version, browser, fonts, and web-form validation	Record the environment, submit a disposable sample, then copy the stored result into the detector.

Accessibility, safety, and misuse

Screen readers may pause, announce a Unicode character, or produce confusing output. Use visible labels for meaningful controls and links.
Hidden code points can break search, comparison, cursor movement, copy/paste, and security review. Do not put them in passwords, URLs, email addresses, file names, or identifiers unless a specification requires it.
Do not use blank text to impersonate people, hide spam, evade moderation, bypass limits, or create deceptive names.
The detector identifies documented characters; it does not decide whether a message, username, or file is safe.

Invisible character questions

Is an invisible character the same as an empty string?

No. An empty string contains zero characters. Blank-looking text contains one or more Unicode code points, so it can affect length limits, searching, cursor movement, line wrapping, and accessibility.

Which invisible character works everywhere?

None. Apps use different fonts, validation rules, and Unicode normalization. BRAILLE PATTERN BLANK and HANGUL FILLER often look blank, while ZERO WIDTH SPACE has no width, but any receiving service can preserve, transform, or reject them.

Why does pasted blank text disappear?

The destination may trim leading or trailing whitespace, normalize Unicode, remove format controls, or use a font that renders the character differently. Try a character with the correct documented purpose rather than adding many hidden characters.

Does the detector upload my text?

No. Detection runs in the page using browser-side JavaScript. The tool can emit action names and aggregate counts for analytics integration, but the pasted string is never included in those events.

Can invisible characters bypass filters or character limits?

They should not be used for that. Hidden characters can create confusing identifiers and may violate platform rules. The detector is provided to inspect text, troubleshoot formatting, and understand Unicode—not to evade safeguards.

Technical sources

Code-point names are based on the Unicode Names List Charts. The descriptions of ZERO WIDTH SPACE, WORD JOINER, NO-BREAK SPACE, and ZERO WIDTH JOINER follow the Unicode Line Breaking Algorithm. Platform acceptance notes are deliberately labeled as variable because receiving services control their own validation.