Won Sign ₩

₩ (U+20A9) 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: Won Sign is part of the Symbols family (block: Currency Symbols). If you need styled or decorative alternatives, try our Fancy Text tool to generate compatible text that works in most modern interfaces.

History & usage: The WON SIGN is a currency symbol with the codepoint U+20A9 in the Currency Symbols block. It sits in the Common script and is used to represent monetary units in prices and finance. In text, it helps readers identify amounts quickly and clearly. The symbol appears in various numeric formats and interacts with digits to form prices in financial documents and everyday transactions. Its use helps track value and cost across markets and records. The research language for this symbol focuses on how it communicates money and value in writing. The meaning stays the same even when the amount changes, while the surrounding formatting can differ. The WON SIGN serves as a compact sign that teams use in invoices, receipts, and catalogs. Users place it next to numbers or at the start of an amount, depending on local rules. This flexibility makes it useful in many regions and formats. The usage note highlights that formatting can vary by locale and that the symbol is part of standard financial notation across platforms and systems.

Copy and input: the quickest method is to copy the character here. You can also insert it by its codepoint U+20A9 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.