Free Fire invisible space not working? Understand the codes and how to check

English version | Free Fire invisible space not working? We use test data to explain the character codes and how to check them step by step

Author: LetrasDiferentes operations team
Updated: October 18, 2026
Reading note: The Unicode data in this article comes from reproducible local experiments. We did not pay to change a name on a real Free Fire account, so we do not claim that any character will definitely work or has an “XX% success rate.”

If you clicked “copy invisible space” on a website, went back to Free Fire, and put it in your nickname, only to find that there is no visible gap, the input field removes the character, or a message appears when you save, we suggest not rushing to try another code.

The main point: “Copied successfully” does not mean “the game will save it.” These are two different things. We suggest first checking which Unicode character you copied, then whether the input field keeps it, and only then thinking about saving. In particular, do not keep spending diamonds just to test a character.

1. A small experiment: are five kinds of “blank” really the same thing?

No. We tested a very simple name: Ana + one character to test + Silva. Without the character in the middle, the name always has 8 English letters.

The experiment used Python 3.13.5, with its built-in Unicode character database version 15.1.0. For each sample, we read the Unicode code, counted the characters and UTF-8 bytes, and tested common text-processing methods. You can reproduce this with the same script at the end of the article.

This table shows us three things:

1. Even if you cannot see anything, it still counts as a character. All five examples have 9 Unicode code points. Being invisible does not mean a character is not counted.
2. The byte counts differ. With the same name, changing the middle character changes the UTF-8 length from 9 bytes to 10 or 11 bytes. However, this does not mean Free Fire limits nicknames by UTF-8 bytes. The game's own rules or actual testing are needed to establish what limit it uses.
3. Some characters change during text processing. In our Python experiment, U+00A0 became a regular space, U+0020, after NFKC processing; U+3164 became U+1160. This only shows that text-processing programs can potentially change characters. It does not mean Free Fire necessarily uses the same processing.

We also ran a more visual little experiment: we put one blank character on each side of Ana, then ran Python's strip() to remove whitespace from both ends of the string. Regular spaces and U+00A0 were removed; U+200B, U+3164, and U+2800 remained.

This also explains why we do not suggest treating every character labeled “hidden space” online as the same thing. Different programs really can process them differently.

Limits of the experiment: The numbers above come from local string tests, not from pasting or saving in the game. We did not measure Free Fire's acceptance rate for these five characters in this experiment.

2. What are the three codes most often confused with each other?

U+3164: Hangul Filler, which looks like a space

The main copy button in our LetrasDiferentes invisible character tool provides U+3164 (Hangul Filler). Its official Unicode name is Hangul Filler, not a regular keyboard space.

It is often used as a “blank separator” between parts of a nickname. However, being able to copy it does not mean the game will accept it. The tool itself cannot validate a name change on the game's behalf.

U+200B: Zero Width Space, which really has no width

The official name of U+200B is Zero Width Space. It is often used to mark possible line-break positions and usually does not create a visible gap between two words.

So, if you want a nickname to look like Ana Silva, but the two words are almost touching after you copy U+200B, that does not necessarily mean copying failed. It may simply be because this character is not meant to display a blank space.

U+00A0: a no-break space, not a nickname pass

U+00A0 is called No-Break Space and often appears in web text. It looks much like a regular space. The main difference is that it is meant to prevent an automatic line break at that position.

Our tests showed that Python's strip() can remove it and that NFKC turns it into a regular space. When using it as a “special nickname space,” you cannot assume it will get around the game's input rules just because it looks the same.

A quick note about U+2800: it is called Braille Pattern Blank. Many fonts display it as a blank space, but Unicode explicitly says it does not act as a regular space. We included it in the local comparison table to help identify the codes. Our website's invisible character detector currently does not include U+2800 in its list of supported characters, so do not expect the tool to flag it automatically.

3. Copied it but it does not work? Check these four steps

There is no need to start by trying ten different codes. We suggest checking in the following order to save time and make it easier to see where the problem happens.

Step 1: identify the character you copied

Open the LetrasDiferentes invisible character page and select 1 character first, rather than copying several at once. The main button copies U+3164.

Place it between two pieces of plain text, for example between Ana and Silva. This is easier to check than pasting something “invisible” on its own.

Step 2: paste it back into the detector and check the code

On the same page, find “Test invisible characters” and paste the name you just made.

Our website currently detects U+00A0, U+200B, U+200C, U+200D, U+2060, U+3164, and U+FEFF, and shows each character's position. This can prove which character is in the text pasted into the detector. It cannot prove Free Fire will save it.

If you meant to copy U+3164 but the detector shows another code, first check whether you copied the text again from a chat app, clipboard manager, or another page along the way.

Step 3: check the game's input field before confirming the name change

Paste the name into Free Fire's nickname field and check three things first:

• Is the visual gap you want still there between the two parts?
• Does the input field immediately remove, replace, or cut off characters?
• Is there a length, format, or other error message?

If anything already looks wrong while entering the name, we suggest stopping. Do not click a paid confirmation just to test a blank character.

Step 4: if it fails, make a minimal comparison instead of changing five things at once

We suggest comparing three simple pieces of text:

Note: [U+3164] and [U+200B] in B and C are character labels written to make the article readable. Do not copy the whole sequence of letters and square brackets as a nickname. Use the actual Unicode characters and check them with the detector.

If A works in the input field but B and C behave differently, we at least know that the difference may be related to the added character. But this alone still cannot prove which filtering algorithm the game uses. If A also gives an error, consider naming rules, length, or other conditions first, rather than blaming everything on the “invisible space.”

4. How would we assess these situations?

Garena Brazil's official help center explicitly recommends avoiding special characters where possible in its nickname-change instructions, because settings on different devices may prevent them from displaying properly. It also says that changing a nickname can involve diamonds or a name-change card. We think this is worth reading before any list of “100% working invisible spaces in 2026.” Read Garena's official instructions

5. Common questions about invisible spaces

Do invisible spaces not count as characters?

They do count. Each of our five local samples has 1 more Unicode code point than AnaSilva. There are different ways to count “characters,” though. We cannot use Python's results to decide how the game calculates nickname length.

Are “large spaces” and “small spaces” official Unicode categories?

No. These names online may refer to completely different characters. We suggest remembering codes such as U+3164, U+200B, and U+00A0, so at least you do not copy the wrong character.

Which one should we try first?

If you want to use our website's existing copy tool, you can start by checking 1 U+3164, because the tool clearly tells you what you copied. “Try first” here only means it is convenient for troubleshooting, not that we have verified it has the highest success rate in Free Fire.

Is there an invisible space that works 100% of the time?

We have no such evidence and will not make that guarantee. Whether a character can be pasted, saved, and displayed may depend on nickname-field rules, the game version, and the device. When a character is not supported, we recommend an ordinary, clear nickname that follows the platform's rules, rather than adding more and more invisible characters.

6. One final reminder

The most useful result of this experiment is not finding a “magic character,” but separating the questions:

What is the Unicode character? → What did we actually copy? → What did the game's input field keep? → What did the final nickname display?

We can confirm the first two steps with local experiments and detection tools. The last two depend on your actual game environment.

When you need the tools, you can open them directly:

• Copy and check invisible characters | LetrasDiferentes
• Create Free Fire nicknames | LetrasDiferentes