Native markup vs. Unicode substitution
WhatsApp's *asterisk* bold only survives inside WhatsApp — Unicode-substituted bold looks the same everywhere it's pasted.
WhatsApp Formatting vs. Unicode Text: Which to Use When
By fontgenerator.tech team · Published 2026-09-06 · Reviewed 2026-09-06
WhatsApp has its own native formatting syntax that's usually the better choice for a WhatsApp message specifically. Per WhatsApp's Help Center (cited below): wrap text in asterisks for *bold*, underscores for _italic_, tildes for ~strikethrough~, and triple backticks for monospace.
Native formatting vs. Unicode substitution
| WhatsApp native (*asterisks*, etc.) | Unicode substitution (this tool) | |
|---|---|---|
| How it works | WhatsApp parses the markers and applies real bold/italic formatting to ordinary characters | Different characters entirely — no formatting involved |
| Survives copy elsewhere? | No — paste it into another app and you'll usually see the literal asterisks | Yes — same characters, same look, everywhere |
| Combinable? | Bold+italic+strikethrough can combine; per WhatsApp, monospace can't combine with the others | Each style is separate; can't stack two styles on the same text |
| Works in every field? | Message text only | Anywhere plain text is accepted — bios, names, messages |
When to use which
- Emphasizing a word or line within a WhatsApp conversation: use WhatsApp's own asterisk/underscore/tilde syntax — it's built for exactly this and looks native.
- Styling your WhatsApp display name, or text you'll copy somewhere other than a live WhatsApp chat (a bio, a document, a different app): use Unicode substitution — WhatsApp's own markers won't survive the trip.
- Combining both: you can wrap Unicode-styled text in WhatsApp's asterisks too, though the visual difference will be subtle since the Unicode characters are already bold-looking.
A caveat on cross-platform behavior
We haven't run our own device tests confirming this formatting behaves identically across WhatsApp for iOS, Android, and Web (see testing methodology) — the syntax above reflects WhatsApp's own published documentation, not our first-hand test across every client.
A worked example
Typing *Meeting moved to 3pm* — see you there into a WhatsApp message renders as a bold "Meeting moved to 3pm" followed by ordinary text, per WhatsApp's own formatting rules. Copy that exact message into an email, a text document, or a different chat app, and per those markers' design you'll typically see the literal asterisks reappear, because the bold was WhatsApp's own rendering choice, not a property of the text itself. Compare that with styling "Meeting moved to 3pm" using this site's Bold Text Generator instead: the result pastes as 𝐌𝐞𝐞𝐭𝐢𝐧𝐠 𝐦𝐨𝐯𝐞𝐝 𝐭𝐨 𝟑𝐩𝐦 — different actual characters — and it looks the same bold wherever you paste it next, WhatsApp or otherwise, because there's no formatting to lose.
Why WhatsApp's syntax uses those particular symbols
Asterisks, underscores, tildes and backticks are a lightweight, keyboard-only markup convention with a long history in plain-text messaging and programming contexts (similar conventions appear in Markdown and many chat/IRC clients) — no special keyboard or copy-paste step is needed, which fits WhatsApp's design as a fast, typed-message-first app. Unicode substitution takes the opposite tradeoff: it requires copying pre-generated characters (since there's no keyboard shortcut for "type a Mathematical Bold A"), but in exchange the result isn't tied to WhatsApp's own parser at all.
What happens if you paste Unicode-styled text and add WhatsApp markers around it
WhatsApp's parser looks for the literal asterisk/underscore/tilde/backtick characters surrounding a run of text and doesn't inspect what that text actually contains — so wrapping already-bold Unicode text in asterisks doesn't cause an error, it just layers WhatsApp's own bold rendering (where supported) on top of characters that already look bold. In practice the visual difference is usually subtle to nonexistent, since the Unicode characters are already heavier-weight than the surrounding plain text. Where this combination is more useful is with a lighter style — for example wrapping small-caps or script text in WhatsApp's asterisks, which layers two visually distinct effects rather than two versions of the same one.
The reverse combination is worth knowing too: if you paste text that already contains literal asterisks as part of its actual content (a math expression, a footnote marker, a username with an asterisk in it) into a WhatsApp message, those asterisks can accidentally trigger bold formatting you didn't intend. This is a WhatsApp-side quirk of using ordinary punctuation as a formatting signal, not something either this tool or WhatsApp's own documentation flags prominently, but it explains an occasional "why did part of my message go bold?" surprise.
Where each approach actually gets used across a typical conversation
| Task | Better choice | Why |
|---|---|---|
| Emphasizing one word in a message you're typing right now | WhatsApp native (*asterisks*) | Fastest, no copy-paste needed, looks native to the app |
| A styled WhatsApp profile name | Unicode substitution | Profile name fields don't parse WhatsApp's message markers at all |
| Text you'll paste into WhatsApp and reuse elsewhere (a bio, a business card) | Unicode substitution | Survives the trip to other apps; native markers don't |
| A quoted code snippet or command in a tech-support chat | WhatsApp native (monospace) | Purpose-built for exactly this and widely understood by other WhatsApp users |
Why WhatsApp's approach doesn't generalize to other apps
It's tempting to assume every messaging app supports the same asterisk-for-bold convention, since several do, but it's never universal — some apps use different markers, some support a subset (bold only, no strikethrough), and many plain-text fields (a bio, a search box, a form field) don't parse any formatting markers at all and will just show the literal punctuation. Unicode substitution sidesteps this entirely by never depending on any app choosing to interpret a marker in the first place — the character already looks the way it looks, everywhere.
Questions people actually ask
Can I use WhatsApp's bold syntax on my WhatsApp display name? No — per WhatsApp's documentation, that formatting syntax is specific to message text; profile name fields don't parse the asterisk/underscore markers, so styling a display name requires Unicode substitution instead.
What happens if I put asterisks around Unicode-bold text? WhatsApp will likely still try to apply its own bold formatting on top, though since the characters already look bold, the visual difference will probably be minor — we haven't verified this combination first-hand across clients.
Does WhatsApp support underline? Not as a native message-formatting option per its published help documentation, which lists bold, italic, strikethrough and monospace only. Unicode substitution (this site's strikethrough/underline generator) can produce an underline effect anywhere, including where WhatsApp's own syntax doesn't reach.