Lowercase o with stroke and acute (ǿ) is the Unicode character at U+01FF in Latin Extended-B. Official name: LATIN SMALL LETTER O WITH STROKE AND ACUTE — the letter o with both a diagonal stroke and an acute accent.
Remember
Character ǿ
Unicode U+01FF
Hex entity ǿ
Decimal ǿ
CSS escape \01FF
Named entity (none)
Capital Ǿ (U+01FE)
Not the same o · ø (ø) · ó (ó)
Prefer ǿ or ǿ in HTML when you need an entity. You can also type ǿ in a UTF-8 document.
Built with Hex: ǿ
Built with Decimal: ǿ
Built with CSS: ǿ
Typed: ǿ
Notation: [ǿ]
How It Works
1. Hex:U+01FF → ǿ in HTML. The browser turns it into ǿ.
2. Decimal: same code point as 511 → ǿ. Same result as hex.
3. CSS: use \01FF in content (not an HTML entity). #point::after appends ǿ.
4. Typed: paste ǿ in a UTF-8 document for Faroese or linguistic text. There is no named entity — numeric form is required when you need an entity.
Pitfalls & Tips
Common mistakes when working with lowercase o with stroke and acute.
Named?
No named entity
HTML5 does not define a named entity for U+01FF. Use ǿ or ǿ.
ø
Not stroke alone
ø (ø) has only the stroke. ǿ also has an acute — different letter, different code point.
ó
Not ó alone
ó (ó) is o with acute only. Do not swap it for ǿ when both marks are required.
Fonts
Need Extended-B coverage
Some fonts omit Latin Extended-B. Prefer a font that includes U+01FF for reliable glyphs.
CSS
Pad the CSS escape
Prefer \01FF (four hex digits). A short \1FF can swallow the next hex digit if one follows immediately.
CSS vs HTML
Do not mix escapes
\01FF belongs in CSS strings. ǿ / ǿ belong in HTML.
Semicolon
End references
Always finish entities with ; — write ǿ, not ǿ.
Compatibility
Browser Support
Lowercase o with stroke and acute (U+01FF) and its entity forms (ǿ, ǿ, CSS \\01FF) are supported in all mainstream browsers. Visible glyphs depend on Latin Extended-B font coverage.
✓ Universal support
Lowercase O Stroke Acute (ǿ)
Encode with hex, decimal, CSS escape, or type the character — same code point everywhere encoding is supported.
100%Browser coverage
Google ChromeSupported
Yes
Microsoft EdgeSupported
Yes
Mozilla FirefoxSupported
Yes
Apple SafariSupported
Yes
OperaSupported
Yes
Internet ExplorerAll versions
Yes
U+01FFFull support
Bottom line: Prefer ǿ or ǿ in HTML when encoding must be explicit, and \\01FF only inside CSS content. There is no named entity.
Remember
Key Takeaways
Unicode: lowercase o with stroke and acute is U+01FF (decimal 511) — glyph ǿ.
HTML: use ǿ or ǿ — no named entity.
CSS: use \01FF inside content for generated text.
Watch out: ǿ ≠ ø ≠ ó ≠ plain o.
One line:U+01FF → ǿ / ǿ / CSS \01FF (no named entity).
Frequently Asked Questions
Use ǿ (hex), ǿ (decimal), type ǿ in UTF-8, or the CSS escape \01FF in content. There is no HTML5 named entity for U+01FF.
U+01FF (LATIN SMALL LETTER O WITH STROKE AND ACUTE). Hex 1FF, decimal 511. It belongs to Latin Extended-B (U+0180–U+024F).
No. HTML5 does not define a named entity for this character. Use numeric references like ǿ or ǿ when you need an entity form.
Use it for Faroese and linguistic notation that needs ǿ. Prefer ø when only the stroke is required, and ó when only the acute is required.
HTML entities (ǿ or ǿ) go in markup. The CSS escape \01FF goes in stylesheet strings (usually content on ::before/::after).
No. ø (U+00F8, ø) has only a stroke. ó (U+00F3, ó) has only an acute. U+01FF is a precomposed letter with both marks.
🤔
Did you know?
Lowercase o with stroke and acute is Unicode U+01FF (decimal 511) — LATIN SMALL LETTER O WITH STROKE AND ACUTE in Latin Extended-B. HTML5 has no named entity for it — use ǿ or ǿ. Capital is U+01FE (Ǿ). It combines a stroke through o with an acute above — mainly Faroese and linguistic notation.
