Inkantic

Binary code tattoo generator

A binary code tattoo generator turns a name or a date into ones and zeros. This one draws them as filled circles and rings rather than typed digits, offers both seven-bit ASCII and eight-bit UTF-8 because they produce different designs, and exports a vector SVG your artist can scale.

Written outA 0 1 0 0 0 0 0 1, d 0 1 1 0 0 1 0 0, a 0 1 1 0 0 0 0 1. Word break. 1 0 0 1 1 0 0 0 1, 8 0 0 1 1 1 0 0 0, 1 0 0 1 1 0 0 0 1, 5 0 0 1 1 0 1 0 156 bits, 7 characters, UTF-8 at 8 bits per byte

ASCII and UTF-8 draw different tattoos

Binary is not one code. A character becomes a number first, and which number depends on the encoding. ASCII is a seven-bit code with 128 slots — the English alphabet, digits, common punctuation, nothing else. UTF-8 covers every writing system at eight bits per byte, one to four bytes per character. For an English name the difference is exactly one leading zero per character, and that zero is another ring on your skin: the default above, “Ada 1815”, is 56 bits in UTF-8 and 49 in ASCII.

Outside the English alphabet they stop agreeing. Type “Zoé” with ASCII selected and the tool reports that é was left out, because ASCII has no code for it — the design would quietly read “Zo”. In UTF-8 the same é is two bytes, sixteen marks, one character taking twice the room of its neighbors. A single emoji takes four bytes, or thirty-two marks.

General-purpose converters handle this unevenly. Of two ranking for “text to binary” in August 2026, one offers a full encoding menu and the other goes through the ASCII table only and says so. Neither is wrong, but a converter that never names its encoding is asking you to tattoo a guess.

The gaps do the work the screen used to do

On a screen, spaces separate the bytes and a monospace font keeps them lined up. On skin there is no font, so the drawing has to carry its own grouping or a row of circles cannot be split back into characters. Binary, unlike Morse code, has no spacing standard: the proportions below are ours, and we state them rather than imply a rule that does not exist.

1 : 1 : 3 : 7Mark width, gap between bits, gap between bytes, gap between words — the ratios the one-line layout draws, measured off its own output. The default row layout puts each character on its own line, so only the first two apply there and a word break becomes a doubled row gap instead. Binary has no spacing standard, so the only real requirement is that the byte gap reads as wider than the bit gap; the values come from international Morse timing rather than from anything specific to binary

Two consequences before the appointment. The gap replaces the space character rather than encoding it — as a seven-unit interval on one line, as a doubled row gap in the default row layout — so a byte-by-byte reading gives your words run together either way; the Morse code tattoo generator treats word breaks the same way. And a zero is a ring whose hole is exactly half the mark width, which makes that hole the first thing ink spread takes away.

Eight marks a character, and what that costs

Binary is the least compact way to write anything on a body. Every character is eight marks in UTF-8 and seven in ASCII, whichever character it is, so length follows from the count alone: on one line a word of n characters measures 18n − 3 units, a unit being one mark width. Five characters is 87 units — 261 millimeters at a three-millimeter mark, longer than most forearms.

That arithmetic is why the tool opens stacked. One character per row makes the same five-letter name 15 units wide and 13 tall, about 45 by 39 millimeters, and turns it into a column that suits a spine or the inside of an arm. The trade is the three-unit byte gap becoming a line break, which is typography rather than part of the code.

Size the design from the hole rather than from the mark. At a three-millimeter mark the hole in a zero is 1.5 millimeters, and that hole is the whole difference between a zero and a one at conversational distance. Placements that hold fine detail badly close it first, which is the practical half of our tattoo placement guide.

How to use it

  1. Step 1Type the text and pick the encodingASCII for plain English and the shorter design, UTF-8 for accents or non-Latin characters. The line under the drawing reports the bit count, so the choice is visible rather than theoretical.
  2. Step 2Choose a column or a single lineA column suits a spine, a forearm or a rib. One continuous line keeps every gap in the geometry, word breaks included, but grows past a limb quickly — read the width before committing to it.
  3. Step 3Print it at the final sizeHold the print at arm’s length. If the holes in the zeros disappear, scale the whole design up rather than thinning the rings.
  4. Step 4Hand your artist the SVGAsk that the file is scaled rather than redrawn by eye. Redrawing is what usually flattens the byte gaps, and a design with even spacing throughout no longer decodes to anything.

One extra check costs nothing: copy the bits and paste them, one word at a time, into any independent binary-to-text converter. The slash marking a word break is our notation, not part of the code, and seven-bit groups will be rejected by a converter that assumes eight — check those against an ASCII table instead.

When binary is the wrong idea

Binary suits a short string: a name, a year, one word. A sentence it does not — eight marks a character makes a twelve-character phrase 96 marks. It is also the wrong choice if the point is that others read it, since most people see a pattern of circles and rings and stop there.

For the same message in fewer marks, Morse spends one to four symbols per letter and five per digit instead of a flat eight. For a message meant to be read, plain lettering does the job and the tattoo font generator shows a word in 24 styles at once. If the coded line is the only settled part, the random tattoo generator proposes the rest of the brief.

The encoding is public if you want to check our arithmetic: UTF-8 is defined in RFC 3629, which sets out how many bytes each character takes.

Questions people ask

How do I turn my name into binary code for a tattoo?
Type the name into a binary code tattoo generator and choose an encoding. Each character becomes eight bits in UTF-8 or seven in ASCII, so a five-letter name is forty marks or thirty-five. This tool draws those marks as filled circles and rings and exports them as a vector SVG your artist can scale.
Should a binary tattoo use ASCII or UTF-8?
For plain English letters, digits and basic punctuation, UTF-8 gives the same bits as ASCII with one extra zero in front of each character. Choose ASCII to save that mark per character, and UTF-8 if the text has accents, non-Latin letters or emoji, which ASCII cannot represent at all.
How long is a binary code tattoo?
On one continuous line a five-character word measures 87 units in UTF-8, where a unit is the width of one mark. At a three-millimeter mark that is 261 millimeters, longer than most forearms. Stacked one character per row the same word is 15 units wide and 13 tall, or 45 by 39 millimeters.
Can I get a binary tattoo design as a vector file?
Yes. This generator exports SVG, which is vector: the circles and rings scale to any size without a soft edge. That matters more here than for lettering, because the readable part of a zero is the hole in the middle, and a scaled-up raster fills that hole with blur.
Will anyone be able to read a binary tattoo?
Only someone who groups the marks correctly and knows the encoding. That is why the gap between bytes is drawn three times wider than the gap between bits: without a visible break, a row of circles cannot be split into characters and decodes to nothing.
Does the space between two words get its own code?
In most text converters yes, as the byte 00100000. Neither layout here encodes it. The one-line layout shows a word break as a seven-unit gap; the default row layout, where every character already sits on its own line, shows it as a double row gap — six units center to center against three inside a word. Either way a strict byte-by-byte reading gives the words run together, so say which convention you used if someone else will decode the design.