Bubble Text Numbers and Case: What’s Actually Supported

"Bubble text" is really two different Unicode mechanisms with different rules: an outline circle (Ⓐⓐ) that supports both letter cases, and a filled "negative" circle (🅐) that exists only as uppercase.

Outline circled: both cases, all digits

Circled Latin capital letters (Ⓐ–Ⓩ) and circled Latin small letters (ⓐ–ⓩ) are both full 26-letter Unicode ranges — style either case and every letter converts. Digits are supported too, but through two separate ranges: digits 1–9 use one Unicode block (①–⑨), and 0 uses a different, standalone code point (⓪) — this tool applies both automatically so you don't need to think about the difference.

Negative (filled) circled: uppercase only

Negative circled Latin letters (🅐–🅩) exist only as uppercase in Unicode — there is no separate lowercase code point at all. If you style lowercase text with this option, we convert it to uppercase first and then circle it, so every letter still gets a filled bubble — but the original letter case is lost in the process. Our Plain Text Converter will get you the letters back, correctly, but as uppercase; it can't reconstruct which letters were originally lowercase.

Negative circled digits are also assembled from two different Unicode blocks: 0 comes from the Enclosed Alphanumerics block (⓿-style zero), while 1–9 come from the Dingbats block's "negative circled digit" characters — a good example of how Unicode's history across different eras of character additions shows up in small, specific gaps like this.

Quick reference

A rendering caveat

Circle rendering (thickness, exact diameter, whether the circle is even visible) varies by font more than most of our styles — some minimal system fonts render only the bare letter with no circle glyph at all. We haven't catalogued this per-platform yet (see testing methodology).

Squared letters follow the same uppercase-only pattern

This site's squared and negative-squared styles (a letter framed in a square rather than a circle) follow the identical rule as negative circled: Unicode only assigned uppercase code points for either variant, with no square-bracket digit glyphs at all. Lowercase input is upper-cased first, the same way as negative circled, and for the same reason — there simply is no lowercase squared "a" anywhere in the Unicode standard to use instead.

A worked example: styling a mixed-case word

Take the word "Bubble". In outline circled, it converts letter-for-letter with case preserved: ⒷⓤⓑⓑⓁⓔ — wait, precisely: capital B stays a capital circled letter, and each lowercase letter becomes its own separate lowercase circled letter, so the result reads Ⓑⓤⓑⓑⓛⓔ, visually matching the original capitalization exactly. In negative circled, the same word first gets upper-cased to "BUBBLE" internally, then every letter becomes a filled circled capital: 🅑🅤🅑🅑🅛🅔. Run that second result back through the Plain Text Converter and you get "BUBBLE" back — correctly recovered as letters, but you can no longer tell that the original word had a single capital B and five lowercase letters, because Unicode never encoded that information for this particular style in the first place.

Why we don't just fake a lowercase negative-circled alphabet

Some fancy-text tools work around this gap by rendering a small circle character combined with a regular letter using layout tricks, or by borrowing a visually similar glyph from an unrelated Unicode block. We avoid that: a character that isn't really "negative circled lowercase b" at the Unicode level will behave unpredictably (different font support, different reverse-conversion behavior, different screen-reader handling) from the real, standard characters used everywhere else in this style. Reporting the honest limitation is more useful than manufacturing a fake completeness that breaks in ways we can't predict or explain.

Where bubble text is actually the right choice

Circled letters work best in short, deliberately spaced-out contexts — a single styled word in a bio, a header line, or a short label — rather than long-form text, for two practical reasons. First, each circled character occupies visually more horizontal space than a plain letter, so a long circled sentence wraps and reflows differently than the plain version, which can look cramped or oddly spaced depending on the container. Second, since digits and letters both convert to enclosed forms, a circled sentence full of both is visually busier than a sentence styled in something like bold or italic that preserves normal letterforms with just a weight or slant change.

How this compares to circled/enclosed emoji you might already know

Some emoji keyboards include enclosed-looking symbols (like a red circle emoji layered manually behind text in an image), but that's a completely different mechanism — a picture or a colored emoji glyph, not a text character at all. It can't be copy-pasted as text, doesn't appear in a plain-text field's character count, and isn't searchable. The circled letters described in this article are ordinary Unicode text characters, indistinguishable at the code-point level from any other letter, which is exactly why they can be typed into a bio field, copy-pasted anywhere plain text goes, and picked up by our engine's coverage counting the same way any other letter is.

Questions people actually ask

Why does my circled text look like plain letters with no circle at all? That's a font-coverage gap on the viewing device or app, not a generation error — see our troubleshooting guide for the general explanation of this symptom.

Can I mix outline and filled circled letters in the same word? Not directly through one style selection — each result row applies one style consistently. You could manually combine copied results from both rows if you want a mixed effect, though we haven't tested how consistently that renders across apps.

Do circled digits support anything beyond 0–9, like two-digit numbers? Not as single circled characters — Unicode's circled-number series stops at double digits for a few special cases (like circled 10) that aren't part of this tool's standard 0–9 digit mapping, so numbers above 9 are styled digit-by-digit.