How to Format Text on Bluesky: Bold, Italic & Styling Options

Bluesky has a built-in rich text toolbar that lets you bold, italicize, and strikethrough text directly in posts. No Markdown syntax, no third-party apps, no workarounds required for those three styles. Select any text in the compose box and a formatting popup appears. That puts Bluesky ahead of most social platforms when it comes to native text formatting.

But the toolbar only covers posts. Your display name, your bio, and anywhere outside the compose box are still plain text fields. And there are formatting options Bluesky simply doesn't offer at all — no headings, no code blocks, no bullet lists. This guide covers exactly what works, what doesn't, and how to fill the gaps.

How the built-in rich text toolbar works

The formatting toolbar appears in both the Bluesky web app and the official mobile apps. The workflow is the same everywhere:

1. Start typing your post in the compose box.
2. Select the text you want to format.
3. A popup toolbar appears with four options: Bold, Italic, Strikethrough, and Link.
4. Tap or click the one you want. The formatting applies immediately.

That's it. No Markdown syntax is involved. Typing **bold** or _italic_ in a Bluesky post will not render as formatted text — it will show the literal asterisks or underscores. The toolbar is the only way to apply native formatting.

You can stack styles. Select a word, bold it, then select it again and italicize it — you get bold italic. Strikethrough can layer on top of either. Links work the same way: select text, tap the link button, paste the URL.

What formatting does Bluesky actually support?

Here is the complete list of native formatting Bluesky supports in posts:

And here is what Bluesky does not support:

• No headings (H1, H2, etc.)
• No bullet or numbered lists
• No code blocks or inline code
• No underline
• No block quotes
• No Markdown rendering of any kind

If you need those formatting options, Bluesky is not the place for them. Long-form formatting belongs on a blog or newsletter; Bluesky posts are short-form by design, with a 300-character limit that keeps things concise.

How it works under the hood: rich text facets

Bluesky runs on the AT Protocol, and the formatting system is built into the protocol itself through something called rich text facets. Each facet is a byte-range annotation attached to the post text, marking a span as bold, italic, strikethrough, a link, a mention, or a hashtag.

This matters for two reasons. First, the formatting is real — it is not a visual trick or a Unicode swap. A bold word on Bluesky is the actual word with a formatting instruction, not a substituted character. Screen readers read it correctly. Search finds it normally. Second, because facets are part of the protocol, any third-party client or app that implements the AT Protocol can display the formatting. Most do, though support varies — some older or minimal clients may ignore strikethrough or render it inconsistently.

Where the toolbar doesn't reach

The rich text toolbar is limited to the post compose box. These fields are plain text with no formatting controls:

• Display name — plain text only
• Bio / description — plain text only
• Handle (username) — domain-based, no Unicode allowed

Your handle is tied to a domain (like yourname.bsky.social or a custom domain), so there is no way to style it at all. But your display name and bio are different — they accept Unicode characters, which opens the door to styled text.

Using Unicode styled text for display names and bios

Since the display name and bio fields don't have a formatting toolbar, the way to get a styled look is to paste Unicode characters that are already shaped to look bold, italic, or decorative. These are not formatting instructions — they are entirely different characters that happen to resemble styled versions of regular letters.

For example, instead of the letter "a" with bold applied, you use the character "𝖢" — a mathematically bold small a from the Unicode Mathematical Alphanumeric Symbols block. It looks bold on its own, so it stays bold anywhere you paste it, including plain text fields.

The Bluesky text formatter on BoldlyType generates these for you. Type your text, pick a style (bold, italic, script, gothic, bubble, and more), copy the output, and paste it into your display name or bio. No extension or app required.

A few things to know about the Unicode approach:

• It works visually, but it is not real formatting. Screen readers may not interpret it correctly.
• Search may not match it. Someone searching for your name won't find the Unicode version by typing the plain version.
• Not every device renders every glyph. Bold sans-serif is widely supported, but rarer styles (fraktur, double-struck) can show as empty boxes on some devices.
• Each styled character counts against your limit the same as a normal character. Bluesky counts grapheme clusters, so one styled letter is one grapheme.

For more on how this technique works across platforms, see how to format bold text.

Formatting in posts vs. display name vs. bio

Here is a quick reference for which formatting method works where:

The practical split is simple: use the native toolbar for posts, and use Unicode styled text (via a text formatter) for your display name and bio.

Third-party Bluesky clients and formatting

Because Bluesky is built on the open AT Protocol, several third-party clients exist. Most of them render bold, italic, and links correctly because those facets are well-established in the protocol. Strikethrough support is newer and less consistent — some clients display it, others ignore the facet and show the text without the line through it.

If you format a post with strikethrough in the official app and someone reads it in a client that doesn't support that facet, they see the plain text without the strikethrough. The text itself is not lost, just the visual effect.

Unicode styled text in display names and bios shows up across all clients, since the characters are part of the text data itself.

Tips for formatting Bluesky posts effectively

With only 300 characters to work with, formatting has to earn its place:

• Bold sparingly. One bold phrase per post draws the eye. Three bold phrases and nothing stands out.
• Use strikethrough for corrections or humor, not for emphasis. It reads as "I crossed this out on purpose."
• Links are formatting too. A well-placed link with descriptive anchor text beats a raw URL pasted at the end.
• Don't over-style your display name. A fully script-font display name can be hard to read at small sizes and may look like boxes on older devices. Mix one styled word with plain text for readability.
• Check your length. Styled Unicode and regular characters both count toward 300 graphemes, but it is still worth running your draft through a character counter before posting. See best free text formatting tools for social media for more options.

Frequently asked questions

Does Bluesky support Markdown?

No. Bluesky does not render Markdown in posts, bios, or display names. Typing **bold** or _italic_ will show the literal asterisks and underscores, not formatted text. Bluesky uses its own rich text toolbar for formatting — select text and tap the bold, italic, or strikethrough button in the popup.

Can you bold text in a Bluesky post?

Yes. Select the text you want to bold in the compose box and tap the B button in the formatting toolbar that appears. This works in both the web app and the official mobile apps. The bold is real formatting stored as a rich text facet in the AT Protocol, not a Unicode workaround.

How do you format your Bluesky display name or bio?

The display name and bio fields have no formatting toolbar. To get a styled look, paste Unicode styled characters generated by a tool like the Bluesky text formatter. The styled characters look bold, italic, or decorative on their own, so they work in any plain text field. Your handle (username) cannot be styled because it is domain-based.

What is the Bluesky character limit?

Bluesky posts are limited to 300 grapheme clusters. A grapheme cluster is what you see as a single character — a regular letter, an emoji, or even a complex emoji with skin tone modifiers all count as one grapheme. This is more generous than platforms that count bytes or UTF-16 code units. For the full breakdown, see Bluesky character limit.

Do third-party Bluesky clients support bold and italic?

Most third-party AT Protocol clients render bold and italic correctly because these facets are well-established in the protocol spec. Strikethrough support is less consistent — some clients display it, others show the text without the line. If formatting is important to your post, the official Bluesky app is the safest bet for both composing and viewing.