Keyboard Symbols

How to type @, €, µ, ± and the rest, with the layout each one depends on.

Checked in a browser on 2026-11-19 · how these tools are tested · runs on your device

Shift, AltGr and Alt codes

Most symbols are a shifted key: @ is Shift+2 on a US layout. The ones that are not usually need AltGr, which European layouts have and US ones do not, or a numeric Alt code typed on the keypad.

    Layouts differ

    £ is Shift+3 on a UK keyboard and nowhere on a US one; € is AltGr+E on many European layouts. The page names the layout whenever the key depends on it.

      Alt codes

      On Windows, hold Alt and type the code on the numeric keypad with a leading zero. Laptops without a keypad often cannot do it at all, which is why the character is also printed so it can be copied.

        Good to know

        On a laptop without a numeric keypad, Alt codes usually require the Fn key and sometimes do not work at all. Copying the character from the table is the reliable fallback.

        The characters in this table are ordinary Unicode text, so they can be copied from the page instead of typed. That is faster than an Alt code and works on keyboards that have no keypad.

          How Keyboard Symbols works

          Every symbol on a keyboard and the key combination that types it, including Alt codes and the layout differences. The method behind Keyboard Symbols is the single-purpose logic inside wave55.js, and this page shows the result with its assumptions in the open.

          • Open Keyboard Symbols and provide keyboard symbols — the page accepts it in the field it shows.
          • For Keyboard Symbols, parsers and formatters run as JavaScript on the text you paste.
          • The Keyboard Symbols output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.

          A worked example for Keyboard Symbols

          A typical run of Keyboard Symbols starts with keyboard symbols and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.

          Paste a payload you know is valid, then break it deliberately — the error message should point at the exact line, which is the difference between a formatter and a black box. That check applies directly to Keyboard Symbols with keyboard symbols.

            When to use Keyboard Symbols — and when not to

            Reasonable uses: Reading an API response; Checking a config file before committing; Comparing two payloads. Keyboard Symbols is deliberately narrow: it does one job and states its assumptions instead of hiding them.

            Editor extensions do this inside a project; they cannot help with a snippet from a ticket. A page that parses in isolation is the right tool for pasted text. The honest ceiling for Keyboard Symbols: for Keyboard Symbols, parsing happens in the tab, so huge files can stutter.

            • Best case for Keyboard Symbols: Reading an API response
            • Also fine with Keyboard Symbols: Checking a config file before committing
            • Not what Keyboard Symbols is for: for Keyboard Symbols, parsing happens in the tab, so huge files can stutter.

            Reading the Keyboard Symbols result

            The output of Keyboard Symbols is a function of the inputs alone — no hidden state and no server.

              Accuracy and limits of Keyboard Symbols

              The method is the single-purpose logic inside wave55.js. Keyboard Symbols prints results at the precision its inputs justify, and the limits below are the honest ones:

              • Keyboard Symbols: For Keyboard Symbols, parsing happens in the tab, so huge files can stutter.
              • For Keyboard Symbols, no validation against a schema unless the page says so.

              Privacy and speed on the Keyboard Symbols page

              The Keyboard Symbols page is a static file plus wave55.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.

              Speed follows the build: Keyboard Symbols loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.

                What you get from Keyboard Symbols

                The output of Keyboard Symbols appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the developer work finishes the moment the numbers are in.

                Because Keyboard Symbols is built from wave55.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.

                  Questions

                  What does Keyboard Symbols do?

                  Every symbol on a keyboard and the key combination that types it, including Alt codes and the layout differences. Everything runs in your browser; nothing is uploaded.

                  How accurate is Keyboard Symbols?

                  The method is the single-purpose logic inside wave55.js. For Keyboard Symbols, parsing happens in the tab, so huge files can stutter.

                  What are the limits of Keyboard Symbols?

                  For Keyboard Symbols, no validation against a schema unless the page says so.

                  Is anything uploaded when I use Keyboard Symbols?

                  No. Keyboard Symbols runs entirely in the browser tab; nothing is uploaded, stored or logged.

                  Can I use Keyboard Symbols offline?

                  Yes — Keyboard Symbols keeps working offline once the page has loaded; the whole tool is a local script.

                  Keep going

                  More developer tools