Does Threads support bold and italic text? Partially. Native formatting exists in exactly one place — the long-form text attachment editor, where a toolbar gives you bold, italic, underline, and strikethrough. Regular posts, replies, and bios are plain text, so the only way to style them is pasting Unicode characters like 𝗯𝗼𝗹𝗱 and 𝘪𝘵𝘢𝘭𝘪𝘤.
That "partially" is the detail most guides get wrong. Some claim Threads has no formatting at all; others promise markdown tricks that have never worked there. The truth splits cleanly down the middle, and once you know where the line sits, getting bold text on Threads takes about ten seconds.
Threads gives you two different writing surfaces, and they behave nothing alike.
The first is the regular composer — the box you use for everyday posts and replies. It holds up to 500 characters, and it is plain text, full stop. There is no formatting toolbar and no markdown parsing. Type **bold** or _italic_ and Threads publishes the asterisks and underscores exactly as you typed them. Your bio works the same way.
The second surface is the text attachment, a long-form option Threads shipped in September 2025. Add one to a post and you can write up to 10,000 characters — and this editor has real formatting. Select some text and toolbar buttons apply bold, italic, underline, or strikethrough. It is the only place on Threads where native rich text exists.
So the honest answer to "does Threads have bold?" is: yes inside text attachments, no everywhere else. Everywhere else, you need a different approach.
One structural quirk worth knowing before we get there: Threads accounts ride on Instagram. Your Threads handle is your Instagram handle, with the same username rules — letters, numbers, periods, and underscores, up to 30 characters. Usernames can never be styled on either app. If you write captions for both platforms, the same Unicode method below works in an Instagram text formatter too.
How to bold text in a normal Threads post
Since the regular composer ignores formatting commands, you don't format the text — you swap in characters that are already bold. Unicode, the character standard behind every modern keyboard, includes entire extra alphabets: mathematical bold (𝗯𝗼𝗹𝗱), italic (𝘪𝘵𝘢𝘭𝘪𝘤), bold italic (𝙗𝙤𝙡𝙙 𝙞𝙩𝙖𝙡𝙞𝙘), monospace (𝚖𝚘𝚗𝚘), and more. Each styled letter is its own character, so the look is baked in. Threads doesn't need to support formatting; it simply displays the characters you paste.
Here's the whole process with the free Threads text formatter:
- Type or paste your text into the formatter.
- Scroll the live previews and pick a style — 𝗯𝗼𝗹𝗱 for emphasis, 𝘪𝘵𝘢𝘭𝘪𝘤 for asides, 𝚖𝚘𝚗𝚘 for a code-like look.
- Tap copy next to the version you want.
- Paste it into your Threads post, reply, or bio.
That's it. The styled text publishes like any other text, looks the same to every follower, and survives copy-paste anywhere else you need it.
Two practical notes. First, the 500-character cap still applies, and styled characters can count differently than they look — a post that reads as 480 characters on screen can overflow after styling. If you're running close, the Threads character limit guide covers how the counter treats them. Second, paste rather than retype: styled characters aren't on your keyboard, so the copy button is the whole workflow.
Using the native text attachment toolbar
For longer writing, skip the Unicode route entirely and use the surface Threads built for it.
Add a text attachment to your post and you get a long-form editor with a 10,000-character ceiling. Select any stretch of text and tap the toolbar buttons — bold, italic, underline, strikethrough — and the formatting applies the way it would in a document editor. Because this is native rich text rather than substituted characters, the words underneath stay ordinary letters. They read normally and carry none of the Unicode trade-offs covered below.
When to reach for it: essays, announcements, changelogs, anything with structure. When not to: the quick 500-character post that makes up most of Threads. Nobody attaches a document to say one sentence, and that's exactly the case Unicode styling handles.
Strikethrough, monospace, bullets, and line breaks
Here's the full picture, format by format:
| Format | Native on Threads? | How to get it |
|---|
| Bold | Only in text attachments | Toolbar there; paste Unicode 𝗯𝗼𝗹𝗱 in posts, replies, and bios |
| Italic | Only in text attachments | Toolbar there; paste Unicode 𝘪𝘵𝘢𝘭𝘪𝘤 elsewhere |
| Underline | Only in text attachments | Toolbar there — no dependable option in regular posts |
| Strikethrough | Only in text attachments | Toolbar there; s̶t̶r̶i̶k̶e̶ via combining characters (U+0336) elsewhere |
| Monospace | No | Paste Unicode 𝚖𝚘𝚗𝚘𝚜𝚙𝚊𝚌𝚎 from a generator |
| Bullet lists | No | Paste a • character at the start of each line |
| Line breaks | Yes | Press Return in the composer |
A few of these deserve a sentence. Strikethrough outside attachments works by stacking a combining character (U+0336) onto each letter, which draws the line through it — and like other less common styles, it's the kind most likely to render as boxes on aging devices, so preview it. Monospace has no native home anywhere on Threads; 𝚖𝚘𝚗𝚘 paste is the only route. And line breaks are the one piece of structure the regular composer fully supports: press Return and the break publishes exactly where you put it, which covers most of what a readable post actually needs.
The trade-offs nobody mentions
Unicode styling fills a real gap, but it has three costs, and a guide that skips them isn't being straight with you.
Screen readers struggle with it. Styled characters sit at different code points than regular letters, and many screen readers announce them one code point at a time — "mathematical bold small b, mathematical bold small o…" — or skip them outright. A post written entirely in 𝗯𝗼𝗹𝗱 can be unlistenable for a blind follower. Our guide to screen readers and fancy text shows exactly what that sounds like.
Search can't see through it. To a search index, 𝗯𝗼𝗹𝗱 and bold are different strings. A styled keyword won't match anyone's query, and a styled hashtag won't join the tag it names. Keep every word you want found in plain text.
Old devices sometimes show boxes. Common bold and italic ranges render almost everywhere, but rarer styles can appear as □□□ on older systems missing the glyphs.
All three point to the same rule: style a word or a phrase for emphasis, never a whole post. Used that way, the downsides barely register and the emphasis still does its job.
Threads rewards a conversational voice. Formatting should serve that voice, not shout over it.
- Bold the hook, not the paragraph. One 𝗯𝗼𝗹𝗱 phrase at the top of a post earns the pause; five cancel each other out.
- Use line breaks generously. Short paragraphs with real breaks read better in the feed than any styled wall of text.
- Build lists with • plus a Return. It's the closest thing Threads has to bullets, and it scans cleanly.
- Keep handles, links, and hashtags plain. Handles can't be styled anyway, and hashtags stop working the moment you try.
- Go long in a text attachment. Heavy formatting is usually a sign the post wants to be an attachment, where the toolbar does it properly and accessibly.
- Leave counter headroom. Styled characters can count against the 500 differently than they look.
Bold text on Threads comes down to knowing which surface you're standing on. Inside an attachment, use the toolbar. Everywhere else, paste the style in — and spend it only on the words that deserve it.
