Fullwidth won sign (￦) is the Unicode character at U+FFE6 in Halfwidth and Fullwidth Forms. Official name: FULLWIDTH WON SIGN. It is the fullwidth form of the regular won sign ₩ — same meaning (Korean won), wider glyph for East Asian layouts.
Remember
Character ￦
Unicode U+FFE6
Hex entity ￦
Decimal ￦
CSS escape \FFE6
Named entity (none)
Meaning fullwidth Korean won currency symbol
Not the same ₩ (won U+20A9) · ￥ (fullwidth yen) · W
Prefer ￦ or ￦ in HTML (no named form). You can also type ￦ in a UTF-8 document. For most pages, prefer the regular won sign (₩).
Built with Hex: ￦
Built with Decimal: ￦
Built with CSS: ￦
Typed: ￦
Price: ￦５０００
Regular won: ₩
How It Works
1. Hex:￦ inserts code point U+FFE6 → ￦.
2. Decimal: same code point as 65510 → ￦. Same visual as hex.
3. CSS: use \FFE6 in content (not an HTML entity). #point::after appends ￦.
4. Typed: paste ￦ in a UTF-8 document when you need the fullwidth won glyph. Compare with ₩ for the regular halfwidth form.
Pitfalls & Tips
Common mistakes when working with fullwidth won sign.
Name
No named entity
There is no HTML5 named entity for U+FFE6. Use ￦ or ￦. Do not invent &fullwon;.
₩
Not regular won (U+20A9)
Regular won is ₩ (U+20A9). Fullwidth is ￦. Prefer ₩ unless you need fullwidth alignment.
Yen
Not yen
Fullwidth yen is ￥ (U+FFE5). Won and yen look related but are different currencies and code points.
Width
Mixed widths look uneven
Pair ￦ with fullwidth digits (for example ５０００). Mixing with ASCII digits often looks misaligned.
Font
Font coverage
Some fonts omit fullwidth currency forms. If ￦ is missing, fall back to ₩ or a font with Halfwidth and Fullwidth Forms coverage.
CSS vs HTML
Do not mix escapes
\FFE6 belongs in CSS strings. ￦ / ￦ belong in HTML.
a11y
Add accessible text
Screen readers may not announce ￦ clearly. Prefer aria-label="5000 won" or nearby prose when the amount matters.
Semicolon
End references
Always finish entities with ; — write ￦, not ￦.
Compatibility
Browser Support
Fullwidth won sign (U+FFE6) and its entity forms (￦, ￦, CSS \\FFE6) are supported in all mainstream browsers. Visible glyphs depend on Halfwidth and Fullwidth Forms font coverage.
✓ Universal support
Fullwidth Won Sign (￦)
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+FFE6Full support
Bottom line: Prefer ￦ in HTML (no named form). Use ￦ when decimal form is required, and \\FFE6 only inside CSS content.
Remember
Key Takeaways
Unicode: fullwidth won is U+FFE6 (decimal 65510) — glyph ￦.
HTML: no named entity — use ￦ / ￦ / type ￦.
CSS: use \FFE6 inside content for generated text.
Meaning: ￦ ≠ ₩ (prefer regular won unless you need fullwidth).
One line:U+FFE6 → ￦ / ￦ / CSS \FFE6 (no named form).
Frequently Asked Questions
Use ￦ (hex), ￦ (decimal), type ￦ directly in UTF-8, or the CSS escape \FFE6 in content. There is no named HTML entity for U+FFE6.
U+FFE6 (FULLWIDTH WON SIGN). Hex FFE6, decimal 65510. It belongs to the Halfwidth and Fullwidth Forms block (U+FF00–U+FFEF).
No. HTML5 does not define a named entity for U+FFE6. Prefer ￦ or ￦. The regular won sign (U+20A9) also has no named entity.
Use it in East Asian fullwidth layouts where currency symbols should match fullwidth digit width. Prefer the regular won sign (U+20A9) for most Western or mixed pages.
HTML numeric entities (￦ or ￦) go in markup. The CSS escape \FFE6 goes in stylesheet strings (usually content on ::before/::after).
No. U+FFE6 is the fullwidth won (￦). The regular won sign is U+20A9 (₩). They look similar but have different widths and code points.
🤔
Did you know?
Fullwidth won sign is Unicode U+FFE6 (decimal 65510) — glyph ￦ (FULLWIDTH WON SIGN) in Halfwidth and Fullwidth Forms. There is no HTML5 named entity; use ￦ or ￦. It is the fullwidth counterpart of the regular won sign (₩, U+20A9). Prefer ₩ for most layouts; use ￦ when aligning with East Asian fullwidth typography.
