Blank text

Invisible & blank text.

How to make text that sends as a real message but shows up as nothing — the empty WhatsApp bubble, the blank Discord line, the clean gap in an Instagram bio. What actually works, why a plain space doesn’t, and how to generate it.

What “invisible text” really is

Invisible text isn’t a trick or an exploit. It’s just a normal character that happens to have no visible shape. Your keyboard’s space bar produces U+0020, a space that most apps consider “empty” and trim away. But Unicode has other characters that a computer treats as genuine, printable content while drawing nothing on screen. Paste one of those into a chat box and the app sees a real message — it just looks blank.

The most useful one is the Braille Pattern Blank, code point U+2800. It belongs to the Braille block and represents a Braille cell with no raised dots — so it’s a printable character with an empty glyph. Because it isn’t whitespace, apps don’t strip it, and because it has no visible form, the result looks empty.

Why a plain space doesn’t work

This is the thing most people get stuck on. You type a few spaces, hit send, and nothing happens. Two things are working against you:

  • Apps trim whitespace. WhatsApp, Discord, Instagram, and most others strip leading and trailing spaces (U+0020) before sending. A message of “just spaces” becomes an empty string.
  • Empty messages are blocked. Once the spaces are trimmed away, there’s nothing left, so the Send button is disabled or silently ignored.

A blank Unicode character sidesteps both. It survives trimming because it isn’t classified as whitespace, and it satisfies the “message must not be empty” check because it counts as content.

Which characters actually work

Not every “invisible” character is equally reliable — some get filtered by the app before they’re sent. Here’s how the common ones behave:

  • Braille Pattern Blank U+2800 — most reliable. A printable character with no glyph. This is what textrepeat.net uses for its Invisible mode. Works consistently on WhatsApp, Discord, and Instagram.
  • Hangul Filler U+3164 — usually works. An old placeholder character that also renders as nothing. A good backup where U+2800 is filtered.
  • Zero-Width Space U+200B — unreliable. Genuinely zero-width, but many apps strip it or collapse it, so a message made only of these can still come through as empty.
  • Non-Breaking Space U+00A0 — often survives, but not truly invisible. It renders as a normal-width blank, so it can be spotted as a gap. Handy for keeping spaces in text that would otherwise be trimmed.

How to make invisible text here

You don’t need to hunt for the character. On the main repeater:

  • Type anything in the text box (it will be replaced with blank characters, so the content doesn’t matter).
  • Under Font style, choose Invisible. Each character becomes a Braille-blank U+2800.
  • Set how many times to repeat. One repetition gives a single blank message; 20 with a New line separator gives a tall, empty block.
  • Press Copy and paste it wherever you need it.

If you want blank text specifically for chat, the WhatsApp repeater is set up for the same workflow with a mobile-friendly copy button.

What people actually use it for

Legitimate, everyday reasons — not just pranks:

  • The blank-message joke. Sending an empty bubble to a friend who then asks “what?” is the classic use. One message, not a hundred.
  • Clean spacing in bios and captions. Instagram and TikTok collapse ordinary blank lines. A single U+2800 on its own line forces a real gap, so you can separate paragraphs in a bio.
  • Usernames and display names that read as “empty.” Some platforms won’t accept a blank name field; a blank character can satisfy the field while appearing nameless.
  • Placeholder content while testing. If you’re building a form or a chat feature, invisible characters are a good way to check how your input validation handles “looks empty but isn’t.”

Honest limitations

Invisible text is a novelty, not a superpower. A few things to keep in mind:

  • It’s still content, so spam rules still apply. Blank messages sent in bulk are spam. Platforms rate-limit and ban for spam whether or not the messages are visible — so don’t flood group chats.
  • Some apps reveal it. Search boxes, developer tools, and “show hidden characters” utilities will display the underlying code points. It’s hidden in normal views, not truly secret.
  • Behavior changes over time. Which characters survive filtering depends on the app version. If U+2800 ever stops working somewhere, try U+3164.
  • It can break accessibility. Screen readers may announce blank characters oddly, so avoid burying them in text meant to be read aloud.

Typing it manually

If you’d rather not use a tool, you can insert the character directly:

# The character itself (Braille Pattern Blank, U+2800):
⠀

# JavaScript
const blank = "⠀";

# Python
blank = "⠀"

# HTML entity
⠀

Copy the between the code fences above and it will behave the same way as the tool’s output.

Common questions

Frequently asked.

Most chat apps trim leading and trailing spaces and then refuse to send an empty message. A regular space (U+0020) gets stripped, so Send does nothing. A blank Unicode character like the Braille Pattern Blank (U+2800) is treated as real content, so the message sends but displays as nothing.

The Braille Pattern Blank (U+2800). It’s a normal, printable character with no visible glyph, so WhatsApp accepts it as content and shows an empty bubble. Zero-width characters like U+200B are often stripped and less dependable.

The occasional blank message or a blank line in a bio is harmless. But flooding a chat with hundreds of invisible messages is still spam, and platforms can rate-limit or ban accounts for spam regardless of whether the messages are visible. Use it in moderation.

Yes. The blank character is part of the text, so copy-paste carries it along. A tool that reveals hidden characters will show the underlying code points, but in normal chat views it stays invisible.

Related

More guides & tools.

Sources & standards

The technical claims on this page are based on primary specifications. Last verified 13 July 2026.