Which converter do you need?
Binary TranslatorText ↔ binary code, 8-bit UTF-8
01001000 01101001Morse Code TranslatorText ↔ Morse with sound and light... --- ...Roman Numeral ConverterNumbers, years and dates2026 = MMXXVIText to HexText ↔ hexadecimal bytes48 65 6c 6c 6fASCII ConverterText ↔ ASCII codes, full table72 101 108 108 111Base64 Encode / DecodeUTF-8, URL-safe, file to data URISGVsbG8=Binary to DecimalBinary, octal, decimal, hex1011 = 11How are binary, hex, ASCII and Base64 related?
They all describe the same thing: the bytes a computer stores for your text. Each character is first turned into one or more bytes with UTF-8 (plain English letters are one byte each). The converters then just write those bytes in a different form.
| Format | "Hi" written as | Used for |
|---|---|---|
| Binary | 01001000 01101001 | Teaching, puzzles, low-level debugging |
| Hexadecimal | 48 69 | Hex dumps, colors, escape sequences |
| ASCII / decimal codes | 72 105 | Character codes in programming |
| Base64 | SGk= | Email attachments, data URIs, tokens |
| Morse code | .... .. | Radio, signaling, puzzles |
Is the conversion done on your server?
No. Every converter on these pages runs as JavaScript in your browser. Nothing you type is sent anywhere, so you can paste private text safely.
Why does an emoji or accented letter become several bytes?
UTF-8 uses 1 byte for ASCII characters, 2 bytes for most accented Latin, Greek and Cyrillic letters, 3 bytes for most other scripts such as Korean or Chinese, and 4 bytes for emoji. "é" is C3 A9 in hex, and "😀" is F0 9F 98 80.
Sources: RFC 3629 (UTF-8) · RFC 4648 (Base64) · ITU-R M.1677-1 (Morse). Checked October 2026.