How to Convert Your Name to Binary Code

To convert your name to binary code, replace each letter with its 8-bit binary number from the ASCII table and join the groups with spaces, because computers store text as numbers and binary is how those numbers look in base two. Convert any name instantly with our free text to binary converter.

Try it now: Text to Binary Converter →

The Method: One Letter, One 8-Bit Number

Converting a name to binary is a lookup repeated once per character, and the lookup table is ASCII, the numbering scheme that assigns every common character a number from 0 to 127. Each letter has one ASCII number, and that number written in base two, padded to 8 digits, is the letter in binary. An uppercase A is ASCII 65, which is 01000001 in binary, while a lowercase a is ASCII 97, which is 01100001, and the difference between the two, 32, is the whole story of case in ASCII, covered below. A space is ASCII 32, which is 00100000, so spaces get their own binary group too, and forgetting the space group is the most common reason a converted name decodes to the wrong words. Digits have ASCII numbers as well, so a name containing a number converts that digit by its ASCII value, not by its face value: the character 7 is ASCII 55, which is 00110111, not the binary for the number seven, which would be 00000111. The method is therefore mechanical: write the name, look up each character, write each 8-bit group, and separate the groups with spaces so the result can be read back. Our guide to converting text to binary by hand explains the division-by-two arithmetic behind each group, for readers who want the numbers, not just the table.

Try it now: Text to Binary Converter →

Worked Example: Sam in Binary

Take the name Sam, three letters, three groups, and convert it letter by letter to see the method in full. The uppercase S is ASCII 83, and 83 in binary is 01010011, because 64 plus 16 plus 2 plus 1 equals 83, and those are the place values switched on. The lowercase a is ASCII 97, and 97 in binary is 01100001, because 64 plus 32 plus 1 equals 97. The lowercase m is ASCII 109, and 109 in binary is 01101101, because 64 plus 32 plus 8 plus 4 plus 1 equals 109. Joined with spaces, Sam in binary is 01010011 01100001 01101101, three groups of eight digits, twenty-four digits in total, and that length rule is worth remembering: every character in a name becomes exactly eight binary digits, so a five-letter name is forty digits, and a ten-letter name is eighty. To check the result, decode it back: read each group as a binary number, look up the ASCII character for that number, and the letters S, a, and m should reappear in order. If they do not, the usual culprit is a dropped leading zero, because 01010011 without its first zero is a seven-digit group that decodes to a different character, which is why padding every group to eight digits matters more than getting any single digit right.

Uppercase, Lowercase, and the 32 Rule

Case changes a name in binary in exactly one place, and knowing that place saves a second table lookup for every letter. An uppercase letter and its lowercase partner differ by 32 in ASCII, and in binary that difference is a single bit, the sixth bit from the right, which is off for uppercase and on for lowercase. Uppercase A is 01000001 and lowercase a is 01100001, and the only digit that changes is the second one, from 0 to 1. The same holds across the alphabet: uppercase B is 01000010 and lowercase b is 01100010, uppercase Z is 01011010 and lowercase z is 01111010, and the pattern never breaks, because the ASCII table was designed with that gap deliberately. That design is also why a name typed in the wrong case converts to a visibly different binary string, and why a binary tattoo, username, or piece of jewelry made from a name must be checked letter by letter against the intended case, not just against the intended letters. A name like Sam and a name like SAM are different binary strings, and a decoder reading SAM will return the wrong name, even though a human reader would call them the same name. Our letter to binary chart lists every letter in both cases, so a long name can be converted without looking up each letter separately.

Spaces, Accented Letters, and Characters Beyond ASCII

Two complications appear as soon as a name leaves plain English letters, and both have clean answers. First, spaces: a first name and a last name are separated by a space character, ASCII 32, binary 00100000, so Mary Jane converts as the groups for M, a, r, y, then 00100000, then J, a, n, e, and dropping that group merges the two names into one unreadable word. Second, accented letters: ASCII stops at 127, so letters like e with an acute accent, n with a tilde, or any non-English letter are not in ASCII at all, and modern systems store them as UTF-8, where one character can take two, three, or four bytes. The letter e-acute, for example, is two bytes in UTF-8, which is sixteen binary digits instead of eight, so a name containing it is longer in binary than its letter count suggests, and a converter that assumes one byte per character will garble it. The practical rule is to use a converter that states UTF-8 handling, and to test the result by decoding it back, because a round trip that returns the exact original name proves the encoding was right, while a round trip that returns replacement characters proves it was not. For a name written entirely in plain letters, none of this matters, and the ASCII method above is complete.

Decoding Binary Back to a Name, and Uses for Name Binary

Decoding reverses the method: split the binary string into 8-digit groups, convert each group from base two to an ordinary number, and look up the ASCII character for that number. The group 01010011 is 83, which is S, the group 01100001 is 97, which is a, and the group 01101101 is 109, which is m, so the string 01010011 01100001 01101101 decodes to Sam, and the round trip confirms the conversion. That reversibility is why name binary shows up in puzzles, classroom exercises, bracelets, and social-media bios: it looks secret, but anyone with the ASCII table can read it, so it is encoding, not encryption, and it must never carry a password or a private message. The same warning applies to every encoding on this site: our guide to converting binary to decimal manually shows the place-value arithmetic the decoding step uses, and the principle is identical there. For a name that must stay readable, keep the groups separated by spaces, keep the case exactly as intended, and decode the finished string once before printing, engraving, or posting it, because a single flipped digit changes a letter, and a changed letter changes the name. A useful self-test is to convert a short name twice, once by hand from the chart and once with the converter, and compare the two strings digit by digit, because agreement between two independent methods is strong evidence that neither method slipped. If the two disagree, check the leading zeros first, then the case of each letter, then whether a space group was dropped, since those three causes explain nearly every mismatch, and only after ruling them out should the arithmetic of an individual group be rechecked. For timing a talk that explains all this, our free minutes to hours converter turns rehearsal minutes into decimal hours, and our free word counter keeps a script inside its word limit.