Bubble Text Generator

What this tool is used for

• Styling a short phrase in a field that strips formatting.
• Producing a decorative label for a social post.
• Making a list marker stand out in plain text.
• Styling a display name so it stands out in a crowded follower list.
• Testing how a field renders enclosed alphanumeric characters.

Frequently Asked Questions

Where do the bubble letters come from?

The Enclosed Alphanumerics block (U+2460-24FF) for the circled forms, plus Enclosed Alphanumeric Supplement (U+1F100-1F1FF) for the filled ones. They were encoded for list markers and map legends, not decoration.

Why is the filled set incomplete?

Because the negative-circled letters were added piecemeal for specific uses, so several are missing or inconsistent in weight. Converters typically fall back to the outlined form mid-word, which is why filled bubble text often looks mixed.

Do the regional indicator letters belong here?

No, and confusing them causes a surprising bug: pairs of regional indicators combine into FLAG emoji. Typing certain two-letter sequences with them produces a flag rather than letters, which is rarely what anyone intends.

Are circled digits available?

Yes, ① through ⑳ and beyond, and they are genuinely useful as list markers. Note that ⓪ (circled zero) was added much later than 1-20, so older fonts may show it as tofu while the rest render fine.

How do they behave in a text field?

Each is a single code point, so cursor movement and deletion are normal — unlike Zalgo or flag emoji. That makes bubble text one of the better-behaved decorative options.

Does bubble text count against a character limit?

Yes, and often for more than it looks — each character is a single code point but sits above the basic plane in some sets, which makes it two units to any counter using UTF-16 length.

Why do some platforms show a square instead?

Font coverage. The enclosed alphanumeric blocks are not in every font, so a platform with a restricted font stack shows the fallback box for characters it cannot draw — most visible on older Android and in some desktop apps.

Can it be converted back to plain text?

Yes — the mapping is one-to-one, and NFKC normalisation converts most enclosed forms back to their base letters. That is also how a search index sees through it.

Common errors and gotchas

• Using it for anything that must be read aloud, since screen readers handle these poorly.
• Expecting complete coverage, as the enclosed ranges have gaps for some characters.
• Assuming it will render everywhere, when many fonts lack the glyphs.
• Expecting search or autocomplete to match the plain letters.
• Using it in long text, which becomes tiring and often illegible at small sizes.