Invisible Character and Blank Text Copy and Paste

What an invisible character actually is

It is a normal Unicode code point whose glyph is nothing. The text is there, your cursor moves through it, a character counter counts it, but the renderer draws no ink. That is the whole trick.

It matters which family you pick. Zero width characters (U+200B, U+200C, U+200D, U+2060, U+FEFF) are classed as format characters. They occupy no width, and because software knows they are formatting, they are the first thing a sanitiser removes. Fillers such as U+3164 Hangul filler and U+2800 braille pattern blank are the opposite: as far as the software is concerned they are ordinary letters or symbols that happen to look empty, so they pass validation that rejects whitespace.

That is why a form which refuses an empty name will often accept U+3164. The string is not empty, and trimming whitespace does not remove it, because it is not whitespace. A plain space (U+0020) or a no-break space gets trimmed away and you are back to an empty field.

• Zero width: invisible and weightless, but easiest for a platform to strip.
• Fillers (U+3164, U+2800, U+115F): survive trimming and empty checks. Best for blank names.
• Spaces (U+00A0, U+2002 to U+200A): visible as gaps, useful for layout and indentation.
• Soft hyphen (U+00AD) is a special case: it appears as a hyphen if the word wraps at that point.

How to send a blank message

Copy U+2800 (braille pattern blank) or U+3164 (Hangul filler), paste it into the message box and send. Do not use the zero width space for this: most chat apps strip it or count the message as empty and refuse to send.

It generally works in WhatsApp, Telegram, Discord, Facebook Messenger, iMessage and plain SMS. Discord accepts the braille blank because the message is not whitespace-only. If one character does not go through, paste two or three, or try the other filler.

Some apps have closed this off. WhatsApp tightened its empty-message check more than once, so the result depends on your version, and a few clients will show the message as a small empty bubble or as a blank preview in the notification. There is no way to guarantee it across every app and every update.

Blank names in games

The usual method is to paste U+3164 into the name field, on its own for a fully blank name or between letters to create gaps. Among Us made this famous, and it has also worked at various times in Free Fire, PUBG Mobile, Mobile Legends, 8 Ball Pool and Call of Duty Mobile.

Whether it works today is a per-game, per-patch question. Studios add name validation precisely to stop this, so a character that worked last season can be rejected, replaced with a placeholder, or silently converted to a normal space after the next update.

Worth knowing before you spend a rename token: a blank or invisible name breaks reporting and moderation, so plenty of games list it under name policy violations. Roblox and Fortnite reject the characters outright. Others accept the name and then rename the account later. If the game's terms say display names must be readable, a blank name is a rule break even when the field accepts it.

• Try U+3164 first, then U+2800, then U+115F.
• If a single character is rejected, some fields accept two or three in a row.
• Check the game's naming policy before using a rename token on it.
• Never use an invisible character to impersonate another player. That is the fastest route to a ban.

Instagram bios, captions and line breaks

Instagram trims whitespace and collapses runs of blank lines, which is why a bio typed with three empty lines comes out as one paragraph. Putting an invisible character on each otherwise empty line gives the line something to hold, so the break survives.

For a bio: type the first line, press return, paste the character, press return, then type the next line. Repeat for each gap you want. The same approach works for captions and comments. If the caption box is fighting you, write the whole thing in Notes or Keep with the invisible characters in place and paste the finished text in one go.

This is less necessary than it used to be. Instagram now keeps line breaks typed directly in the app in most versions, so try it plainly first and only reach for the trick if your spacing collapses. Be sparing in comments: a comment consisting only of invisible characters is a classic spam signal and can get the comment hidden or the account rate limited.

Where invisible characters cause real problems

These characters are genuinely useful, and they also cause a specific set of bugs that are hard to see because the cause is invisible. It is worth knowing them before you paste one into something important.

The biggest category is silent rejection. Usernames, email addresses, domain names and payment fields are normalised or validated in ways that drop format characters, so your carefully placed U+200B disappears somewhere between the form and the database, or the record is saved with it and never matches again when you search for it.

Anti-spam systems treat them as a signal, because hiding characters inside words is a standard filter evasion technique. An invisible character in an email subject or in the middle of a word can raise the spam score of a message that would otherwise arrive fine.

• Search breaks: a zero width space inside a word means CTRL + F will never find that word.
• Code breaks: a zero width space in a JavaScript or Python file produces a syntax error on a line that looks perfect, and a U+FEFF at the top of a PHP file causes the headers already sent error.
• Spreadsheets break: a no-break space pasted in from a web page makes a number into text, so SUM returns zero and VLOOKUP misses.
• Accessibility: a screen reader has nothing to announce for a blank name, so it reads out nothing at all or reads the code point.
• Moderation: some platforms flag invisible characters as evasion and remove the post.
• Passwords and two factor codes: never, because you will not be able to retype it.

How to find and remove invisible characters

If you have inherited text that behaves oddly, the fix is to strip the characters rather than retype everything. In Microsoft Word, open Find and Replace, type ^u8203 in the Find box (8203 is the decimal value of U+200B), and leave the Replace box empty. Repeat with ^u65279 for the byte order mark and ^u160 for a no-break space, replacing that last one with a normal space.

In VS Code or Sublime Text, turn on regex search and look for [\u200B-\u200D\u2060\uFEFF] with an empty replacement. VS Code also highlights invisible and ambiguous characters in code by default, which is usually your first clue that one is there.

In Excel and Google Sheets, CLEAN is not enough: it only removes control characters 0 to 31, so it leaves both the no-break space and the zero width space untouched. Use =TRIM(SUBSTITUTE(SUBSTITUTE(A1,UNICHAR(160)," "),UNICHAR(8203),"")) to clear the two most common offenders and tidy the result.

• To see them, paste the text into a code editor with whitespace rendering turned on.
• LEN in a spreadsheet tells you the truth: a cell that looks empty with LEN of 1 holds an invisible character.
• On the command line, perl -CSD -pe 's/\x{200b}|\x{feff}//g' file.txt strips the common ones.