A browser-based tool that converts plain text into Unicode-styled text. The styled output looks bold, italic, monospace, small-caps, or fullwidth when pasted into LinkedIn, Instagram, X, and other platforms that strip away normal formatting.

No. All transformations happen in your browser. Your draft never leaves your device when you use the web interface. See the Privacy Policy for full details.

Yes, on LinkedIn, Instagram, X, Bluesky, Threads, and most modern platforms. Each "styled" character is a real Unicode code point, not a formatting tag, so it pastes through cleanly.

The exception is platforms or apps that explicitly normalize Unicode (some email clients, e-readers, and older CMS editors). Always preview on the platform you'll publish to.

It's text that uses alternative letter shapes defined by the Unicode standard — primarily the Mathematical Alphanumeric Symbols block (U+1D400–U+1D7FF) and the Halfwidth and Fullwidth Forms block (U+FF00–U+FFEF). The shapes look like bold, italic, sans, mono, or fullwidth versions of the alphabet, but each one is a separate character.

See the Unicode Styling Explained page for more detail.

When on, the tool auto-detects headers and applies your chosen header style. It treats a line as a header if any of the following are true:

• The line starts with a Markdown # heading marker
• It is the first line of your draft (and is reasonably short)
• It is short and ends in : or ?
• It is short, all-caps, and near the top
• It is short and the next line is blank

Turn it off if you want everything styled with the body style and no header detection.

Header style is applied to lines the tool identifies as headers. Body style is applied to everything else.

A common pattern: bold sans for headers, plain for the body. Keeping the body plain is better for both accessibility and reach.

They apply a Unicode style to whatever text you have selected in the Input panel:

• B — Bold serif (𝐁𝐨𝐥𝐝)
• I — Italic serif (𝐼𝑡𝑎𝑙𝑖𝑐)
• M — Monospace (𝙼𝚘𝚗𝚘)
• SC — Small caps (sᴍᴀʟʟ ᴄᴀᴘs)
• FW — Fullwidth (Ｆｕｌｌｗｉｄｔｈ)

Select the text first; otherwise the tool will prompt you to make a selection.

They're hidden by default. Underline and strikethrough use Unicode combining marks, which screen readers handle poorly and which some social platforms render inconsistently.

To enable them, turn off Safe accessibility mode in the Formatting panel.

It hides the underline and strikethrough buttons because their combining marks are unreliable for assistive technology. Safe mode prevents you from accidentally using them. Turn it off only when you know your audience and platform support them.

It shows the share of styled (non-plain) characters in your output:

• Light — under 20% styled
• Balanced — 20%–55% styled (recommended)
• Heavy — over 55% styled

Heavy emphasis is harder to scan, more likely to look gimmicky, and harder for screen readers. The check list below the meter calls out specific risks.

It changes the character target the counter checks your output against:

• LinkedIn — 3,000 chars (LinkedIn post limit)
• Instagram — 2,200 chars (caption limit)
• Profile — 260 chars (LinkedIn headline)

A warning appears in the readability checks if your styled output exceeds the target.

They change the bullet character added to lines that don't already start with a bullet:

• Dot — • (U+2022)
• Check — ✓ (U+2713)
• Arrow — → (U+2192)

Choose Preserve lines if you want to keep the draft as-is.

The device or app you're viewing the text on doesn't have a font that includes those Unicode code points. This is rare on modern desktops and phones, but more common on older systems, e-readers, and some embedded contexts (older email clients, some CMS editors).

Always preview your post on the platform you'll publish to before posting.

Inconsistently. Mathematical Alphanumeric Symbols and fullwidth characters are read differently by different screen readers — some spell them out letter-by-letter, others skip them, and some read them as their plain equivalents.

Recommendations:

• Keep critical information (names, dates, calls to action) in plain text
• Use styled emphasis sparingly — on headers and a few key lines
• Keep Safe accessibility mode on
• Aim for a "Light" or "Balanced" emphasis meter

Copy styled text copies only the Unicode-styled output. Paste it directly into a social post.

Copy JSON copies a structured payload — the styled text plus metadata about the platform, your formatting options, and character counts. Useful when piping output into automation tools like Zapier, n8n, or your own scripts.

Click Clear format in the input toolbar.

• If you have text selected, only that selection is cleared.
• If nothing is selected, the entire draft is converted back to plain ASCII.

The text content is preserved — only the Unicode styling is removed.

No tracking cookies. The site uses your browser's local storage to remember your theme (light / dark) and language (EN / NL). Those values stay on your device.

Google reCAPTCHA may set its own cookies when active; see the Privacy Policy.

Once the page has loaded, the formatter works without a network connection — all transformations happen in your browser. Loading the page initially does require a connection.

Yes. Two endpoints are available for deployments that include the serverless functions:

• POST /api/format — REST endpoint that returns the styled-text payload.
• POST /mcp — JSON-RPC Streamable-HTTP MCP endpoint for AI clients (Model Context Protocol).

Both accept either an Authorization: Bearer <API_TOKEN> header or an X-Recaptcha-Token header. See the project README for setup.

Use the Buy me a coffee button in the top bar of the main page. Feedback and bug reports are also welcome — see the About page for contact details.