WhatsApp is rolling out an opt-in @username so people can message you without ever seeing your phone number. The rules are strict — 3 to 35 characters, lowercase only, no styled Unicode — and it's a brand-new locked field sitting next to the Display Name most fancy-text users already style.
WhatsApp opened @username reservations globally on June 29, 2026, and has been switching reserved usernames on for users on a rolling basis since — some are already seeing their username go active. The stated goal is privacy: a username lets a new contact reach you without ever seeing your phone number, which WhatsApp confirms remains required to create and hold an account in the first place. This isn't a replacement for the phone number — it's an additional, optional layer on top of it.
WhatsApp also has no username directory or discovery search, so a username only works if the other person already knows it — closer to a Discord handle than a searchable social profile.
The rules for the username itself are strict: 3 to 35 characters, lowercase letters and numbers only, plus periods and underscores, and it must contain at least one letter (an all-numeric string isn't allowed). It also can't start with "www." or end in a domain-style suffix like .com or .net — guardrails against usernames masquerading as web addresses.
WhatsApp actually has three separate text fields with three separate rule sets — and the new one is the strictest by far:
| Field | Length | Allowed characters | Styled Unicode? | Status |
|---|---|---|---|---|
| @Username (new) | 3–35 | Lowercase a-z, 0-9, . _ — must include a letter | ✗ Never — plain ASCII, unique per person | 🆕 Rolling out since Jun 29, 2026 |
| Display Name | 25 | Broad Unicode | ✓ Accepts styled Unicode | Unchanged, standing policy |
| About / bio | 139 | Broad Unicode | ✓ Accepts styled Unicode | Unchanged, standing policy |
The username is unique across all of WhatsApp, which is exactly why it's locked to plain ASCII — the same impersonation and searchability reasons every platform's account-handle field gives for staying strict. Your styled Unicode name still belongs on the Display Name, untouched by this change.
This is the exact pattern our WhatsApp font generator already exists to serve on the permissive side: a locked, plain-ASCII account handle underneath a Unicode-friendly display layer. Discord, Instagram and Roblox all split the same way — the mistake is always pasting a decorated name into the strict field instead of the free one. Paste ꧁𝓔𝓶𝓶𝓪꧂ into the new @username box and it'll bounce; put it in your Display Name and it works exactly as it always has.
Run any candidate username through our character counter before you commit — it'll catch the 3–35 length rule instantly, faster than trial-and-error inside the app. And because the field requires at least one real letter and rejects anything outside a-z0-9._, the invisible-character tricks covered on our invisible character page (blank names, spacer characters) won't get you anywhere here — they still work fine on the Display Name, just not on this new locked handle. WhatsApp's native *bold*/_italic_ chat formatting is untouched by any of this — see WhatsApp text formatting explained for where that does and doesn't apply.
WhatsApp says broader availability keeps rolling out by country through the rest of 2026 rather than landing on one fixed global date, so reserved usernames not yet live should keep switching on progressively. We'll update this entry if the character rules change, if WhatsApp adds a username directory or discovery search, or if the rollout completes broadly enough to call this "done" rather than "in progress."
Your WhatsApp Display Name still takes full Unicode — build one, check the length, and paste it in.
Open the WhatsApp Font Generator →Reservation-opening date and phone-number policy per TechCrunch's coverage of WhatsApp's username reservations and 9to5Google's report on the same launch; character-rule specifics per Business Today's breakdown of the allowed-character rules; rollout-in-progress status per MacRumors' July 2026 update.