Superscript Ordinal Generator
Make a copyable 1st, 2nd, 3rd, 4th—or any ordinal—with the correct raised suffix.
Numbers ending in 11, 12 and 13 correctly use th.
Normal digits, raised suffix—the conventional form for dates and rankings.
Every available digit and suffix character is raised for display text.
Common Superscript Ordinals
Tap an example to load it into the generator. Use the suffix form for ordinary writing; use the full version when the whole number should look raised.
When to Superscript the Suffix
In normal English typography, write the digits at the baseline and raise only the ending: 1ˢᵗ, 2ⁿᵈ, 3ʳᵈ, 4ᵗʰ. This is especially clear in dates, competition positions and compact labels. The fully raised version is a decorative Unicode alternative, not a requirement for correct writing.
How Ordinal Endings Work
Most numbers ending in 1 use st, 2 use nd, 3 use rd, and the rest use th. The exception is 11, 12 and 13: they always use th. This tool applies the rule before converting the suffix with the same Unicode characters used by the Superscript Generator.
Choose the Standard or Fully Raised Form
The standard result keeps the number on the baseline and raises only the ending: 21ˢᵗ or 42ⁿᵈ. It is the clearer choice for dates, edition labels, rankings, and ordinary prose because the number stays easy to scan. The fully superscript result, such as ²¹ˢᵗ, is a display treatment. It can work in a short heading, profile line, or compact label, but it is not a substitute for a publisher’s normal style guide. For a digits-only value, use the Superscript Numbers 0–9 tool rather than applying an ordinal ending.
If you are unsure, copy the standard form first. A reader should be able to understand an ordinal without needing to recognize a decorative character. The generator shows both versions so that the visual choice is deliberate rather than an accidental side effect of converting every character.
Check the Destination Before You Publish
Superscript suffixes are Unicode text, not formatting attached to a document. Many modern browsers, chat apps, and profile fields display them, but acceptance is controlled by the place where you paste. A strict form may allow only plain letters and digits; a searchable field may treat the raised letters differently; and a system using its own font may show a fallback glyph. Paste one short example into a draft before using the style in a public label or a saved form.
Do not use decorative ordinals in passwords, account identifiers, source-code names, or other machine-readable values. For a date, legal record, or anything people must search and copy exactly, ordinary 1st, 2nd, and 3rd remain the safest fallback. The Character Coverage Reference explains why this site leaves unsupported characters unchanged instead of pretending every letter has a perfect raised counterpart.
Check the Language Rule Before Styling
This generator implements English ordinal endings. The last digit normally determines the suffix—1st, 2nd, 3rd, then th—but 11th, 12th, and 13th override that pattern, including 111th, 112th, and 113th. It does not translate ordinal conventions for other languages or decide whether a date style is appropriate for a particular publisher.
For ordinary writing, leave the number at baseline and raise only the suffix. The fully raised output is supplied for compact display text, not as a replacement for editorial style. As with the other Unicode tools, copy a result into the actual destination before publishing: a strict form field may reject decorative characters even when a browser displays them correctly.
FAQ
How do you write 1st in superscript?
The usual copy-and-paste form is 1ˢᵗ. The raised letters are Unicode characters, so they keep their appearance when you paste them into supported text fields.
Why are 11th, 12th and 13th not 11st, 12nd and 13rd?
They are special English ordinal endings: 11ᵗʰ, 12ᵗʰ and 13ᵗʰ. The rule applies to 111th, 112th and 113th as well.
Will the superscript suffix work everywhere?
It works in many modern apps and browsers because it is Unicode text. A strict form or username field can still reject it, so test the destination before relying on it.