DotDashKeySupport Us

Text to Binary, Hex & ASCII Translator

Multi-byte characters (accents, emoji, non-Latin scripts) are encoded as several bytes each, the same way UTF-8 stores them on disk — one emoji can legitimately produce 4 separate bytes.

Result appears here as you type.

ASCII table lookup

CharDecHexBinary
(space)322000100000
!332100100001
"342200100010
#352300100011
$362400100100
%372500100101
&382600100110
'392700100111
(402800101000
)412900101001
*422a00101010
+432b00101011
,442c00101100
-452d00101101
.462e00101110
/472f00101111
0483000110000
1493100110001
2503200110010
3513300110011
4523400110100
5533500110101
6543600110110
7553700110111
8563800111000
9573900111001
:583a00111010
;593b00111011
<603c00111100
=613d00111101
>623e00111110
?633f00111111
@644001000000
A654101000001
B664201000010
C674301000011
D684401000100
E694501000101
F704601000110
G714701000111
H724801001000
I734901001001
J744a01001010
K754b01001011
L764c01001100
M774d01001101
N784e01001110
O794f01001111
P805001010000
Q815101010001
R825201010010
S835301010011
T845401010100
U855501010101
V865601010110
W875701010111
X885801011000
Y895901011001
Z905a01011010
[915b01011011
\925c01011100
]935d01011101
^945e01011110
_955f01011111
`966001100000
a976101100001
b986201100010
c996301100011
d1006401100100
e1016501100101
f1026601100110
g1036701100111
h1046801101000
i1056901101001
j1066a01101010
k1076b01101011
l1086c01101100
m1096d01101101
n1106e01101110
o1116f01101111
p1127001110000
q1137101110001
r1147201110010
s1157301110011
t1167401110100
u1177501110101
v1187601110110
w1197701110111
x1207801111000
y1217901111001
z1227a01111010
{1237b01111011
|1247c01111100
}1257d01111101
~1267e01111110

Type text above to see its binary or hexadecimal representation, or paste in binary to convert it back to readable text. Under the hood, every character you type is first looked up in a character-code table — by default ASCII — which assigns each letter, digit and punctuation mark a specific whole number, and that number is what actually gets shown in binary or hex. Converting "A" to binary isn't really converting a letter at all; it's converting the number 65, which is what "A" happens to mean in ASCII.

Why Everything Comes Down to a Number Table

Computers only ever store numbers. ASCII (American Standard Code for Information Interchange), standardized in 1963 as ANSI X3.4, solved the problem of getting text into that number-only world by fixing a single agreed table: 65 always means capital A, 97 always means lowercase a, 48 always means the digit character "0", and so on through 128 total code points, using just 7 bits. That original 1963 version didn't even include lowercase letters — they were added in the 1967 revision once 7 bits' worth of headroom was better understood to be enough for both cases plus punctuation and control codes. Every modern system still honors that original 128-character mapping exactly, which is why ASCII is sometimes called the closest thing computing has to a universal constant.

Reading the Binary Output

Each character converts to 8 binary digits — a byte — with the extra leading bit (ASCII only strictly needs 7) fixed at 0 for standard text. "A" is 65 in decimal, which is 01000001 in binary: reading right to left, that's 64 + 1, matching 65. Spaces between bytes in the output mark character boundaries, the same way the space between Morse letters marks a letter boundary elsewhere on this site — without that separator, a run of 1s and 0s would be genuinely ambiguous about where one character's code ends and the next one begins.

Why Emoji and Accented Letters Break a Naive Binary Converter

ASCII only ever defined 128 characters, which is nowhere near enough for the accented letters used across European languages, let alone emoji or non-Latin scripts. Modern text almost always relies on UTF-8 instead — this site's binary and ASCII reference covers exactly who built it and why — which keeps plain ASCII text untouched while spreading anything outside those original 128 characters across two, three, or even four bytes tagged with a leading-bit pattern marking each one as part of a larger character. That's why a naive character-by-character binary converter that assumes one letter equals one byte will mangle an emoji or an accented letter like é — it isn't a bug in the concept of binary conversion, it's a sign the converter is silently assuming ASCII when the actual input needs UTF-8's multi-byte rules.

Hexadecimal: The Same Numbers, Shorter

Hex output represents the exact same underlying character-code numbers as the binary output, just in base 16 instead of base 2, using digits 0-9 and letters A-F. "A" (65 decimal, 01000001 binary) is 41 in hex — noticeably shorter to read and far less error-prone to type by hand than eight 1s and 0s, which is exactly why hex is the format programmers actually use when they need to look at raw byte values, from memory addresses to color codes to network packet dumps.

A Worked Example: Converting "Hi"

"H" is 72 in ASCII (01001000 in binary, 48 in hex) and "i" is 105 (01101001 in binary, 69 in hex). So "Hi" becomes 01001000 01101001 in binary, or 48 69 in hex — two bytes for two characters, which holds true for any plain-ASCII text but stops holding true the moment UTF-8 multi-byte characters get involved.

Hex Decoding and the ASCII Lookup Table

Hex now decodes back to text as well, handling the same multi-byte UTF-8 reassembly as the binary decoder — paste in space-separated hex pairs (the "0x" prefix is optional and ignored) and they're regrouped into the correct characters, not read one byte per character. Below the converter, a searchable ASCII lookup table lists every printable character from space through tilde alongside its decimal, hex and binary values, so you can look up a single code without running a full conversion.

Frequently Asked Questions

Is binary code the same thing for every computer, or does it vary by machine?

The 1s and 0s themselves are universal, but what they mean depends entirely on the agreed character-code table being used — ASCII, UTF-8, and older systems like EBCDIC all assign different numbers to the same letters, so the same binary sequence can decode to different text under a different table.

Why is a byte always 8 bits instead of some other number?

There's no law of physics requiring it — early computers used varying word sizes — but 8 bits became the near-universal standard because it comfortably covers the 128 ASCII codes with room to spare, splits evenly into two 4-bit hex digits, and was cemented by influential 1960s-70s hardware like IBM's System/360, after which the rest of the industry converged on it too.

Does capitalization change the binary value of a letter?

Yes, and by exactly 32 in decimal for every letter: lowercase letters sit 32 higher than their uppercase counterparts in the ASCII table (A is 65, a is 97), a deliberate design choice with a genuinely elegant side effect — it turns case-conversion into a one-position binary toggle instead of a full lookup-table swap.