WhatsApp is the one messaging app on this site that has real text formatting of its own, and that changes the advice completely. Everywhere else, unicode styling is the only option. Here you have two, they do not combine, and picking the wrong one produces a message full of visible asterisks. The rule that settles it is simple once you know why the two are incompatible.
Surround a word with asterisks and WhatsApp renders it bold. Underscores give italic. Tildes give strikethrough. Three backticks on each side give monospace.
These are parsed by the app when it displays the message. The characters you typed are still asterisks and letters in the stored text; WhatsApp reads the pattern and applies the formatting when drawing.
That makes them genuinely different from unicode styling. The formatting is a property applied to your plain letters rather than a replacement for them. Your text stays searchable, quotable, readable by a screen reader, and the same length it was before, because the wrappers cost four characters total no matter how long the word is.
The WhatsApp page offers all four as copy formats, which no other page on this site does, because no other network has them.
WhatsApp's parser looks for its wrappers around ordinary characters. Wrap a mathematical bold word in asterisks and one of two things happens: the app applies bold to characters that are already fixed bold glyphs and nothing visibly changes, or the pattern fails to match and the asterisks are left sitting in the message where everyone can see them.
Either way you have spent four characters and gained nothing.
That is why the WhatsApp copy formats on this site wrap the raw text rather than the styled text. Choosing the bold wrapper gives you your plain words with asterisks around them, not your styled words with asterisks around them. Mixing the two is the mistake the format is designed to prevent.
So treat them as alternatives. Formatting or unicode, not both.
In a message body, use WhatsApp's own formatting. It is free in characters, it reads correctly to a screen reader, the recipient can search for the words, and it renders identically on every device running WhatsApp because the app is doing the drawing.
In the About field, use unicode styling, because the wrappers are not parsed there. Asterisks in an About line show up as asterisks.
In a group name or a contact name, unicode again, for the same reason.
That is the whole decision. Formatting is a message-body feature. Everywhere else in the interface, the only way to change how text looks is to change which characters it is made of, and that means the fancy text generator or the WhatsApp styles page.
The WhatsApp About line caps at 139 characters, which is a slightly awkward number and tighter than most people assume. It is less than an Instagram bio and less than an X bio.
A message, by contrast, allows 65,536 characters. The two fields are four orders of magnitude apart, and advice about one is useless for the other.
That gap is why the WhatsApp page here has a field selector. The badge on every style counts against whichever field you picked, so the same style shows as comfortable for a message and as an overflow for an About line.
At 139 characters, the styles worth using are the cheap ones. A frame costs a fixed four to twelve characters. An overlay style like strikethrough costs roughly one character per letter and will take a short phrase past the limit on its own.
The WhatsApp page shows fewer styles than the general generator, and the filter is arithmetic rather than taste.
Styles whose cost grows with the length of your text are excluded, because a 139-character field cannot absorb them. So are styles that add more than a few characters of fixed overhead.
What is left is the set that fits: substituted alphabets that exchange one character for one character, small frames, and the cheap blocks that cost one storage unit per letter.
There is a toggle to show the full list if you want it, because nobody should be stuck inside a filter. But the default is the set that will actually fit in the field you are writing for, which is more useful than three hundred rows most of which overflow.
A point in favour of WhatsApp's own formatting that is easy to miss: it travels correctly.
A forwarded message keeps its wrappers, so the bold stays bold for the next recipient. A quoted reply keeps them. A message copied out to another app arrives with the literal asterisks, which is ugly but recoverable, because the words underneath are intact.
Unicode styling also travels, but it travels as characters, which means it arrives in the other app exactly as it left: still styled, still unsearchable, and still liable to render as boxes if the receiving device has thin font coverage.
For anything that might be forwarded outside WhatsApp, the wrappers are the safer choice. For anything that stays inside a name or About field, unicode is the only choice.
Three backticks on each side give monospace, and it is the wrapper people use least and should use most.
Monospace is the right format for anything that has to be transcribed accurately: a reference number, a code, a serial, an address, a command. Fixed-width characters make it easy to tell a zero from a letter O and a one from a lowercase L, which is exactly where handwritten and typed transcription goes wrong.
It also visually separates the string from the sentence around it, so the recipient can see where the value begins and ends without you adding quotation marks.
Four extra characters at each end, no length penalty on the content, and a meaningful reduction in the chance that someone reads it back wrong.
Group names are where unicode styling earns its place on WhatsApp, because there is no formatting alternative and the field is visible constantly.
Frames work well there. A frame leaves your letters as ordinary characters and adds ornaments around them, so if a member's device cannot draw an ornament they lose the ornament rather than the name.
Substituted alphabets are riskier for the same reason they are always riskier: if the glyphs are missing, the entire group name is rectangles, and unlike your own profile you will not be the one seeing it.
WhatsApp runs on a very wide range of Android devices, many of them older and with limited font coverage, which makes this more of a live concern here than on platforms with a narrower device base.
Message body: use asterisks, underscores, tildes and backticks. Free, accessible, searchable, reliable.
About line, group name, contact name: use unicode, keep it cheap, and remember the About field is 139 characters.
Never both on the same text, because the parser works on plain characters and styled text is not plain.
And if you need the plain version of something already styled, the plain text converter will give it back.
Occasionally you send a formatted message and the recipient sees the asterisks. There are a few reasons and they are worth telling apart.
The wrapper must sit against the word with no space between. An asterisk followed by a space is punctuation as far as the parser is concerned, so it is left alone and displayed.
The pair must both be present. An opening wrapper with no closing one is not a pattern, so nothing is applied.
Punctuation inside the wrapper is fine, but a wrapper inside a word can fail, because the parser looks for boundaries.
And the message must be going somewhere WhatsApp renders. Copy a formatted message out to another app and the asterisks come with it, since they were always literal characters in the stored text.
That last one is the most common surprise. The formatting was never attached to the words; it was a pattern WhatsApp recognised, and outside WhatsApp there is nothing to recognise it.
A WhatsApp message allows 65,536 characters, which is long enough that length stops being a constraint and readability becomes one instead.
At that size, styled text works against you. A long message in a substituted alphabet is slower to read, cannot be searched within the chat, and is announced badly by a screen reader. The same message in plain text with the app's own bold on a few key phrases is easier to read and easier to find later.
What helps at length is structure rather than styling. Line breaks between ideas. A short first line that says what the message is about, since that is what shows in the chat list preview. Monospace for anything that has to be transcribed.
The styling tools here earn their place in short fields where there is no formatting available. In a long message with formatting available, they mostly cost you something and return very little.
No. The parser applies formatting to plain characters, and styled letters are already fixed glyphs. You either see no change or you see the asterisks.
139 characters. A message allows 65,536, so advice about one does not transfer to the other.
Four in total per wrapped run, regardless of how long the run is. Unicode styling costs per letter, which is why the wrappers are cheaper for anything long.