Fullwidth Won Sign ￦

￦ (U+FFE6) is a standard Unicode character that you can copy and paste anywhere text is accepted. This page provides a concise reference with safe tips, internal links, and practical guidance so you can use it reliably across apps and platforms.

What it is and where it’s used: Fullwidth Won Sign is part of the Symbols family (block: Halfwidth and Fullwidth Forms). If you need styled or decorative alternatives, try our Fancy Text tool to generate compatible text that works in most modern interfaces.

History & usage: FULLWIDTH WON SIGN is a currency symbol used in pricing and finance. Its code point is U+FFE6, and it belongs to the Halfwidth and Fullwidth Forms block. It uses the Common script. Its primary role is to denote monetary units when fullwidth characters are needed in text. The symbol appears in contexts that require alignment with other fullwidth characters. In practice, currencies can be shown with various signs across locales, and the one used can affect how numbers and prices are presented. The Fullwidth Won Sign is part of a set of characters designed for fullwidth text, which helps integrate with other typography. Usage notes indicate that currency symbols can denote price, cost, or value in financial data and documents. Formatting of currency symbols, including placement and spacing, can vary by locale and system settings. This symbol, like others in its block, supports clear representation in environments that use fullwidth forms. The general idea is that currency signs denote amounts and help readers identify money at a glance.

Copy and input: the quickest method is to copy the character here. You can also insert it by its codepoint U+FFE6 in many development tools or editors. Some operating systems provide a character viewer or input palette that lets you search by name or code and insert the glyph into documents.

Display and fallback: if you see an empty box (tofu) or a placeholder rectangle, the active font might not include this codepoint. Switching to a font with broader Unicode coverage or using a fallback font usually fixes the issue. On the web, ensure the page’s font stack includes a general‑purpose fallback.

Related references: browse the Categories for similar characters. When choosing a symbol, prefer the official codepoint for semantic clarity and better compatibility with search, copy, and accessibility tooling.

See our category page for related symbols.