Is the output an image or text?

It is text. Each cell is a single Unicode Braille character from the range U+2800 to U+28FF, so you can copy and paste it like any other text — no image file is produced.

How are pixels turned into Braille?

A Braille cell holds a 2-wide by 4-tall pattern of dots. The renderer slices the pixel grid into 2×4 blocks and sets the matching dot bits, then adds the result to the base code point U+2800.

Why do some characters disappear?

Only A–Z and 0–9 are in the built-in 5×5 font. Lowercase is uppercased; punctuation and other symbols are skipped so the grid stays clean.

Will it display correctly everywhere?

Most modern fonts include Braille glyphs, so it renders on the web, Discord, and many editors. A few older fonts lack them and will show boxes instead of dots.

Is this readable by a Braille display?

Not meaningfully. The dots form a visual bitmap of the letters, not Braille spellings, so a refreshable Braille display would output the raw dot patterns, not the words.

Braille Dot Bitmap Renderer

Draw text with Braille dots

The Unicode Braille block (U+2800–U+28FF) contains 256 characters, one for every possible arrangement of dots in a 2-wide by 4-tall cell. That makes Braille characters a handy, compact way to draw bitmaps in plain text — each character packs eight pixels. This tool renders your text on a pixel grid and then encodes that grid as Braille characters you can copy and paste.

How it works

Each supported character is stored as a 5×5 pixel font, where 1 is a filled dot and 0 is blank. The letters are laid out left to right with a one-pixel gap to form one wide pixel grid. The grid is then scanned in 2×4 blocks; for each block the renderer sets the corresponding dot bits and adds them to the base code point:

cell = 0x2800
for each set pixel (col, row) in the 2x4 block:
    cell |= DOT_BIT[row][col]
character = String.fromCharCode(cell)

The Unicode dot-bit layout is not sequential — the left column is bits 1, 2, 4, 64 top-to-bottom and the right column is bits 8, 16, 32, 128 — so the tool uses that exact mapping to produce valid Braille glyphs.

Tips and notes

Display the result in any Unicode-aware context; unlike ASCII art it does not strictly require a monospace font, though monospace keeps multi-line output tidiest. Keep inputs short, since each character is five pixels wide and the combined bitmap can get wide quickly. If you see empty boxes instead of dots, your font lacks Braille glyphs — switch to a font like Segoe UI Symbol, Noto Sans, or DejaVu Sans.