Facebook Messenger text formatting works through typed markers rather than a toolbar. An asterisk on each side gives bold, an underscore gives italic, a tilde gives strikethrough and a backtick gives monospace. There is no formatting button and no keyboard shortcut.
The catch is that support is not uniform across Messenger clients, and the markers are stored in the message rather than converted at send time. That means what your recipient sees depends on their app, not yours.
This is a different system from Facebook posts and comments, which have no formatting at all. If you landed here looking for the feed rather than chat, the Facebook posts and bio guide covers that side.
The four shortcuts
| Style | Type this | Marker |
|---|---|---|
| Bold | *bold* |
asterisk |
| Italic | _italic_ |
underscore |
| Strikethrough | ~struck~ |
tilde |
| Monospace | `code` |
backtick |
One marker on each side, not two. If you have come from a Markdown editor where bold takes **two asterisks**, Messenger will surprise you: two asterisks usually leave one visible.
The markers must touch the text. _ italic _ fails. _italic_ works. A single stray space is the most common reason formatting does not apply, and because there is no live preview you will not see the problem until the message is sent.
Which clients render the markers
This is the part worth being precise about, because a lot of guides state it as though it were settled.
The shortcuts have been most reliable on Messenger for desktop and in the browser at messenger.com or in the chat panel on Facebook on a computer. Reports of the mobile apps showing the raw symbols instead of rendering them are common, and the behaviour has changed across app versions more than once.
Rather than trusting any single account of it, including this one, test your own build. Message yourself, send one line of each of the four styles, then open the same thread on every device you use. That takes a minute and tells you exactly what your setup does. Behaviour described here reflects reports current in September 2026.
The important consequence: because the markers travel with the message, a recipient on a client that does not parse them sees *this* with the asterisks intact. Formatting in Messenger is a request, not a guarantee.
Where each field stands
| Field | Native formatting | Unicode | Recommended |
|---|---|---|---|
| Chat message | Yes, client dependent | Yes | Native shortcuts |
| Group chat message | Yes, client dependent | Yes | Native shortcuts |
| Group chat name | No | Yes | Unicode, short |
| Your Messenger display name | No | Restricted | Keep plain, name policy applies |
| Nickname for a contact | No | Yes | Unicode, short |
| Message reply and quote | Follows the original message | Yes | Native shortcuts |
Group chat names and per contact nicknames are plain text fields with no marker parsing at all, which is exactly where converted characters earn their place.
Your own Messenger display name comes from your Facebook profile, so Facebook’s name standards apply. Decorative characters there can get a profile flagged for identity confirmation, which is a high price for a slanted name.
How to italicize in Messenger, step by step
- Type the message normally.
- Put an underscore immediately before the first character of the phrase and immediately after the last one.
- Check there is no space inside either marker.
- Send.
- Read the sent bubble. If the underscores are gone, the client parsed it.
If you want bold and italic on the same phrase, nest them: *_both_*. Nest cleanly, because a marker that opens and never closes will usually leave every marker in the message visible.
Monospace is the one people underuse. A backtick pair around a booking reference, a serial number or a wifi password renders it in a fixed width face, which makes characters like l, 1, I and 0 far easier to tell apart. That is a genuine readability win rather than decoration.
Desktop, web and mobile in practice
The three ways people use Messenger behave differently enough to be worth separating.
Messenger for desktop and messenger.com. A physical keyboard makes the markers easy to type accurately, and this is where the shortcuts have been most consistent. It is also the only place where you can comfortably compose a longer message, check the markers before sending, and see the result immediately in a wide bubble.
The Facebook chat panel on a computer. Same parsing as the browser client in most reports, but the composer is smaller and it is easier to lose track of an unpaired marker in a long line.
The mobile apps. There is no formatting toolbar above the keyboard, so every marker is typed by hand, and mobile keyboards are the main source of failures. Smart punctuation can turn a straight backtick into a curly quote, and autocorrect will happily insert a space after a symbol. If a message that worked on your laptop fails on your phone, retype it on the phone and look closely at the characters rather than assuming the app dropped support.
Whatever your setup, the useful habit is the same: send the four test lines to yourself once, on every device you use, and stop guessing.
When Unicode is the better choice
Three cases.
A field with no markers. Group chat names and contact nicknames do not parse anything. If you want a styled group name, conversion is the only route.
A style Messenger does not have. The four shortcuts cover bold, italic, strikethrough and monospace. They do not cover cursive script, small caps, double struck or circled letters. If you want a group named 𝓯𝓻𝓲𝓭𝓪𝔂 𝓹𝓵𝓪𝓷𝓼, you are converting characters.
Consistency across clients. Because converted characters are characters rather than markup, they look the same on every client that has a font for them. If it matters that a phrase renders identically for everyone in a group, conversion is more predictable than the shortcuts.
The workflow: convert the phrase in the Italic Text Generator, copy the result, and paste it into the message or the name field.
What recipients actually see
Four outcomes, in rough order of likelihood.
- The formatting renders as intended.
- The raw markers appear because their client does not parse them.
- Converted characters render correctly, because their device has a font covering the Unicode block.
- Converted characters appear as boxes or question marks, because their device does not.
Outcome four is the one to plan around. It shows up most on older Android builds, on some in car and TV browsers, and on a few enterprise managed devices. WhatsApp users run into the same failure mode for the same reason, and our WhatsApp formatting guide covers how it looks on that side of Meta’s messaging stack.
A practical hedge: never put information that only exists in styled form. If the address is styled, put the plain address in the next line.
Copy, paste and search
Native markers and converted characters behave differently once a message leaves the thread.
Copy a natively formatted message and you get the markers back, because that is what is stored. Paste it into an email and you get *bold* rather than bold. Copy a converted phrase and the styling travels with it into anything, because the characters themselves carry the shape.
Messenger’s in app search matches literal text. A converted word will not be found by searching for its ordinary spelling, so a group name written entirely in script characters becomes hard to find in a long chat list. That is a real cost in a messaging app where search is how you find an old thread six months later.
Accessibility
Natively formatted messages keep their letters as letters. A screen reader receives the word italic and reads it as a word, whether or not the emphasis itself is announced.
Converted characters are separate code points. Depending on the reader and its verbosity setting, they can be spelled out one at a time using full Unicode character names, read as unrecognised symbols, or skipped entirely. A styled group name is announced on every notification from that group, which turns a small decorative choice into a repeated annoyance for anyone using a reader. What screen readers really announce covers the detail.
Where Messenger gives you a native shortcut, use it. That is the accessible option and it costs nothing.
Try it with yourself
- Open a chat with yourself, or start a group with one other account you control.
- Send four messages:
*bold*,_italic_,~struck~and`mono`. - Open the thread on your phone, then on a computer, and note which of the four rendered on each.
- Rename the chat using a converted phrase and check the chat list on both devices.
- Search the thread for a word that only exists in converted form.
Step three gives you a client compatibility map for your own setup. Step five shows you why converted text does not belong in anything you might need to find again.
Troubleshooting
Asterisks are visible in the sent message. A space inside the markers, an unpaired marker, or a client that does not parse the shortcut. Retype the phrase with the markers flush against the text and test again on desktop.
Two asterisks left one behind. Messenger uses a single marker. **bold** sends one asterisk through.
Formatting renders for you and not for the recipient. Their client, not yours. The markers are stored in the message and parsed on display.
A backtick turned into a curly quote. Some mobile keyboards substitute smart punctuation. Turn off smart punctuation for that keyboard, or paste the backtick from somewhere it is already straight.
A converted group name shows as boxes on one phone. That device is missing a font for the Unicode block. Rename the group in plain characters if any member reports it.
Monospace lost its spacing when quoted. Quoting a message re-renders it, and some clients drop the markers in the quote. Send the reference on its own line rather than inside a longer message.
Questions people ask about Messenger formatting
How do you italicize in Messenger? An underscore immediately before and after the words, with no space inside the markers. Send the message and the underscores disappear on clients that parse them.
What are the Messenger formatting shortcuts? Asterisk for bold, underscore for italic, tilde for strikethrough, backtick for monospace. All typed, one marker on each side.
Why does Messenger show my asterisks instead of bold text? Either a space slipped inside the markers or your client does not parse that shortcut. Desktop and the browser version have been the most consistent.
Does the recipient see the formatting? That depends on their client. The markers are stored in the message, so a client that does not parse them shows the symbols.
Should I use a font generator instead? For group names, nicknames, and styles Messenger has no shortcut for. Keep it short, and keep anything you might need to search for in ordinary letters.
Where that leaves chat
Messenger is a rare Meta surface with real formatting, and the four shortcuts are worth the muscle memory, particularly monospace for anything containing digits. Treat the rendering as best effort across clients, keep converted characters for names and styles the shortcuts cannot reach, and never let a styled string be the only copy of information someone might need.
Client behaviour summarised from MakeUseOf’s Messenger formatting walkthrough and The Windows Club’s comparison of Messenger and WhatsApp formatting, checked September 2026.
