HTML Entity for Lowercase N Eng (ŋ)

Beginner
⏱️ 5 min read
📚 Updated: Jun 2026
🎯 1 Code Example
Unicode U+014B

What You'll Learn

How to display the lowercase n eng (ŋ) in HTML using named entity, hexadecimal, decimal, and CSS escape methods. This character is U+014B in the Latin Extended-A block. It represents the velar nasal sound—the “ng” in “sing” or “ring”—and is used in the International Phonetic Alphabet (IPA) and in languages such as Sami and Inuktitut.

Render it with ŋ, ŋ, ŋ, or CSS escape \014B. The named entity ŋ is often the most readable option in HTML source.

⚡ Quick Reference — Lowercase N Eng Entity

Unicode U+014B

Latin Extended-A

Hex Code ŋ

Hexadecimal reference

HTML Code ŋ

Decimal reference

Named Entity ŋ

Most readable option

Reference Table
Name           Value
────────────   ──────────
Unicode        U+014B
Hex code       ŋ
HTML code      ŋ
Named entity   ŋ
CSS code       \014B
Meaning        Latin small letter eng
IPA            Velar nasal (ng in “sing”)
Related        U+014A = Ŋ (uppercase)
Block          Latin Extended-A (U+0100–U+017F)
1

Complete HTML Example

A simple example showing the lowercase n eng (ŋ) using hexadecimal code, decimal HTML code, the named entity, and a CSS content escape:

html
<!DOCTYPE html>
<html>
<head>
 <style>
  #point:after{
   content: "\014B";
  }
 </style>
</head>
<body>
<p>Symbol (hex): &#x014B;</p>
<p>Symbol (decimal): &#331;</p>
<p>Symbol (named): &eng;</p>
<p id="point">Symbol (CSS): </p>
</body>
</html>
Try It Yourself

🌐 Browser Support

The lowercase n eng (ŋ) and the named entity &eng; are supported in all modern browsers:

Chrome1+
Firefox1+
Safari1+
Edge12+
Opera4+
Android4.4+
iOS Safari1+

👀 Live Preview

See the lowercase n eng (ŋ) in phonetic and language contexts:

Large glyphŋ
IPAVelar nasal: siŋ (sing), riŋ (ring)
SamiUsed in Northern Sami and other Sami orthographies
Named entity&eng; renders as ŋ
Not the same asȵ (n curl)  |  ň (n caron)  |  ñ (n tilde)
Numeric refs&#x014B; &#331; &eng; \014B

🧠 How It Works

1

Hexadecimal Code

&#x014B; uses the Unicode hexadecimal value 014B to display the character. The x prefix indicates hexadecimal format.

HTML markup
2

Decimal HTML Code

&#331; uses the decimal Unicode value 331 to display the same character. A common method when a numeric reference is needed.

HTML markup
3

Named Entity

&eng; is the named entity for eng (Latin small letter eng)—readable in source HTML and easy to remember for this IPA and orthography symbol.

HTML markup
4

CSS Entity

\014B is used in CSS stylesheets, particularly in the content property of pseudo-elements like ::before and ::after.

CSS stylesheet
=

Same visual result

All four methods produce the glyph: ŋ. Unicode U+014B sits in Latin Extended-A. Uppercase equivalent: U+014A (Ŋ). Do not confuse with ȵ (n curl), ň (n caron), or ñ (n tilde).

Use Cases

The lowercase n eng (ŋ) is commonly used in:

🎤 IPA Transcription

Standard IPA symbol for the velar nasal consonant. Used in dictionaries, linguistics, and phonetic guides.

🇪🇺 Sami Languages

Essential in Northern Sami, Inari Sami, Skolt Sami, and other Sami orthographies for correct spelling and localization.

🇨🇦 Inuktitut

Used in Inuktitut and other indigenous Latin-script orthographies. Correct characters improve readability and respect for native writing systems.

🌐 Multilingual Sites

Localization for Nordic minority languages and indigenous content. Set appropriate lang attributes for SEO and accessibility.

⚙ Programmatic HTML

When building HTML from language data or CMS content, using &#331; or &eng; guarantees correct output.

📚 Documentation

Tutorials on HTML entities, Unicode, IPA, or language orthographies showing &eng; and numeric codes.

♿ Accessibility

Using the correct character (U+014B) ensures assistive technologies interpret language-specific content correctly.

💡 Best Practices

Do

  • Use &eng; in HTML when possible for readability
  • Serve pages as UTF-8; you can also type ŋ directly in UTF-8 source
  • Set lang="se", lang="iu", or other appropriate codes on relevant content
  • Use fonts that support Latin Extended-A phonetic and orthography characters
  • Distinguish ŋ (eng) from ȵ (n curl) and ň (n caron) in linguistic content

Don’t

  • Confuse ŋ (eng) with ȵ (n curl), ň (n caron), or ñ (n tilde)
  • Substitute “ng” digraph when ŋ is required in IPA or orthography
  • Put CSS escape \014B in HTML text nodes
  • Double-encode numeric references in dynamically generated HTML
  • Omit UTF-8 encoding on pages with extended Latin characters

Key Takeaways

1

Four references render ŋ; named entity is most readable

&#x014B; &#331; &eng;
2

For CSS stylesheets, use the escape in the content property

\014B
3

Unicode U+014B — LATIN SMALL LETTER ENG (velar nasal)

4

Used in IPA, Sami, Inuktitut; uppercase is Ŋ (U+014A)

❓ Frequently Asked Questions

Use &eng; (named), &#x014B; (hex), &#331; (decimal), or \014B in CSS content. In UTF-8 you can also type ŋ directly.
U+014B (LATIN SMALL LETTER ENG). Latin Extended-A block. Hex 014B, decimal 331. Represents the velar nasal sound used in IPA and languages like Sami and Inuktitut. Uppercase form is U+014A (Ŋ).
When displaying IPA transcription, Sami, Inuktitut, or other languages that use ŋ, in linguistics or multilingual content, or when you need a reliable character reference. In UTF-8 pages you can type ŋ directly.
The named HTML entity is &eng;. You can also use &#331; or &#x014B;, or the CSS entity \014B.
HTML entity (&eng;, &#331;, or &#x014B;) is used in HTML content; CSS entity \014B is used in stylesheets in the content property of pseudo-elements. Both produce ŋ.

Explore More HTML Entities!

Discover 1500+ HTML character references — IPA symbols, letters, 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