FFNick’s editorial policy explains how nicknames for Garena Free Fire and Free Fire MAX get onto this site: names sent through a submit form are reviewed before they appear, copied names pass automatic filters, and every in-game claim names the OB version and date it was checked.
| Step | What happens | Who | Result |
|---|---|---|---|
| 1. Submitted | The name is saved exactly as typed and held in a review queue. It is not shown anywhere yet. | Visitor | Pending |
| 2. Automatic filter | Links, code, page markup, empty strings, banned words and anything past 30 characters are refused. | Site software | Refused, or passed on |
| 3. Human review | A person reads the name against the rules below and approves or rejects it. | FFNick editor | Approved or rejected |
| 4. Published | The name appears in its category list with 0 likes and 0 dislikes; its position comes only from real votes. | Visitors vote | Public |
| 5. Re-check | Reported names are hidden at once and reviewed again; lists are re-read after each game update. | FFNick editor | Kept or removed |
On this page
Who edits FFNick
FFNick is edited by one person, Hoàng Dương Dũng, an independent web and app developer who also builds the generator and answers the inbox. There is no separate moderation team and no outsourced review, so every approval on the site is his decision. Our about us page covers how the site is run and how its lists are counted; this page covers the rules behind those lists.
How submitted names are reviewed
A name sent through a “Submit your FF name” form is never published straight away: it waits in a review queue until a person approves it. That is the one rule with no exception, because a name list is only useful if nothing offensive or misleading lands on it by accident.
The review looks at the name as a Free Fire player would see it, not as a string of code points. A person checks what the letters spell once the decoration is ignored, whether it pretends to be someone, and whether it tries to send readers somewhere else. Approved names keep their exact characters; rejected ones are deleted from the queue.
New names start at zero. FFNick does not seed a list with invented likes, copy counts or “popular” badges, so a category that has just opened shows 0 votes until visitors start voting.
What we reject
FFNick rejects a submitted name when it is obscene, impersonates someone, is spam or targets a group — whatever symbols it is wrapped in. Decorative characters do not change the meaning: a slur written in small caps or with combining marks is still a slur.
- Obscene or sexual names, including ones spelled with look-alike letters, numbers for letters (0 for o, 3 for e, 4 for a) or symbols placed between the letters.
- Impersonation: names that claim to be Garena staff, a moderator, an official account, or a named streamer or pro player — for example a “real” Raistar account. Styles inspired by a streamer are fine; claiming to be them is not.
- Spam: links, usernames on other apps, phone numbers, “free diamonds”, top-up offers, hack or mod promises.
- Hate and harassment: slurs, caste or religious insults, and names aimed at a real person.
- Empty or broken entries: strings that are nothing but spaces or invisible marks once trimmed.
What we deliberately keep: combinations that only look broken on a computer. Stacked marks, rare scripts and decorative brackets such as ꧁ ꧂ often display correctly in the game and on phones while showing boxes on a desktop browser, so an approved name is stored byte for byte as it was sent — never “cleaned up”.
How copied names are recorded
Tapping Copy on a nickname registers that exact string with the site’s shared library and adds one to its copy count; this happens automatically, without a human review. Because of that, copied names pass the same automatic filter as submissions — links, code, markup, empty strings and banned words are refused, and anything past 30 characters is cut — and they are removed by hand when reported.
Copies and votes are separate counters. A copy says someone used the name; a like says someone approved of it. Lists sorted by votes use only likes and dislikes, and no counter is ever typed in or adjusted by hand.
How names are tested in the Free Fire name field
A name counts as tested on FFNick only when it has been pasted into the rename field of Free Fire or Free Fire MAX and the result recorded with four facts: which app, which device, which OB version and which date. Anything without that record is marked “verify” instead of “works”.
| Field | Why it matters |
|---|---|
| App: Free Fire or Free Fire MAX | Both share one account and one name, but whether they filter every rare symbol identically has not been re-checked on OB55. |
| Device and keyboard | Boxes on screen often come from the phone’s fonts, not from the game refusing the name. |
| OB version | Garena can change the name filter with any update; the current version is OB55, released 16 September 2026. |
| Date | Lets a reader see how old the result is. |
| Result | Accepted, refused with a message, refused silently, or accepted but shown with boxes. |
Some results are well established and are stated as facts with their version: the no-break space U+00A0 works as a gap in the name field on OB55, while the Hangul filler U+3164 has been blocked since OB43. Other limits are not: Garena does not publish a list of accepted characters or an official length limit, and the 12-character figure most sites repeat has not been re-checked on OB55, so our pages call it a guide and say “verify”. The current rules we can stand behind are collected in the Free Fire name rules page.
How often lists are re-checked
Every FFNick list is re-read after each Free Fire OB update and at least once every 90 days, and its “last reviewed” date changes only when something was actually re-checked or changed. A routine re-save never moves the date.
- After an OB update: pages that make in-game claims are re-read first. The next update after OB55 is expected in December 2026 — until then OB55 stays the reference version.
- Every 90 days: each page is compared against what players actually search for and copy, dead styles are removed and new ones added.
- On report: a reported name is hidden straight away and reviewed before it can return.
How to report a broken or unwanted name
To report a name, email the exact text you copied, where you pasted it and what the game showed; a name you want removed is hidden first and checked second. Retyped names or screenshots cannot be tested, because look-alike symbols are different characters. The address and reply times are on the contact page, and removal requests follow the steps on the DMCA and name removal page.
FAQ
Does FFNick publish submitted names straight away?
No. A name sent through a submit form waits in a review queue and appears only after a person approves it. Names registered by tapping Copy pass automatic filters and are removed if reported.
Why does my name show 0 likes?
Because FFNick never seeds votes. A newly approved name starts at 0 likes and 0 dislikes, and only real visitor votes move it up a list.
Has every name on FFNick been tested in Free Fire?
No. Only names with a recorded test — app, device, OB version and date — are called tested. Everything else is marked “verify”, so paste it into the rename field before spending a Name Change Card.
Why was my name rejected?
Usually because it spelled something obscene under the decoration, claimed to be a staff member or a real player, or contained a link or contact detail. Symbols alone never get a name rejected.
These rules apply to every list on FFNick. Last reviewed by Hoàng Dương Dũng.