HTML Entity for Roman Numeral One (Ⅰ)

Beginner
⏱️ 5 min read
📚 Updated: Aug 2025
🎯 1 Code Example
Unicode U+2160

What You'll Learn

How to display Roman Numeral One (Ⅰ) in HTML using Unicode entity methods: hex, decimal, and a CSS escape. This character is part of the Number Forms block and is useful for outlines, chapter numbering, and typographic roman numerals.

The character is referenced as Unicode U+2160.

⚡ Quick Reference — Roman Numeral One (Ⅰ)

Unicode U+2160

Number Forms block

Hex Code Ⅰ

Hexadecimal reference

HTML Code Ⅰ

Decimal reference

Named Entity

No named entity available

Reference Table
Name           Value
────────────   ──────────
Unicode        U+2160
Hex code       Ⅰ
HTML code      Ⅰ
Named entity   —
CSS code       \2160
1

Complete HTML Example

This example renders Ⅰ using the hex entity, decimal entity, and a CSS escape on a pseudo-element:

html
<!DOCTYPE html>
<html>
<head>
 <style>
  #point:after{
   content: "\2160";
  }
 </style>
</head>
<body>

<p>Roman One using Hexa Decimal: &#x2160;</p>
<p>Roman One using HTML Code: &#8544;</p>
<p id="point">Roman One using CSS Entity: </p>

</body>
</html>
Try It Yourself

🌐 Browser Support

This Unicode character (Ⅰ) and its numeric entities are supported in modern browsers (rendering can vary slightly by font):

Chrome 1+
Firefox 1+
Safari 1+
Edge 12+
Opera 4+
Android 4.4+
iOS Safari 1+

👀 Live Preview

See Ⅰ used in a few common numbering patterns:

Chapter label Chapter Ⅰ
Large glyph
Inline in text Parts: Ⅰ, Ⅱ, Ⅲ
Monospace Ⅰ -> level 1
With entities Hex: Ⅰ | Decimal: Ⅰ

🧠 How It Works

1

Hexadecimal Code

&#x2160; uses the Unicode hexadecimal value 2160 to display Ⅰ.

HTML markup
2

Decimal HTML Code

&#8544; uses the decimal Unicode value 8544 for the same character.

HTML markup
3

CSS Entity

\2160 is a CSS escape typically used in the content property of pseudo-elements.

CSS stylesheet
=

Same visual result

All methods render . Unicode U+2160 is in the Number Forms block.

Use Cases

Roman Numeral One (Ⅰ) is commonly used in:

📋 Outlines

Hierarchical numbering like Ⅰ, Ⅱ, Ⅲ for main sections.

📌 Lists

Primary list numbering in articles and documentation.

📚 Academic Content

Chapter/volume numbering and citation styles.

📑 Chapters & Parts

Formats like “Part Ⅰ” or “Chapter Ⅰ”.

🎨 Typography

Roman numeral styling in headings and captions.

⚖️ Legal / Book Numbering

Volume numbering (Ⅰ, Ⅱ, Ⅲ) and conventions.

💡 Best Practices

Do

  • Use &#x2160; or &#8544; consistently across a page
  • Verify font support for the Number Forms block on your target devices
  • Use semantic structure (<ol>, headings) for real lists/outlines and treat Ⅰ as a stylistic glyph
  • Ensure Ⅰ is distinguishable from the letter “I” in your chosen font where it matters

Don’t

  • Assume there is a named entity for Ⅰ (there isn’t)
  • Mix CSS escapes into HTML content (use them in stylesheets only)
  • Use roman numeral glyphs where plain digits are clearer
  • Rely on one font without fallbacks for Number Forms characters

Key Takeaways

1

Ⅰ is Unicode U+2160 (Number Forms)

U+2160 &#x2160; &#8544;
2

Use CSS escape for generated content in content

\2160
3

There is no named HTML entity for Ⅰ

4

Font choice matters—make sure Ⅰ isn’t confused with “I”

❓ Frequently Asked Questions

Use &#x2160; (hex), &#8544; (decimal), or \2160 in CSS content. All render Ⅰ.
U+2160 (hex 2160, decimal 8544) in the Number Forms block.
No. Use numeric references like &#x2160; or &#8544;.
Some fonts draw roman numeral glyphs similarly to letters. If clarity matters, choose a font with distinct Number Forms, or use CSS list styles / plain text numbering.
For real lists, CSS list-style-type: upper-roman keeps semantics and scales automatically. Use Ⅰ when you need the specific Unicode glyph in inline text or UI labels.

Explore More HTML Entities!

Discover 1500+ HTML character references — currency symbols, arrows, math operators, emojis, and more.

All HTML Entities →

About the author

Mari Selvan M P
Mari Selvan M P 🔗

Developer, cloud engineer, and technical writer

  • Experience 12 years building web and cloud systems
  • Focus Full Stack Development, AWS, and Developer Education

I write practical tutorials so students and working developers can learn by doing—from databases and APIs to deployment on AWS.

8 people found this page helpful