{"id":757,"date":"2026-09-06T08:08:57","date_gmt":"2026-09-06T08:08:57","guid":{"rendered":"https:\/\/texttoolz.com\/blog\/?p=757"},"modified":"2026-09-06T08:08:57","modified_gmt":"2026-09-06T08:08:57","slug":"how-to-type-currency-symbols","status":"publish","type":"post","link":"https:\/\/texttoolz.com\/blog\/how-to-type-currency-symbols\/","title":{"rendered":"How to Type Currency Symbols Your Keyboard Does Not Have"},"content":{"rendered":"<p>The euro sign is one character, <code>\u20ac<\/code>, which Unicode calls <code>U+20AC EURO SIGN<\/code> and files as a currency symbol. The pound, cent and yen are <code>U+00A3<\/code>, <code>U+00A2<\/code> and <code>U+00A5<\/code>. On Windows, hold <kbd>Alt<\/kbd> and type <kbd>0128<\/kbd> on the numeric keypad, or press <kbd>AltGr<\/kbd> and <kbd>4<\/kbd>. On a Mac, press <kbd>Option<\/kbd> and <kbd>Shift<\/kbd> and <kbd>2<\/kbd>.<\/p>\n<p>There is a second reason the euro gives people trouble, and it has nothing to do with the keyboard. Three of those four signs can be stored in the older character encoding that most systems fall back to, and the euro cannot be stored in it at all. That is why the euro breaks in places the pound does not, on the same machine, in the same application. It is measured further down.<\/p>\n<h2>How Do You Type the Euro Sign?<\/h2>\n<p>Three routes exist: a numeric code, a dedicated key on the keyboard layout, and a character picker. Which of them you have depends on your keyboard rather than on your operating system, which is why the answers you find contradict each other.<\/p>\n<h3>On Windows with a numeric keypad<\/h3>\n<p>Hold <kbd>Alt<\/kbd>, type <kbd>0128<\/kbd> on the numeric keypad, then release <kbd>Alt<\/kbd>. Num Lock must be on and the digits must come from the keypad rather than the number row above the letters. The leading zero is not decoration and is not optional: it decides which internal table Windows reads the number from. That mechanism is measured on <a href=\"https:\/\/texttoolz.com\/blog\/how-to-type-degree-symbol\/\">our page about the degree symbol<\/a>, where the same rule inverts and gives you the wrong character, so it is worth understanding once rather than memorising per symbol.<\/p>\n<h3>On Windows without a numeric keypad<\/h3>\n<p>Press <kbd>AltGr<\/kbd> and <kbd>4<\/kbd> together. On the US International layout it is <kbd>AltGr<\/kbd> and <kbd>5<\/kbd> instead. This is the route that depends on the keyboard rather than the machine, and it is why so many people conclude the shortcut is broken: on a plain US layout there is no AltGr key at all, and the combination does nothing. Microsoft&#8217;s own answer page ranking for this query exists because of exactly that confusion. The route that always works regardless of layout is the emoji panel: press <kbd>Windows<\/kbd> and the period key, choose the omega symbols tab, and pick the sign.<\/p>\n<h3>On a Mac<\/h3>\n<p>Press <kbd>Option<\/kbd> and <kbd>Shift<\/kbd> and <kbd>2<\/kbd> on a US layout. On a UK layout it is <kbd>Option<\/kbd> and <kbd>2<\/kbd>, without the Shift, which is the same layout dependence running in the other direction and it catches people who move between machines regularly. If you would rather look the character up than remember which of the two applies, press <kbd>Control<\/kbd> and <kbd>Command<\/kbd> and <kbd>Space<\/kbd> to open the Character Viewer and search it for the word euro.<\/p>\n<h3>In Word, Excel, PowerPoint and Outlook<\/h3>\n<p>The answer is the same in all four, which is why this is one section rather than four. Insert, then Symbol, finds the sign in every one of them. Word additionally accepts the Unicode route: type <kbd>20AC<\/kbd> and press <kbd>Alt<\/kbd> and <kbd>X<\/kbd> immediately after. All four Office applications also bind <kbd>Ctrl<\/kbd> and <kbd>Alt<\/kbd> and <kbd>E<\/kbd> directly to the euro sign. There is one Excel-specific point the general guides omit: a euro sign typed into a cell turns that cell into text, so if the number has to stay a number and be added up, apply the euro through currency formatting instead and leave the value alone.<\/p>\n<h3>In Google Docs, Sheets and Gmail<\/h3>\n<p>In Google Docs, use Insert, then Special characters, and search the panel for the word euro. Sheets and Gmail have no equivalent picker, so there the answer is either an operating-system method from above or a substitution rule that turns a string of your choosing into the character as you type. This section exists because of a genuine gap in what ranks: five of the related searches Google itself lists under this query name a Google product, and not one of the pages ranking for it covers any of them.<\/p>\n<h3>On a phone<\/h3>\n<p>Switch to the symbols layout and press and hold the currency key. The alternatives appear in a pop-up above your finger, including the euro, the pound and the yen. Which sign appears on the key itself before you hold it depends on the phone&#8217;s region setting, so the default under your finger is usually your local currency and the rest are hidden behind the long press. That is worth knowing because it makes the key look like it only does one thing.<\/p>\n<h2>How Do You Type the Pound, Cent and Yen Signs?<\/h2>\n<p>The same way, with different numbers: <kbd>Alt<\/kbd> <kbd>0163<\/kbd> for the pound, <kbd>Alt<\/kbd> <kbd>0162<\/kbd> for the cent, <kbd>Alt<\/kbd> <kbd>0165<\/kbd> for the yen. On a Mac, <kbd>Option<\/kbd> and <kbd>3<\/kbd> gives the pound and <kbd>Option<\/kbd> and <kbd>4<\/kbd> gives the cent.<\/p>\n<h3>The pound sign<\/h3>\n<p><kbd>Alt<\/kbd> <kbd>0163<\/kbd> on Windows, <kbd>Option<\/kbd> and <kbd>3<\/kbd> on a Mac. On a UK keyboard layout none of that is necessary, because the pound is simply <kbd>Shift<\/kbd> and <kbd>3<\/kbd>, printed on the key. On a US layout that same physical key gives you a hash instead and the pound sign is not on the keyboard anywhere. This is the clearest example on this page of the point made throughout it: the question of how to type a character often has a different answer on two machines running identical software.<\/p>\n<h3>The cent, yen and rupee signs<\/h3>\n<p><kbd>Alt<\/kbd> <kbd>0162<\/kbd> gives the cent and <kbd>Alt<\/kbd> <kbd>0165<\/kbd> gives the yen. The Indian rupee, <code>\u20b9<\/code>, has no Alt code of that kind at all, and needs the hexadecimal route, <kbd>20B9<\/kbd> followed by <kbd>Alt<\/kbd> and <kbd>X<\/kbd> in Word, or a character picker anywhere else. That absence is not an oversight in this page or in Windows. It is the beginning of the next section, because the rupee and the euro have something in common that the pound, cent and yen do not.<\/p>\n<h2>Why Can&#8217;t I Type the Euro Sign on My Keyboard?<\/h2>\n<p>There are two entirely different reasons, and they get mistaken for each other constantly. The first is the keyboard, and it is well covered: four of the seven pages ranking for this query explain AltGr and the difference between UK, European and US layouts, including Microsoft&#8217;s own answer page. If your AltGr combination does nothing, that is the reason, and the sections above are the fix.<\/p>\n<p>The second reason is the encoding, and nothing on this search covers it. Older text systems fall back to ISO-8859-1, usually called Latin-1. Encoding each sign through the Python standard library shows which of them that older standard can hold at all:<\/p>\n<div class=\"table-scroll\" style=\"overflow-x:auto;max-width:100%\">\n<table>\n<caption>Which currency signs can be stored in ISO-8859-1. Measured with the Python standard library codecs on 3 September 2026.<\/caption>\n<thead>\n<tr>\n<th>Character<\/th>\n<th>Fits in ISO-8859-1?<\/th>\n<th>Byte<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>\u00a3<\/code> pound U+00A3<\/td>\n<td>Yes<\/td>\n<td>0xA3<\/td>\n<\/tr>\n<tr>\n<td><code>\u00a2<\/code> cent U+00A2<\/td>\n<td>Yes<\/td>\n<td>0xA2<\/td>\n<\/tr>\n<tr>\n<td><code>\u00a5<\/code> yen U+00A5<\/td>\n<td>Yes<\/td>\n<td>0xA5<\/td>\n<\/tr>\n<tr>\n<td><code>\u20ac<\/code> euro U+20AC<\/td>\n<td><strong>No, cannot be encoded at all<\/strong><\/td>\n<td>none exists<\/td>\n<\/tr>\n<tr>\n<td><code>\u20b9<\/code> rupee U+20B9<\/td>\n<td><strong>No, cannot be encoded at all<\/strong><\/td>\n<td>none exists<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>The reason is chronology. The pound, cent and yen were in the standard before it was finalised. The euro was introduced in 1999, after ISO-8859-1 was fixed and could no longer be added to, and the rupee sign is more recent still. So the euro has no representation in that encoding whatsoever, while the pound has had one all along.<\/p>\n<p>This is what makes the problem feel like a keyboard fault when it is not. The pound works and the euro does not, on the same machine, in the same application, typed the same way. Wikipedia&#8217;s article on the euro sign already explains the related half of this, that Microsoft allocated byte 0x80 in Windows-1252 to the euro, and credit for that belongs to it. What is added here is the asymmetry: which signs the older standard can hold and which it cannot.<\/p>\n<figure><img decoding=\"async\" src=\"https:\/\/texttoolz.com\/blog\/wp-content\/uploads\/2026\/09\/ttz-type-currency-latin1.png\" alt=\"Four currency signs and whether ISO-8859-1 can store them: pound fits at byte 0xA3, cent at 0xA2, yen at 0xA5, and the euro cannot be encoded in it at all\" \/><figcaption>The three older signs have a slot in the standard. The euro arrived after it was fixed, and the rupee later still.<\/figcaption><\/figure>\n<h2>Why Does My Euro Sign Show as Strange Characters?<\/h2>\n<p>Because one program wrote the text as UTF-8 and another read those same bytes as Windows-1252, and neither of them reported an error. The characters you end up with are completely predictable, and they are worth recognising on sight because they tell you exactly what went wrong.<\/p>\n<div class=\"table-scroll\" style=\"overflow-x:auto;max-width:100%\">\n<table>\n<caption>Each sign encoded as UTF-8 and then read back as Windows-1252. Measured with the Python standard library on 3 September 2026.<\/caption>\n<thead>\n<tr>\n<th>Character<\/th>\n<th>UTF-8 bytes<\/th>\n<th>What appears instead<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>\u00a3<\/code> pound<\/td>\n<td><code>C2 A3<\/code><\/td>\n<td><code>\u00c2\u00a3<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>\u20ac<\/code> euro<\/td>\n<td><code>E2 82 AC<\/code><\/td>\n<td><code>\u00e2\u201a\u00ac<\/code><\/td>\n<\/tr>\n<tr>\n<td><code>\u00a5<\/code> yen<\/td>\n<td><code>C2 A5<\/code><\/td>\n<td><code>\u00c2\u00a5<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>Wikipedia states that documents exchanged between systems that made different encoding choices would fail to display, and that is accurate as far as it goes. It does not show what they display instead, and no other page ranking for this question does either. The strings above are what actually appears on a mispriced product page or in a spreadsheet exported from the wrong system.<\/p>\n<p>One detail makes them diagnosable at a glance. The euro turns into three characters where the pound and yen turn into two, because the euro is a three-byte character in UTF-8 and the other two are two-byte. So a price list full of two-character garbage was probably pounds, and one full of three-character garbage was euros. This is the same class of silent failure as <a href=\"https:\/\/texttoolz.com\/blog\/invisible-characters-explained\/\">the invisible characters that survive a copy and paste<\/a>: nothing errors, and the text is simply wrong.<\/p>\n<figure><img decoding=\"async\" src=\"https:\/\/texttoolz.com\/blog\/wp-content\/uploads\/2026\/09\/ttz-type-currency-mojibake-1.png\" alt=\"Three currency signs encoded as UTF-8 and read back as Windows-1252: pound from bytes C2 A3, euro from bytes E2 82 AC producing three characters, and yen from bytes C2 A5\" \/><figcaption>The exact output strings. The euro mangles into three characters because it is three bytes in UTF-8.<\/figcaption><\/figure>\n<h2>What This Page Does Not Claim<\/h2>\n<p>No keystroke here was tested by us. There is no Windows machine in this environment, so every shortcut is reported as what its named source publishes, and the encoding results are arithmetic performed with the Python standard library.<\/p>\n<p>Two things on this page were established by other people first and are credited where they are used rather than presented as findings. Keyboard layout and the AltGr key are carried by four of the seven pages ranking for this query, Microsoft&#8217;s own answer page among them. The allocation of byte 0x80 to the euro in Windows-1252 is published by Wikipedia. Worth saying plainly: the plan for this page proposed keyboard-layout dependence as the thing nobody had covered, and reading the ranking pages showed that four of them cover it thoroughly. That half of the plan was dropped rather than written.<\/p>\n<h2>How This Guide Was Built<\/h2>\n<p>Eight ranking results were captured live on 3 September 2026 with the country set to the United States and personalisation off, and the AI Overview was captured twice to confirm it was stable. Seven of the eight were extracted in full at no cost. The eighth is recorded as blocked with the tool and the reason: it returned nothing behind a Cloudflare wall, and a paid fetch was not spent on it because Microsoft&#8217;s answer page in the same result set covers the identical question of typing the euro without a numeric keypad.<\/p>\n<p>Keyword research was run the same day against Google autocomplete. That source publishes no search volume and none is quoted here. Encoding behaviour was measured with Python 3.12.13 and the standard library cp1252 and latin-1 codecs, and character properties with unicodedata at Unicode version 15.0.0.<\/p>\n<p>Sources credited by name above: Wikipedia and Microsoft Learn.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The euro sign is one character, \u20ac, which Unicode calls U+20AC EURO SIGN and files as a currency symbol. The pound, cent and yen are U+00A3, U+00A2 and U+00A5. On Windows, hold Alt and type 0128 on the numeric keypad, or press AltGr and 4. On a Mac, press Option and Shift and 2. There [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":752,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-757","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guides"],"_links":{"self":[{"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/posts\/757","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/comments?post=757"}],"version-history":[{"count":1,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/posts\/757\/revisions"}],"predecessor-version":[{"id":758,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/posts\/757\/revisions\/758"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/media\/752"}],"wp:attachment":[{"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/media?parent=757"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/categories?post=757"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/tags?post=757"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}